Releasing reth_gnosis @ v1

Important Note: Upgrading to v1.0.0 from *ANY* previous version will need a database re-sync. The existing db will not work – you have to delete it manually and start from an empty datadir.

More details here: #101. This database format is expected to be stable starting from v1.

v1 adds several new features:

• Pre-merge history (including receipts and logs)
  • This is enabled via ERA file imports. Should you choose to import pre-merge history, you have to run import-era before starting your node for the first time. This allows RPC providers to serve pre-merge blocks and is not essential for validators.
  • Automatic ERA file imports are limited to Gnosis Chain and not currently available on Chiado.
• State files are now hosted in a more robust way instead of the previous Git LFS solution
• Upcoming Balancer hardfork – Spec
  • This hard fork specification introduces an irregular state change intended to recover funds stolen in the Balancer V2 hack in November 2025. Whether and when this specification is activated on Gnosis Chain depends on validator adoption and client configuration.

This release uses paradigmxyz/reth:v1.9.3 – so all Fusaka related logic is included as well.

Docker

docker pull ghcr.io/gnosischain/reth_gnosis:v1.0.0

What's Changed

• feat: support Gnosis primitives (full history 1 of 2) by @debjit-bw in #81
• feat: support Era Imports for Gnosis (full history 2 of 2) by @debjit-bw in #83
• refactor: use GnosisChainSpec directly instead of traitbounds by @debjit-bw in #92
• feat: implement Gnosis block execution ctx for header lookup by @debjit-bw in #93
• feat: Balancer hardfork spec - per block application by @debjit-bw in #95
• feat: use files hosted on cloudflare r2 instead of git lfs by @debjit-bw in #94
• chore: upgrade upstream reth@1.9.3 (fusaka-ready) by @debjit-bw in #97
• fix: Cargo.toml to use branch v1.9.3-gnosis for reth by @debjit-bw in #98
• Balancer Hardfork by @debjit-bw in #99

Full Changelog: v0.1.8...v0.1.9