Reth v2.8.1 removes the Amsterdam activation from Hoodi, which has been cancelled: https://blog.ethereum.org/2026/10/16/glamsterdam-hoodi-announcement
- Unscheduled the Amsterdam hardfork on Hoodi: bumped
alloy-hardforksto 0.4.11, which drops Amsterdam from the Hoodi schedule (alloy-rs/hardforks#113), so Hoodi stays on BPO2 (#28089).
Action Required
Hoodi operators must upgrade before 26 October 2026 at 17:42:48 UTC, the activation time v2.8.0 scheduled. A v2.8.0 node on Hoodi would activate Amsterdam at that timestamp and fork off the network.
Backwards Compatibility
Important
v2.8.1 makes no database changes. You can downgrade to v2.8.0, but on Hoodi that version still activates Amsterdam.
Update Priority
| User Class | Priority |
|---|---|
| Payload Builders | High on Hoodi, Low elsewhere |
| Non-Payload Builders | High on Hoodi, Low elsewhere |
All Changes
- fix: unschedule Hoodi Amsterdam activation (#28089)
- chore: release 2.8.1
Binaries
See pre-built binaries documentation.
The binaries are signed with the PGP key: 50FB 7CC5 5B2E 8AFA 59FE 03B7 AA5E D56A 7FBF 253E
Reth
| System | Architecture | Binary | PGP Signature |
|---|---|---|---|
| x86_64 | reth-v2.8.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
| aarch64 | reth-v2.8.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
| aarch64 | reth-v2.8.1-aarch64-apple-darwin.tar.gz | PGP Signature | |
| Docker | paradigmxyz/reth | - |