Celo-blockchain v1.7.0-stable includes the Istanbul consensus fork and a change in the RPC block representation to be more compatible with ethereum tools.
You will want to upgrade to this version if you are:
-
A Validator
-
Running an RPC node that is serving request that returns a block as a response, and your users, use libraries as for example
Ethers.js
Istanbul consensus fork #1937
Implements a consensus fork that is determined by a specific block number. From that sequence on, the messages Preprepare and RoundChange will be no longer used, and PreprepareV2 and RoundChangeV2 will be used instead. This is only relevant for validator nodes. This release already has set the Alfajores activation for Block # 14287656 and the Mainnet activation for Block #16068685.
RPC block representation changed #1957
An additional two fields have been added to the block representation returned by the RPC api, they are:
gasLimitbaseFeePerGas
Both fields previously existed as parameters of the system held in contract state. The reason for this change is to improve compatibility with existing ethereum tooling specifically Ethers.js which crashes if the gasLimit is not present on a block and is unable to send EIP-1559 transactions if baseFeePerGas is not present.
Note that the internal block representation has not been modified so these new fields should not be taken into account in block hashing or signing operations. Since these fields are not part of the internal block representation they need to be fetched from state when the RPC call is made, if the state for these fields is missing then they will not be present on the block response. Non archive full nodes retain state for only the last 128 blocks, so when interacting with a non archive full node blocks more than 128 below the head block or blocks older than about 10 minutes will not have these fields present. If you require these fields on all blocks then you will need to make your RPC requests to an archive node.
A new flag has been added which allows disabling the addition of the new fields as a measure to help ease the transition to the new RPC block representation, the flag will likely be removed in a future release.
Other changes
- Various fixes in mycelo
Notes (Important for Baklava validators already in the 1.7.0-beta.1)
The Enable Snap Sync #1962 that was part of the 1.7.0-beta.1 presented some issues that we were not able to reproduce. We decided to revert those changes for this particular version to be added in the future after verifying that everything works as it should
Docker Images
Celo blockchain client: us.gcr.io/celo-org/geth:1.7.0
Celo blockchain client and associated tools: us.gcr.io/celo-org/geth-all:1.7.0