Skip to content

v3.6.4: Support ArbOS40 without BoLD Proving

Choose a tag to compare

@ethenotethan ethenotethan released this 03 Sep 17:06
· 3765 commits to eigenda since this release
42e1773

Containers: nitro-node, nitro-node-dev
Replay Artifact: consensus-eigenda-v40

Release Summary

This release rebases (technically merges) the upstream Nitro v3.6.4 change set. While this version of Nitro includes support for Arbitrum BoLD, BoLD proving is not currently supported since nitro-contracts have not yet been upgraded to the v3.0.0 series. For now, all EigenDA chains will continue to use the "legacy" validator.

In addition, this release introduces a patch for CLI ingestion along with minor updates.

CLI Ingestion Patch

Previously, the EigenDA configuration struct in the core node config could only be set through config files, as it was not wired through CLI dependency injection. PR #117 resolves this by:

  • Adding CLI support for EigenDA configuration fields.
  • Introducing a hot-loading policy consistent with other DA config types.

BoLD Testing for EigenDA

Although BoLD proving is not yet enabled, we have extended the existing BoLD challenge test suite to cover EigenDA-specific inbox messages.

This ensures proper one-step proof resolution for EigenDA message types, which is critical since these messages use custom preimage fields when computing hashes. These hashes are persisted in the storage accumulator and referenced during ReadInboxMessage opcode dispute resolution.

This provides an additional layer of assurance ahead of full BoLD support (assuming we every fully support for BoLD for EigenDA V1 given medium term deprecation for EigenDA V2).

NOTE: Properly upgrading to this version requires updating the wasm module root on your parent chain, this can be done via calling your Rollup contract's setWasmModuleRoot method via your UpgradeExecutor contract.

What's Changed

New Contributors

  • @litt3 made their first contribution in #88

Full Changelog: v3.5.3...v3.6.4