Bitweb Core 30.3.1 — Bitcoin 30.x Backport Patches

Bitweb Core 30.3.1 is now available. This is a patch release that backports fixes and improvements from the Bitcoin Core 30.x branch onto the Bitweb 30.x codebase.

⚠️ IMPORTANT! ALWAYS BACK UP YOUR WALLET DATA BEFORE ANY UPDATE. Shut down your wallet completely, then copy your wallet.dat file to a safe place before updating. If possible, always encrypt your wallet with a strong password.

What's included

This release cherry-picks stability and correctness patches from the upstream Bitcoin Core 30.x series. No consensus changes are introduced. The update is recommended for all node operators running 30.3.

Upgrade from 30.3

If you are already running Bitweb Core 30.3 on the current chain, upgrading is straightforward:

1. Shut down your node completely.
2. Back up your wallet.dat to a safe location outside the data directory.
3. Install Bitweb Core 30.3.1.
4. Start the node — it will continue syncing from where it left off.

No rescan or wallet migration is required when upgrading from 30.3.

Wallet migration (upgrading from a pre-30.3 chain)

If you are migrating from the old Bitweb chain (pre-30.3), this release still includes the full cross-chain wallet migration tooling. Follow the steps below.

Note: Cross-chain migration support is present in 30.3.1. It will not be available in the next major release (31.1). If you need to migrate an old wallet, do so using 30.3 or 30.3.1 before upgrading to 31.x.

Step 1 — Back up your wallet

Shut down your old node completely. Copy wallet.dat to a safe location outside the data directory. Keep this backup — you will need it below.

Step 2 — Install and sync

Download and install Bitweb Core 30.3.1. Start the node and let it fully sync the new chain from scratch, then shut it down.

Which wallet type do I have?

Run this on your old node before shutting it down:

bitweb-cli getwalletinfo

• If "descriptors": true → follow Step 3a
• If "descriptors": false → follow Step 3b

Step 3a — Descriptor wallet

Copy your backed-up wallet.dat into the new data directory, then enable cross-chain import.

Add to bitweb.conf:

walletcrosschain=1

Or use the command-line flag:

bitwebd -walletcrosschain

GUI users: Start the node → File → Open Wallet → select your wallet. Rescan starts automatically. Wait for it to complete before checking your balance.

CLI users:

bitweb-cli loadwallet "your-wallet-name"
bitweb-cli rescanblockchain

Step 3b — Legacy wallet

Copy wallet.dat into the new data directory, enable walletcrosschain (same as 3a above), then run:

bitweb-cli migratewallet "your-wallet-name"
bitweb-cli rescanblockchain

We strongly recommend creating a new native descriptor wallet and transferring all coins there.

After migration

Once migration is complete, remove walletcrosschain=1 from bitweb.conf.

Troubleshooting

• "Unexpected application id" error — ensure you are using the 30.3.1 binary, not an older one.
• Balance shows zero after rescan — wait for the rescan to fully complete: bitweb-cli getwalletinfo → check the "scanning" field.

Issues or questions? Use the issue tracker or join the community on the resources page.