Hi everyone!
The Fusaka hardfork will be activated on Ethereum in the next couple of days, and we’ve received a lot of questions about it. The goal of this post is to clarify the most common ones.
Do we need to update the Celo client before the HF?
No. You only need to verify that the L1 RPC endpoint your nodes use is compatible with the Fusaka hardfork. (RPC providers should already be compatible.)
What about the Jovian HF from Optimism?
We are not releasing a new version with that fork yet. Our current focus is deploying Succinct on Celo next week. For this update, node operators will not need to update anything.
At the beginning of Q1 2026 (exact date TBD), we will publish and announce a new client version that includes Jovian HF activation.
Do we need to update the eigenda-proxy version?
It is not required to update it now. As some of you have noticed, the eigenda-proxy repo is deprecated (with v1.8.2 being the last release—and the one we currently use).
It is technically possible to upgrade to v2.4.1 from EigenDA monorepo, and it should work with our setup using the appropriate parameters. However, since we will require everyone to update their client once we release the version that includes the Jovian HF, we prefer to provide one unified update with proper instructions for all related services (including full parameter details), rather than multiple staggered updates.
As a note: we will use the same Jovian HF activation block to also switch the batcher to Eigenda’s v3 verification.
TL;DR
Just make sure your L1 endpoints are compatible with Fusaka, and wait for our Q1 communication for the next round of updates.
Thanks for your attention,
The cLabs team