Contracts Release 10

Release Notes:

This is the tenth release of the Celo Core Contracts. It follows the standard release process per the docs.

Audit:

Security audit by Hexens attached is attached to this release.

Key updates in this release:

General:

1. Add solidity wrappers for CIP-20/30/31 precompiles #10240
2. Update Lock Gold Error Message "Not Account" #10315
3. Update upvote function #10268
4. Fix dequeueProposalIfReady() for expired proposals. #10324
5. Remove TransferWhitelist contract #10318
6. Proposal info exposed #10330
7. Interfaces solidity version update #10355
8. Governance vote delegation #10325

Relevant for Gingerbread Hardfork:
10. Ultra Green Celo Implementation #10227
11. GasPriceMinimum update #10437

Specific Version Updates:

• Accounts: 1.1.4.0 => 1.1.4.1
• BlockchainParameters: 1.2.0.0 => 1.3.0.0
• FeeCurrencyWhitelist: 1.1.0.0 => 1.1.1.0
• FeeHandler: N/A => 1.1.0.0
• GasPriceMinimum: 1.1.1.0 => 1.2.0.0
• Governance: 1.3.0.0 => 1.4.0.0
• LockedGold: 1.1.2.1 => 1.1.3.0
• MentoFeeHandlerSeller: N/A => 1.1.0.0
• UniswapFeeHandler: N/A => 1.1.0.0
• Validators: 1.2.0.4 => 1.2.0.5

@celo/explorer 5.0.5

patch changes

• 53bbd49: Note celo sdk packages will no longer be fix bumped (ie will not share the same version always) and will now use ^range when depending on each other
• d48c68a: Calls to getContractMappingFromSourcify() are now memoized in the same structure (this.addressMapping) as getContractMappingFromCore, getContractMappingWithSelector now runs in parallel

ContractKit / Connection / Wallets Release 5.1.0

5.1.0

Minor Changes

• 53bbd49: Add cip64 support for feeCurrency Transactions. Note this is the replacement for the deprecated cip42 and legacy tx types https://github.com/celo-org/celo-proposals/blob/master/CIPs/cip/0064.md

Patch

• 53bbd49: Note celo sdk packages will no longer be fix bumped (ie will not share the same version always) and will now use ^range when depending on each other

• d48c68a: Add memoization to Connection.chainId() funciton. this is reset when setProvider is called.

• d48c68a: parallelize async calls in Governance Wrapper

SDK Release 5.0.4

@celo/wallet-ledger

Fixes issue where uses trying to sign with ledger where unable to by forcing use of celo legacy tx type as this is all celo ledger app supports for now see #10487

CeloCLi 3.0.1

Fixes

• once again signing with ledgers work

[email protected]

Breaking changes

This release if the celocli bumps node support from node 14 to node 18

other changes / fixes

• gasCurrency param is now respected when sending tokens (previously would always use pay fee in same token sending (this is still the default behavior) #10483
• Fix CLI returning zero required votes on proposals with no tx #10477

dep changes

• use contractkit v5 (this brings eip 1559 / cip 42 support under the hood)
• bump humanize-duration to latest version
• remove unused deps, @celo/bls12377js, bip32, bip39

v5.0.0

Description

This Beta Release for 5.0 series Adds Support for and favors using eip1559 (when no fee currency selected) and cip42 (when it is) legacy transaction serialization will only be used if gasPrice is explicitly set.

Note on versions 5.0.0 and 5.0.1

These version have a bug and do not work use 5.0.2 or higher

Other changes

TopLine Changes

• Add support for CIP42 and EIP1559 Transactions
• Prefer EIP1559 if no feeCurrency and CIP42 if using feeCurrency, Old CeloLegacy transations still supported (set the gasPrice explicitly) but discouraged
  upgrade Web3 dependency

@celo/connect

• gasPrice is no longer an option on config. setting 0 (or any empty value) for gasPrice in transaction will result in maxFeePerGas and maxPriorityFee per gas being set on the transaction

• likewise gasPrice is no longer settable on the connection itself

• (note that the gasPrice function for fetching price from node is NOT affected)

• replace connection.fillGasPrice with connection.setFeeMarketGas

• add inputAccessListFormatter

• remove deprecated setGasPriceForCurrency

• EncodedTransaction Type now supports CIp42 and EIP1559 transactions

• inputCeloTxFormater now returns type FormattedCeloTx although apart from support for cip42 and eip1559 tx the data returned hasnt changed

• numberToHex, ensureLeading0x, inputAddressFormatter now are typed to return 0x{string} instead of just string

*added parseAccessList and inputAccessListFormatter for converting accessList from json to array of array and back

• RLPEncodedTx now types its transaction field as FormattedTransaction this is more accurate than the CeloTX type it previously had

@celo/contrackit

• removed gasPriceSuggestionMultiplier == gas price from rpc no longer multipled by 5

• remove kit.fillGasPrice

• remove updateGasPriceInConnectionLayer

• remove kit.gasPrice

@celo/wallet-base

• extractSignature now throws if the length of provided tx is not correct

• extractSignature was incorrectly typed to return Buffers for r and s values

• ensureLeading0x now types output to be 0x{string}

npm

https://www.npmjs.com/package/@celo/contractkit/v/5.0.0-beta.1

ODIS Combiner 3.0.0

Misc performance improvements. See #10513

ODIS Signer 3.0.1

This patch release fixes an issue we saw shortly after releasing v3.0.0 where the Signer incorrectly treats a closed socket from the Combiner as a timeout and attempts to respond with a 500 status code. When the Combiner receives enough responses from Signers to respond to the user, it will abort outstanding requests with an AbortSignal. In v3.0.0, the Signer timeout logic was upgraded to listen for 'abort' events and treat them as timeouts. Because the Signer was unable to distinguish between 'abort' events caused by timeouts and ones caused by the Combiner, it appeared to be timing out and returning 500s frequently.

In this release, we've changed back the Signer's timeout logic to rely on setTimeout and added a new connectionClosedHandler to catch closed socket events

ODIS Signer 3.0.0

• This upgrade features significant performance improvements to reduce latency and increase throughput.
• Full node queries will now be cached, so we've removed blockNumber from the SignMessageResponse type.
• We've also fully deprecated the legacy endpoints and deleted the legacy rate limiting mechanism from the code

See #10462