Releases: Layr-Labs/nitro
v3.9.0 with ArbOS 50 support
Nitro v3.9.0 with eigenDA integration
Containers: nitro-node, nitro-node-dev
Compatible Upstream Version: v3.9.0
Rebase onto upstream Arbitrum Nitro v3.9.0 with EigenDA integration.
What's changed
- Upstream v3.9.0 rebase: Merged all upstream improvements while preserving EigenDA functionality
- API compatibility: Updated for v3.9.0 changes (Promise API, AdvanceStateByBlock, etc.)
- Consensus machine: Using
consensus-eigenda-v50(0x54c6ce94...) as latest WASM module
Docker Image
docker pull ghcr.io/layr-labs/nitro/nitro-node:v3.9.0Full Changelog: v3.8.0...v3.9.0
EigenDA Consensus v50
EigenDA consensus machine for arbOS v50
Module Root: 0x54c6ce94cc0ca6dd16e931e782f612c094163fac83845f719dea100489073745
Files:
machine.wavm.br- Main consensus machine artifactreplay.wasm- Replay binary
v3.8.0
Containers: nitro-node, nitro-node-dev
Compatible Upstream Version: v3.8.0
Merge upstream v3.8.0 (62c0aa7) into eigenda branch | Previous: v3.8.0-rc.16
What's Changed
- Merge upstream v3.8.0
Full Changelog: v3.8.0-rc.16...v3.8.0
v3.8.0-rc.16
Merge upstream v3.8.0-rc.16 into eigenda branch.
Containers: nitro-node, nitro-node-dev
Compatible Upstream Version: v3.8.0-rc.16
What's Changed
- Merge upstream v3.8.0-rc.16 in 8786a4b
Full Changelog: v3.8.0-rc.12...v3.8.0-rc.16
v3.8.0-rc.12
Merge upstream v3.8.0-rc.12 into eigenda branch.
Containers: nitro-node, nitro-node-dev
Compatible Upstream Version: v3.8.0-rc.12
What's Changed
- Merge upstream v3.8.0-rc.12 in 7165f5c
Full Changelog: v3.8.0-rc.7...v3.8.0-rc.12
v3.8.0-rc.7
Containers: nitro-node, nitro-node-dev
Compatible Upstream Version: v3.8.0-rc.7
What's Changed
- Merge upstream v3.8.0-rc.7 with history by @ethenotethan in #128
Full Changelog: v3.7.4...v3.8.0-rc7
v3.7.6: EigenDA Support
Containers: nitro-node, nitro-node-dev
Compatible Upstream Version: v3.7.6
Release Summary
Incorporates upstream v3.7.6 and adds a downstream runbook articulating the wasm root generation process.
What's Changed
- feat: Devops runbook by @ethenotethan in #126
- Merge upstream v3.7.6 by @ethenotethan in #132
Full Changelog: v3.7.4...v3.7.6
v3.7.4: Support ArbOS50 Alpha (still no BoLD x EigenDA)
Containers: nitro-node, nitro-node-dev
Compatible Upstream Version: v3.7.4
Release Summary
Incorporates upstream v3.7.4 and adds a new ArbOS50 alpha consensus artifact. EigenDA V1 integration is still incompatible with BoLD proving.
What's Changed
- merge
upstream/v3.7.4by @ethenotethan in #121 - chore: Update V50-alpha.1 consensus root reference in Dockerfile by @ethenotethan in #124
Full Changelog: v3.6.4...v3.7.4
Consensus EigenDA V50-alpha.1
WAVM Module Root: 0x34454ede1b5edaee4c5d6c5ccebb20d5cc15d71cf662525be089a60925865ed0
This consensus release supports ArbOS 50-alpha.1 w/ EigenDA.
v3.6.4: Support ArbOS40 without BoLD Proving
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
EigenDAconfiguration 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
- V3.6.4 merge by @litt3 in #88
- fix: Max Size Check w/ EigenDA by @ethenotethan in #93
- chore: Cherry pick changes made in v3.5.6 && v3.5.7 releases by @ethenotethan in #110
- feat: updated fork summary for v3.6.4 with minor cleanups by @ethenotethan in #111
- feat: BoLD Inbox Challenge Test with EigenDA by @ethenotethan in #112
- feat: BoLD Challenge Test for EigenDA by @ethenotethan in #113
- fix: Use Foundry v1.0.0 in CI by @ethenotethan in #116
- fix: eigenda cfg ingestion via CLI by @ethenotethan in #117
- feat: Support ArbOS40 Download in
nitro-nodeDocker Image by @ethenotethan in #118
New Contributors
Full Changelog: v3.5.3...v3.6.4