Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Migrating a Bitcoin Core Legacy Wallet to Descriptors
Bitcoin Core 25 migratewallet guide covering its experimental boundary, automatic legacy backup, encrypted wallets, split outputs, verification and rollback.
This guide explains Bitcoin Core migratewallet in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.
TL;DR
- What it is: Bitcoin Core 25.0 documented migratewallet as an experimental RPC for converting a legacy wallet to descriptor wallets. The command first creates a timestamped .legacy.bak file and returns its path.
- Why it matters: migratewallet is a custody-state transformation, not a formatting convenience. Completion means both backup paths restore, every returned wallet is reconciled and signing and watch-only boundaries match the original policy.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
What this means in simple English
Technical standards often describe several layers at once. This article separates the basic idea from the detailed rules so the practical meaning is clear.
Start with the simple explanation and current status. Use the later sections and primary sources only when you need more detail.
Simple example
Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Experimental status
The 25.0 RPC warns that it may not work as expected and may change. Run it only under a version-pinned migration plan with tested rollback.
Target selection
wallet_name is optional and defaults from the wallet RPC endpoint. If both are supplied they must match; confirm network, data directory and exact wallet before mutation.
Encryption
Encrypted wallets require the passphrase argument. Avoid shell history and shared logs, restrict RPC access and relock or stop the isolated environment immediately after the operation.
Automatic backup
Before conversion Core creates wallet-name plus timestamp and .legacy.bak in the wallet directory. Copy it to protected independent storage and prove restorewallet can read it.
Split wallets
The response names the primary descriptor wallet and can name watch-only and solvable companion wallets. Reconcile descriptors, address books, balances, UTXOs and labels across all outputs.
New backup
Official documentation says a new wallet backup is needed after migration. Preserve the migrated descriptor state, origins, ranges and next indexes, not only the legacy backup.
Acceptance
Compare chain tip, transactions, spendability, receive and change derivation, watch-only flags and signing. Restore both legacy and migrated backups in isolated test nodes before approval. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is Migrating a Bitcoin Core Legacy Wallet to Descriptors?
Bitcoin Core 25.0 documented migratewallet as an experimental RPC for converting a legacy wallet to descriptor wallets. The command first creates a timestamped .legacy.bak file and returns its path.
Is Migrating a Bitcoin Core Legacy Wallet to Descriptors active or supported today?
Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Why does Migrating a Bitcoin Core Legacy Wallet to Descriptors matter?
migratewallet is a custody-state transformation, not a formatting convenience. Completion means both backup paths restore, every returned wallet is reconciled and signing and watch-only boundaries match the original policy.
Do beginners need to use the technical details?
No. The opening explanation and questions cover the main idea. The detailed sections are available for readers who need to go further.
Conclusion
migratewallet is a custody-state transformation, not a formatting convenience. Completion means both backup paths restore, every returned wallet is reconciled and signing and watch-only boundaries match the original policy.
Primary sources
- Bitcoin Core 25.0 migratewallet RPC
- Bitcoin Core 25.0 release notes
- Bitcoin Core descriptor documentation
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 explained in detail: its seven consensus restrictions, 55% signalling threshold, chain-split risk and August 2026 closure.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.