Hello Validators and Node Operators,
In light of the chain split on Ethereum today as reported by Geth Core Developer Marius Van Der Wijden here, and the troubles being seen on other EVM networks, our solution remains to fix this in the E-Hardfork as explained in our original statement on the Geth 1.10.8 patch here.
As we explained there, the bug fixed in go-ethereum v1.10.8 affects smart contract execution in an extreme edge case, and therefore can be rolled out safely on the next hard fork, to ensure that all nodes agree on when the new rules come into effect.
Rolling out the fix without the hard-fork mechanism (which is what was done on some other EVM networks) can produce a consensus failure (due to different nodes using different rules) and is therefore unsafe. In the case of Celo due to IBFT consensus, such a consensus failure could result in a network stall rather than a chain split.
In the case of Ethereum, using a hard fork would not have helped, because they have multiple client implementations and therefore already had different nodes using different rules no matter which course of action was followed.
Given that fixing it safely requires a hard fork there were two options: an emergency hard fork or including it in the next regular hard fork. As explained in the forum post, we chose the second option due to the bug only affecting contracts specifically crafted to trigger it.
Feel free to reach out to the cLabs Blockchain team, either on this forum post or on Celo’s Discord server.
Thank you for keeping the Celo network secure.
The cLabs Team