Bitweb Core 31.1 is now available. This release updates the Bitweb codebase to the Bitcoin Core 31.x upstream, bringing all improvements, bug fixes, and protocol enhancements from that series.
⚠️ IMPORTANT! ALWAYS BACK UP YOUR WALLET DATA BEFORE ANY UPDATE. Shut down your wallet completely, then copy your
wallet.datfile to a safe place before updating. If possible, always encrypt your wallet with a strong password.
⚠️ Cross-chain migration removed in 31.1
Bitweb Core 31.1 no longer contains the cross-chain wallet migration code.
If you are still running a wallet from the old Bitweb chain (pre-30.3), you must migrate using Bitweb Core 30.3.1 before upgrading to 31.1. Once your wallet has been successfully migrated and rescanned on the 30.x chain, you can then upgrade to 31.1 safely.
Migration path:
Old chain wallet → Bitweb Core 30.3.1 (migrate) → Bitweb Core 31.1
See the 30.3.1 release post for full migration instructions.
Upgrade from 30.3 or 30.3.1
If you are already running Bitweb Core 30.3 or 30.3.1 on the current chain with a migrated wallet, upgrading to 31.1 is straightforward:
- Shut down your node completely.
- Back up your
wallet.datto a safe location outside the data directory. - Install Bitweb Core 31.1.
- Start the node — it will continue syncing from where it left off.
No rescan or migration is required when upgrading from 30.3.x (assuming your wallet was already migrated during the 30.3 upgrade).
What's new in 31.x
This release brings all upstream improvements from Bitcoin Core 31.x, including performance enhancements, P2P networking improvements, and wallet and RPC refinements. See the release notes on GitHub for the full changelog.
Troubleshooting
- Node won't start after upgrade — ensure your wallet was already migrated using 30.3.1. If you skipped migration, downgrade to 30.3.1, complete migration, then upgrade again.
- Balance shows zero after upgrade — run
bitweb-cli rescanblockchainto rescan the chain. - "walletcrosschain" option not recognized — this option has been removed in 31.1.
Remove it from
bitweb.confbefore starting the node.
Issues or questions? Use the issue tracker or join the community on the resources page.