Releases: gcash/bchd
v0.22.0
This release adds support for the May 15, 2026 Bitcoin Cash network upgrade ("upgrade12"). All node operators must upgrade before activation to stay in consensus.
What's new
- CHIP-2021-05 — Bounded looping operations (
OP_BEGIN/OP_UNTIL) - CHIP-2025-05 Functions — Function definition and invocation (
OP_DEFINE/OP_INVOKE) - CHIP-2025-05 Bitwise — Re-enables
OP_INVERT,OP_LSHIFTNUM,OP_RSHIFTNUM,OP_LSHIFTBIN,OP_RSHIFTBIN - CHIP-2024-12 P2S — Pay-to-Script standardization
- VMB test vectors for all of the above
Activation
| Network | MTP activation |
|---|---|
| Mainnet / testnet3 / testnet4 | 2026-05-15 12:00 UTC |
| Chipnet | 2025-11-15 12:00 UTC (already active) |
| Regtest / simnet | always active |
Upgrade notes
- No database migration required.
- Pre-upgrade script types (P2PKH, P2SH20, P2SH32, etc.) continue to behave as before.
- Upgrade before May 15, 2026 to avoid consensus divergence.
Full Changelog: v0.21.1...v0.22.0
v0.21.1
v0.21.0
v0.20.0
v0.20.0-rc2
- Updated seeds to match BCHN and add newly restored BCHD seeds.
- Fixed syncing issue with nodes supporting sendaddrv2 messages.
- Fixed syncing testnet4 with SLP indexes.
v0.20.0-rc1
This is a huge milestone. Finally are back in consensus with the rest of the BCH ecosystem!
v0.19.0
v0.18.1
v0.18.0
This release is recommended for all users, and includes changes for the May 15th upgrade!
- Added full support for SLP tokens! This also includes SLP Graph Search!
- Updates standardness rules to allow multiple OP_RETURN outputs.
- Added
SignMuSigtobchecpackage. - Added basic prometheus support.
- Improved component shutdown logging.
- Fixed longstanding issue with unexpected shutdown recovery code.
- Minor fixes/improvements.
v0.17.1
This release is mostly a cleanup from the November hardfork. It hardcodes some of the difficulty adjustment parameters rather than calculating them on the fly. It also updates the checkpoints and fastsync utxo set. Finally it fixes a bug in the compact blocks code that was causing problems when connecting two bchd nodes together.
Note we recommend deleting the peers.json file found at .bchd/data/mainnet/peers.json before restarting as it might contain a number of ABC nodes that can make getting a good connection to the BCH network more difficult.