Celo-Blockchain Release 1.5.7

The 1.5.7 release includes a fix to support bigger consensus messages on validators.

Changes

• Increase max size for p2p messages (#1922 )

Docker images

Celo blockchain client: us.gcr.io/celo-org/geth:1.5.7
Celo blockchain client and associated tools: us.gcr.io/celo-org/geth-all:1.5.7

Celo-Blockchain Release 1.5.5

The 1.5.5 release includes a mitigation to an issue with gas estimation observed in 1.5.4 after the Espresso hardfork.

You will want to upgrade to this version if you are running an RPC node that is serving eth_estimateGas queries. This included most nodes that support transaction submission.

Note that 1.5.4 also included a change to address an issue with gas estimation. The issue being addressed here exists in 1.5.4 and is
currently unknown.

Changes

• Add a gas inflation rate flag (#1865)
  Adds the rpc.gasinflationrate flag which specifies a multiplier to be applied to responses to eth_estimateGas. Default value is set to 1.3 to cover any minor underestimates.

Docker images

Celo blockchain client: us.gcr.io/celo-org/geth:1.5.5
Celo blockchain client and associated tools: us.gcr.io/celo-org/geth-all:1.5.5

Celo-Blockchain Release 1.5.4-stable

The 1.5.4 release includes two fixes which are important to RPC providing nodes.

You will want to upgrade to this version if you are:

• Running an RPC node that is serving debug_traceBlock queries.
  Examples of this could be block indexers, exchanges, and dApps that look up transaction as part of their logic.

• Running an RPC node that is serving eth_estimateGas queries.
  Examples of this would be most nodes that support transaction submission.

Changes

• Fix concurrent map access error when tracing blocks (#1822)
  Calling debug_traceBlock could result in a concurrent map access error causing the node to crash.

• Fix low gas estimates after espresso activation (#1858)
  Calling eth_estimateGas would provide a gas value that was too low to cover the execution of the transaction, causing the transaction submission to fail with an out of gas error.

Docker images

Celo blockchain client: us.gcr.io/celo-org/geth:1.5.4
Celo blockchain client and associated tools: us.gcr.io/celo-org/geth-all:1.5.4

Celo-Blockchain Release 1.5.3-stable

The 1.5.3 includes two fixes which are important to RPC providing nodes, and Baklava validators respectively.
​
You will want to upgrade to this version if you are:
​

• Running a Baklava validator. PR #1840 includes an important fix to block proposing behavior which is required to get the network back to full operation.
• Running an RPC node that responses to eth_getTransaction queries. Examples of this include block indexers, exchanges, and dApps that look up transaction as part of their logic.
  ​

Changes

​

• Fix to logic for showing gas price on the eth_getTransaction RPC (#1837)
• Fix to randomness contribution caching logic to fix miner behavior (#1840)
  ​

Docker images

​
Celo blockchain client: us.gcr.io/celo-org/geth:1.5.3
Celo blockchain client and associated tools: us.gcr.io/celo-org/geth-all:1.5.3

Celo-blockchain Release 1.5.2

The 1.5.2, fixes a security vulnerability found on consensus

Vulnerability involve Validators accepting as valid, a block without AggregatedParentSeal field on the header. This issue would generate consensus on an invalid block that later will be rejected the all full nodes. And quite probably stall the network. But safety of the network is not compromised.

• The fix and details on it can be found on #1830

Docker Images

geth: us.gcr.io/celo-org/geth:1.5.2
geth-all: us.gcr.io/celo-org/geth-all:1.5.2

Celo-blockchain Release 1.4.3

The 1.4.3, fixes a security vulnerability found on consensus

Vulnerability involve Validators accepting as valid, a block without AggregatedParentSeal field on the header. This issue would generate consensus on an invalid block that later will be rejected the all full nodes. And quite probably stall the network. But safety of the network is not compromised.

• The fix and details on it can be found on #1831

Docker Images

geth: us.gcr.io/celo-org/geth:1.4.3
geth-all: us.gcr.io/celo-org/geth-all:1.4.3

Celo-Blockchain Release 1.5.1-stable

This v1.5.1 it's a bug fix release. Also, updates the Mainnet Espresso block activation number

The Mainnet activation block is 11838440 targeting an activation at 12:15 PM PDT on March Tuesday 8th.

Important bug fixes

• Fix memory leak introduced in the 1.5.0. See the #1816 PR for more details
• Fix panic when fetching the pending block state over RPC (#1769)

Other fixes

• Reinstate delay before signature aggregation in backend.Prepare (#1798)
• Fix tx DecodeRLP for rlp lists (#1801)
• Fix race condition in tx pool (upstream cherry pick) (#1800)
• Fix minimum search in multicurrencyprice heap Pop (#1817)
• Eth api using baseFee only when needed (#1818)
• Return no effectiveGasPrice instead of 0, in case that the node has no state for that block (#1825)

Docker Images

geth: us.gcr.io/celo-org/geth:1.5.1
geth-all: us.gcr.io/celo-org/geth-all:1.5.1

Celo-Blockchain Release 1.4.2-stable

This v1.4.2 it's a bug fix release.

Fixes

• [tx_pool] Invalidate txs with gasPrice < gasPriceMinimumFloor (#1749)
• Reinstate delay before signature aggregation in backend.Prepare (#1798)

Docker Images

geth: us.gcr.io/celo-org/geth:1.4.2
geth-all: us.gcr.io/celo-org/geth-all:1.4.2

Celo-Blockchain Release 1.5.0-stable

The Mainnet activation block is 11354500 targeting an activation at 12:06 PM PDT on Tuesday February 8th.
The Alfajores activation block is 9472000 targeting an activation at 13:56 PM PDT on Thursday January 20th.

The biggest and most important change in v1.5.0 is the implementation and activation of the Espresso hard fork with the following CIPS.

• CIP-43: Block Context
• CIP-47: Increased round change timer for early rounds in IBFT
• CIP-45: Relax canPayFee condition for non-native tokens
• CIP-50: Allow unprotected transactions

Relative to v1.4.0 version 1.5.0 has the following breaking changes

Please note that reverting to Celo blockchain v1.4.0 or prior after upgrading to v1.5.0 is not possible without a resync because the blockchain database layout has changed. Please take a backup of the data directory to be able to downgrade.

Flag Changes
The following previously deprecated flags have been removed.

--pprofport value                      use --pprof.port
--pprofaddr value                      use --pprof.addr
--memprofilerate value                 use --pprof.memprofilerate
--blockprofilerate value               use --pprof.blockprofilerate
--cpuprofile value                     use --pprof.cpuprofile
--bootnodesv4                          use --bootnodes
--bootnodesv5                          use --bootnodes

The following flags have been removed

--vm.evm                           no substitute
--vm.ewasm                         no substitute
WHISPER (EXPERIMENTAL) OPTIONS
--shh                              no substitute
--shh.maxmessagesize value         no substitute
--shh.pow value                    no substitute
--shh.restrict-light               no substitute

The following flags have been added

--datadir.minfreedisk
--usb
--mainnet
--txlookuplimit
--light.nosyncserve
--cache.preimages
--http.rpcprefix
--http.timeout.read
--http.timeout.write
--http.timeout.idle
--ws.rpcprefix
--bloomfilter.size

The following flags have been deprecated and will be removed in a future release.

--nousb                            USB defaults to off.  Use --usb to enable
--backtrace                        use --log.backtrace
--debug                            use --log.debug
--consoleformat                    use --log.json (true for JSON, false for Term output format)

Other Notable changes

• Merged upstream (go-ethereum) changes corresponding to versions v1.9.19-v1.9.25 (#1615) and v1.10.0-v1.10.7 (#1695). Please refer to go-ethereum release notes if you are interested in a detailed list of changes from this versions, but this includes Berlin and London EIPs.
• Add the commit that made the go-ethereum v1.10.8 a hot-fix (and was required a hardfork from our side) (#1739)

Docker Images

geth: us.gcr.io/celo-org/geth:1.5.0
geth-all: us.gcr.io/celo-org/geth-all:1.5.0

Celo-Blockchain Release 1.5.0-beta.1

v1.5.0-beta.1 is the Baklava-only release of v1.5.0. After testing on the Baklava testnet, it will be followed by v1.5.0-stable which will be intended for mainnet and Alfajores

The baklava activation block is 9195000 targeting an activation at 12:45 PM PDT on Wednesday December 15th.

The biggest and most important change in v1.5.0 is the implementation and activation of the Espresso hard fork with the following CIPS.

• CIP-43: Block Context
• CIP-47: Increased round change timer for early rounds in IBFT
• CIP-45: Relax canPayFee condition for non-native tokens
• CIP-50: Allow unprotected transactions

Relative to v1.4.0 version 1.5.0 has the following breaking changes

Please note that reverting to Celo blockchain v1.4.0 or prior after upgrading to v1.5.0 is not possible without a resync because the blockchain database layout has changed. Please take a backup of the data directory to be able to downgrade.

Flag Changes
The following previously deprecated flags have been removed.

--pprofport value                  use --pprof.port
--pprofaddr value                  use --pprof.addr
--memprofilerate value             use --pprof.memprofilerate
--blockprofilerate value           use --pprof.blockprofilerate
--cpuprofile value                 use --pprof.cpuprofile
--bootnodesv4                      use --bootnodes
--bootnodesv5                      use --bootnodes

The following flags have been removed

--vm.evm                           no substitute
--vm.ewasm                         no substitute
WHISPER (EXPERIMENTAL) OPTIONS
--shh                              no substitute
--shh.maxmessagesize value         no substitute
--shh.pow value                    no substitute
--shh.restrict-light               no substitute

The following flags have been added

--datadir.minfreedisk
--usb
--mainnet
--txlookuplimit
--light.nosyncserve
--cache.preimages
--http.rpcprefix
--ws.rpcprefix
--bloomfilter.size

The following flags have been deprecated and will be removed in a future release.

--nousb                            USB defaults to off. Use --usb to enable
--backtrace                        use --log.backtrace
--debug                            use --log.debug
--consoleformat                    use --log.json (true for JSON, false for Term output format)

Other:
We are aware of an issue when syncing with syncmode=light, but are releasing this to start testing the other changes for the hardfork.

Docker Images

geth: us.gcr.io/celo-org/geth:1.5.0-beta.1
geth-all: us.gcr.io/celo-org/geth-all:1.5.0-beta.1