Skip to content

Update Jovian Notice #2148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
palango merged 1 commit into from
Mar 12, 2026
Merged

Update Jovian Notice #2148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 43 additions & 5 deletions infra-partners/notices/jovian-upgrade.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,12 @@ title: "Jovian Hardfork"
This page outlines changes related to the Jovian Upgrade for node operators.

<Note>
This page will be kept updated with key information about the upgrade. Activation timestamps will be announced soon.
This page will be kept updated with key information about the upgrade.

- Celo Sepolia testnet activation: TBD
- **Mainnet** activation: TBF
- 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`
</Note>

## What is the Jovian Hardfork?
Expand All @@ -25,10 +27,46 @@ For the full technical specification, see the [Jovian upgrade spec](https://spec

## For Node Operators

Software versions will be announced ahead of the activation date. Check back for updates.
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.

- `op-geth` at [v2.2.0](https://github.com/celo-org/op-geth/releases/tag/celo-v2.2.0)
- `op-node` at [v2.2.0](https://github.com/celo-org/optimism/releases/tag/celo-v2.2.0)
- `eigenda-proxy` at [v2.6.0](https://github.com/Layr-Labs/eigenda/releases/tag/v2.6.0)

#### 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
- Sepolia: [`0xf4f934A0b5c09d302d9C6f60040754fEebdd6073`](https://sepolia.etherscan.io/address/0xf4f934A0b5c09d302d9C6f60040754fEebdd6073)
- Mainnet: TBD
- `--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`

<Tip>
**Docker Compose**

The required configuration for each service can be found in our [Docker Compose Setup](https://github.com/celo-org/celo-l2-node-docker-compose), where every network has a corresponding `<network>.env` file.
The configuration for each service can be found in our [Docker Compose Setup](https://github.com/celo-org/celo-l2-node-docker-compose), where every network has a corresponding `<network>.env` file.
</Tip>

### 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
Loading