Skip to main content

​
Isthmus

If you reached the hardfork block before upgrading to v2.1.0 your node can get stuck.This can be resolved by upgrading both op-geth and op-node to v2.1.0, stopping op-node, rewinding the op-geth head to before the hardfork and starting op-node again.To rewind the head you can use:
cast rpc -r <op-geth-node-address> debug_setHead 49908270

​
Mainnet

A couple of issues could be causing this.
  • If you are running multiple instances of op-node, make sure to check that they each have a unique and persisted private key at --p2p.priv.path
  • Ensure that your node is accessible to other nodes, check the Configure P2P for external network access section under Running a full node
See the guides for running a node or the guide on how to migrate an L1 node.
Yes. This is part of running a node. If you’re using the Docker Compose Setup, it’s included.
All balances have been carried over to the L2, unchanged.
There is no change and it continues to work in the same way as before.
Yes, same as with Ethereum.
Validators are becoming Community RPC providers.
There are multiple options.
Governance remains a pillar of the Celo blockchain. The Validator Hotfix process has been adapted, see Updated Governance Hotfix for the changes.
The block period is 1 second.
The gas limit per block is 30 million, so the maximum throughput is 30M gas/s.
See What’s Changed Celo L1 -> L2 and L1 -> L2 Migration Changes in the spec for greater detail.

​
Testnets

Dango was a short-lived testnet forked from Alfajores at block 24940100 to test the migration to L2. It was shut down in October 2024.Alfajores is a long running Celo network testnet that was launched in July 2019 and upgraded to L2 in September 2024.See the Alfajores network info here.
⌘I