List of Upgrades
BitNet Upgrade History (Mainnet & Testnet)
This section outlines all historical upgrade events for BitNet’s mainnet and testnet environments, including planned upgrades, breaking changes, and special upgrade instructions.
Each version is listed with the following flags:
Planned: Scheduled through governance
Breaking: Requires state or genesis migration
Data Reset: Full node data reset needed
Manual Only: Requires node operator action (no automatic upgrade path)
🛰️ Mainnet Upgrade Summary
v18.1.0
✅
✅
❌
❌
21,209,000
v18.0.0
✅
✅
❌
❌
20,396,852
v17.0.0
✅
✅
❌
❌
20,101,000
v16.0.0
✅
✅
❌
❌
18,295,000
v15.0.0
✅
✅
❌
❌
16,946,771
v14.1.0
✅
✅
❌
❌
16,105,000
v13.0.2
✅
✅
❌
❌
14,538,200
v12.1.0
✅
✅
❌
❌
12,303,000
v11.0.0
✅
✅
❌
❌
10,561,414
v10.0.0
✅
✅
❌
❌
9,495,000
v9.1.0
✅
✅
❌
❌
6,654,000
v8.2.0
✅
✅
❌
✅
4,888,000
v7.0.0
✅
✅
❌
✅
2,476,000
Testnet Upgrade Summary
v18.0.0
✅
✅
❌
❌
22,933,646
v17.0.0
✅
✅
❌
❌
22,541,000
v16.0.0-rc5
✅
✅
❌
❌
20,017,000
v14.0.0-rc2
✅
✅
❌
❌
16,554,500
v13.0.0
✅
✅
❌
❌
15,374,000
v10.0.0-rc1
✅
✅
❌
❌
8,700,000
v8.2.3
✅
✅
❌
❌
8,037,000
v6.0.1
✅
✅
❌
❌
2,176,500
v4.0.1
✅
✅
❌
❌
1,200,000
Notes for Validators
Breaking upgrades: Require careful coordination and state migrations.
Manual upgrades: These must be installed directly by node operators — cosmovisor or other automated tooling won’t handle them.
Upgrade heights: Ensure your node halts and updates before reaching the listed height to prevent consensus issues or downtime.
Last updated