Bitweb Core 30.3 — Network Restart & Wallet Migration

Bitweb Core 30.3 is now available. This release restarts the Bitweb network with a new chain and updates to the latest Bitcoin Core 0.30.x codebase. The old chain is abandoned.

Back up your wallet before doing anything. Shut down your wallet completely, copy wallet.dat to a safe location outside the data directory. Encrypt your wallet with a strong password if you haven't already. Encrypted wallets survive migration without issues — migration only updates a file header field (SQLite application_id, bytes 68–71) separate from encrypted key data.

Step 1 — Back up your wallet

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

Step 2 — Install and sync the new version

Download and install Bitweb Core 30.3. Start the node and let it fully sync the new chain from scratch (this may take time). Then shut it down before proceeding.

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 (most users)

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 (extra step required)

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 moving all coins there. The node supports only descriptor wallets going forward.

Importing private keys (optional)

If you need to import an old WIF private key:

bitweb-cli getdescriptorinfo "combo(YOUR_WIF_KEY)"

Note the checksum from the output, then import:

bitweb-cli importdescriptors '[{"desc":"combo(YOUR_WIF_KEY)#CHECKSUM","timestamp":"now"}]'
bitweb-cli rescanblockchain

Troubleshooting

• "Unexpected application id" error — ensure you are using the 30.3 binary, not the old one.
• Balance shows zero after rescan — wait for rescan to fully complete. Check progress: bitweb-cli getwalletinfo → look for the "scanning" field.
• Remove the flag after migration — once migration is done, remove walletcrosschain=1 from bitweb.conf.

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