Important
Hoodi node operators must upgrade before Mon, 26 Oct 2026, 17:42:48 UTC. This release removes the Glamsterdam fork from Hoodi. A Hoodi node still on 2.2.0 will activate Glamsterdam at that time and fork off the network. Your consensus client must also be on a release that removes the Glamsterdam fork from Hoodi.
Release notes
A patch release on top of 2.2.0 that removes the Glamsterdam (Amsterdam) fork from Hoodi, which was planned for Mon, 26 Oct 2026, 17:42:48 UTC (timestamp 1793036568).
The fork is on hold on Hoodi following the security concerns discussed on ACDE #248. A new date will come in a later release.
This is the only change. There are no database-format or configuration changes, so you can upgrade in place from any 2.2.x version. No other network is affected.
Overview
1 change since 2.2.0:
- Glamsterdam removed from Hoodi: Hoodi stays on BPO2 (fork hash
0x23aa1351) with no next fork announced (#15110)
What's Changed
- fix(specs): deschedule Hoodi Amsterdam fork by @stdevMac in #15110
- chore: update Directory.Build.props for 2.2.1 by @stdevMac in #15126
Full Changelog: 2.2.0...2.2.1
Build signatures
The packages are signed with the following OpenPGP key: AD12 7976 5093 C675 9CD8 A400 24A7 7461 6F1E 617E