Jovian Hardfork Live on Celo Mainnet

Announcements
1

Dear Celo community,

The Jovian hardfork is now live on Celo Mainnet.

Jovian activated on Tuesday, March 31, 2026 at 12:06:28 UTC (timestamp 1774958788), marking the latest step in Celo’s continued alignment with the OP Stack while preserving the network’s unique extensions and real-world payments focus.

This upgrade follows successful activation on Celo Sepolia and brings a set of improvements that strengthen protocol compatibility, improve gas accounting behavior, and prepare Celo for upcoming infrastructure advancements across the broader Ethereum and OP Stack ecosystem.

What’s Included in Jovian

The Jovian hardfork adopts features from Optimism’s latest upgrade path alongside several Celo-specific improvements, including:

  • Transfer Precompile Address Warming to align with standard EVM behavior and improve gas accounting consistency
  • Minimum Base Fee Transition, moving from Celo’s custom gas price floor to Optimism’s configurable minimum base fee model
  • Fusaka readiness, improving compatibility with upcoming Ethereum and OP Stack changes
  • EigenDA proxy upgrade to support the latest trustless integration and newer EigenDA protocol versions

Together, these changes improve compatibility, simplify future maintenance, and help ensure Celo remains aligned with the evolving OP Stack roadmap while continuing to support core Celo innovations like fee abstraction and token duality.

For the full technical specification, see the Jovian upgrade documentation.

For Bridges and Users

Celo’s Jovian hardfork includes Optimism Upgrade 16. This update requires a one-time invalidation of all pending withdrawal proofs created on L1. Any pending withdrawals before the update need to submit a second withdrawal proof transaction on L1.

This invalidation does not place any ETH or ERC-20 tokens at risk.

For Node Operators and Infrastructure Partners

Node operators, RPC providers, indexers, bridge providers, and other infrastructure partners should now confirm that their systems are running the required Jovian-compatible releases.

The required releases for Jovian include:

Important: EigenDA Proxy Configuration Changes

Jovian increases the minimum EigenDA proxy version to v2.6.0, which requires configuration updates.

Set the following flags

  • --eigenda.v2.network to either mainnet or sepolia_testnet
  • --eigenda.v2.cert-verifier-router-or-immutable-verifier-addr to the CertRouter contract on the corresponding L1
  • --apis.enabled to "op-generic,op-keccak,standard,metrics"
  • Remove the following flags if they are set
    • --eigenda.signer-private-key-hex
    • --eigenda.v2.disperser-rpc
    • --eigenda.v2.cert-verifier-addr
    • --eigenda.v2.eigenda-directory
    • --eigenda.v2.signer-payment-key-hex
    • --eigenda.v2.service-manager-addr
    • --eigenda.v2.bls-operator-state-retriever-addr
    • --eigenda.g1-path
    • --eigenda.g2-path
    • --eigenda.g2-path-trailing

For Docker Compose users, reference configurations are available in the Celo L2 Docker Compose repository.

Post-Activation Verification

Operators should verify the following after activation:

  • op-node logs show the correct Jovian activation time
  • op-geth logs show the correct Jovian activation time
  • EigenDA proxy is updated to v2.6.0 with the required new flags
  • Services have resumed normal operation and are syncing as expected

Upon initial startup, nodes will perform a one-time log index rebuild. This process is visible in the logs as Log index head rendering in progress and may require several hours as the full chain history is processed. Subsequent restarts will not trigger a re-index.

Questions

If you have any questions or need support following the upgrade, please reply here or reach out in the usual channels.

The cLabs team

4 Likes