Repository navigation
Summary
Fixes an incremental state root bug in reth (paradigmxyz/reth#28264) that can drop a newly inserted leaf and seal or accept a block with a wrong state root. All previous bera-reth releases are affected. No upstream reth release contains the fix yet, so bera-reth now builds on berachain/reth at commit 862aeff1, which is upstream v1.11.4 plus that single commit.
The fix does not change state execution, so patched and unpatched nodes agree on every block and this rolls out as a normal validator upgrade with no flag, config or datadir changes. Validators should upgrade promptly: every validator builds blocks, so the network is only protected once the validator set has moved.
Also included since v1.4.4: the mainnet bootnode list refresh (#282) and the dependency updates from the September audit fix (#286).
After restarting, confirm the node is signing again (height advancing, catching_up false). If beacond stays at one height logging "payload status is SYNCING", restart beacond and bera-reth together, then bera-reth once more. That is a known beacon-kit v1.4.1 restart behavior and unrelated to this fix. Verify the deployed build by its commit, 44ad965, not the version banner.
Update Priority
| User Class | Priority |
|---|---|
| Payload Builders | Required |
| Non-Payload Builders | Required |
All Changes
- fix(deps): pin reth fork with trie seek fix (#291)
- chore(ci): fix security audit and tx-sender failures (#286)
- chore(chainspec): align mainnet bootnodes with seed refresh (#282)
Binaries
The binaries are signed with the PGP key: 9B79 D302 7909 D094 3EFD DA8A A8A8 EF9C 940F AD3A
Bera-Reth
| System | Architecture | Binary | PGP Signature |
|---|---|---|---|
| x86_64 | bera-reth-v1.4.5-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
| aarch64 | bera-reth-v1.4.5-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
| aarch64 | bera-reth-v1.4.5-aarch64-apple-darwin.tar.gz | PGP Signature | |
| Docker | berachain/bera-reth | - |
