Skip to content

Bitweb Core 30.3.1

Choose a tag to compare

View all tags
@mraksoll4 mraksoll4 released this 26 Jun 05:53
Immutable release. Only release title and notes can be modified.
v30.3.1
This tag was signed with the committer’s verified signature.
mraksoll4 mraksoll
GPG key ID: 35A7538B1C816E49
Verified
Learn about vigilant mode.
0dd1369
This commit was signed with the committer’s verified signature.
mraksoll4 mraksoll
GPG key ID: 35A7538B1C816E49
Verified
Learn about vigilant mode.

This Release is a Backport of fixes from the Latest Bitcoin 0.30.x branch.

Caution

ALWAYS BACK UP YOUR WALLET DATA BEFORE ANY UPDATE. SHUTDOWN WALLET COMPLETELY,
THEN COPY YOUR wallet.dat FILE TO A SAFE PLACE BEFORE UPDATING.
IF POSSIBLE — ALWAYS ENCRYPT YOUR WALLET WITH A STRONG PASSWORD!

Caution

IF YOU HAVE AN OLD WALLET — DO NOT SKIP THIS RELEASE!
The 30.x branch is the LAST release that contains wallet migration code.
Starting from 31.1, migration code has been removed as part of refactoring.
You MUST download this release first, migrate your wallet, and only then update to newer versions.
If you skip this step and update directly to 31.1+, you will NOT be able to migrate your old wallet.

IMPORTANT: Wallet Migration Required

This release restarts the Bitweb network with a new chain and denomination
change. The old chain is abandoned. You must migrate your wallet before use.
ALWAYS BACK UP wallet.dat BEFORE doing anything.

Step 1 - Back up your wallet

Shutdown your old Bitweb node completely, then copy wallet.dat to a safe
location outside the data directory.

If your wallet is encrypted, it will survive migration without any issues.
The migration only updates a file header field (SQLite application_id,
bytes 68-71) that is separate from encrypted key data.

Step 2 - Install new version and sync

Download the latest release and start the node. Let it fully sync the new
chain from scratch. This may take time. Then Shutdown.

Step 3a - Descriptor wallet (most users)

GUI users:

  1. Copy your backed-up wallet.dat into the new data directory.
  2. Add to bitweb.conf:
walletcrosschain=1

or run:

bitwebd -walletcrosschain
  1. Start Node.
  2. In the Bitweb GUI go to File -> Open Wallet.
  3. Select your wallet when prompted.
  4. The node will import it and start a rescan automatically — do a full rescan!
  5. Wait for the rescan to complete before checking your balance.

Node / CLI users (no GUI):

Place wallet.dat in the new data directory, then run:

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

Wait for the rescan to complete.

Step 3b - Legacy wallet (additional step required)

If you used a legacy (non-descriptor) wallet, you must run the migration
command after placing wallet.dat in the new data directory and starting the node.

Add to bitweb.conf:

walletcrosschain=1

or run:

bitwebd -walletcrosschain

Then migrate:

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

How do I know which wallet type I have?

Run this on your OLD node before shutting it down:

bitweb-cli getwalletinfo
  • If "descriptors" is true → Step 3a
  • If "descriptors" is false → Step 3b

We also strongly recommend creating a new native descriptor wallet and moving all coins there.
Node only supports descriptor wallets from now on.

Also if you need to import an old private key

getdescriptorinfo "combo(wif)"

Get the checksum, then:

importdescriptors '[{"desc":"combo(wif)#checksum","timestamp":"now"}]'

And do:

rescanblockchain

Troubleshooting

  • "Unexpected application id" error — make sure you are using this release, not the old binary.
  • Balance shows zero after rescan — wait for rescan to fully complete. Check progress with bitweb-cli getwalletinfo (look for the "scanning" field).
  • Do not use -walletcrosschain flag after migration is done. Remove it from bitweb.conf once migration is complete.
Assets 23
Loading