Skip to main content
This page outlines changes related to the Jovian Upgrade for node operators.
This page will be kept updated with key information about the upgrade.
  • Celo Sepolia testnet activation: Tue, Mar 17, 2026, 12:03:57 UTC
    • Activation timestamp: 1773749037
  • Mainnet activation: Tue, Mar 31, 2026, 12:06:28 UTC
    • Actvation timestamp: 1774958788

​
What is the Jovian Hardfork?

The Jovian Hardfork adopts features from Optimism’s Jovian hardfork along with Celo-specific improvements focused on gas accounting and base fee alignment. Key changes include:
  • Transfer Precompile Address Warming: The transfer precompile now warms from and to addresses during execution, aligning with standard EVM behavior and ensuring correct gas accounting for subsequent operations on the same address.
  • Minimum Base Fee Transition: Celo moves from its own gas price floor mechanism to Optimism’s configurable Minimum Base Fee standard, maintaining a cost floor while aligning with OP Stack conventions. For the full technical specification, see the Jovian upgrade spec.
  • L1 Fusaka Upgrade: Celo now includes improvements to handle the L1 Fusaka upgrade, leading to better compatibility with the Optimism stack. For more details see OP Fusaka upgrade notice.
  • EigenDA upgrade: The EigenDA proxy is upgraded to a recent version which improves the trustless integration and allows switching to the latest EigenDA protocol version.

​
For Node Operators

Node operators will need to upgrade to the respective Jovian releases before the activation dates.

​
Update to the latest release

The release contains the activation timestamps for Celo Mainnet and Celo Sepolia testnet.

​
Updating the EigenDA proxy

The Jovian hardfork also increases the minimum EigenDA proxy version to v2.6.0. This update requires some changes to the configuration:
  • 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.signer-payment-key-hex
    • --eigenda.v2.service-manager-addr
    • --eigenda.v2.bls-operator-state-retriever-addr
Docker ComposeThe configuration for each service can be found in our Docker Compose Setup, where every network has a corresponding <network>.env file.

​
Verify Your Configuration

Make the following checks to verify that your node is properly configured.
  • op-node and op-geth will log their configurations at startup
  • Check that the Jovian time is set correctly in the op-node startup logs
  • Check that the Jovian time is set correctly in the op-geth startup logs