From 7998961104aaefe467ced9eac53f1537fff85d20 Mon Sep 17 00:00:00 2001 From: Paul Lange Date: Mon, 23 Mar 2026 13:01:53 +0100 Subject: [PATCH 1/2] jovian: Update versions --- infra-partners/notices/jovian-upgrade.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/infra-partners/notices/jovian-upgrade.mdx b/infra-partners/notices/jovian-upgrade.mdx index a51608fe8..640cf0fc4 100644 --- a/infra-partners/notices/jovian-upgrade.mdx +++ b/infra-partners/notices/jovian-upgrade.mdx @@ -33,8 +33,8 @@ Node operators will need to upgrade to the respective Jovian releases before the 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) +- `op-geth` at [v2.2.1](https://github.com/celo-org/op-geth/releases/tag/celo-v2.2.1) +- `op-node` at [v2.2.1](https://github.com/celo-org/optimism/releases/tag/celo-v2.2.1) - `eigenda-proxy` at [v2.6.0](https://github.com/Layr-Labs/eigenda/releases/tag/v2.6.0) #### Updating the EigenDA proxy From eec10043b5cdb776420b25653107ddfcb964f9cf Mon Sep 17 00:00:00 2001 From: Paul Lange Date: Mon, 23 Mar 2026 14:07:36 +0100 Subject: [PATCH 2/2] jovian: Note index rebuild --- infra-partners/notices/jovian-upgrade.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/infra-partners/notices/jovian-upgrade.mdx b/infra-partners/notices/jovian-upgrade.mdx index 640cf0fc4..2dadca431 100644 --- a/infra-partners/notices/jovian-upgrade.mdx +++ b/infra-partners/notices/jovian-upgrade.mdx @@ -74,3 +74,11 @@ 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 + +### Notes + +#### Log Index Rebuild on Upgrade + +Nodes will perform a one-time log index rebuild on first start, visible as `Log +index head rendering in progress` in logs. This can take several hours as the +full chain history is processed. Subsequent restarts will not re-index.