A mnemonic is the master backup for a Bitcoin wallet, but a mnemonic alone does not always restore the same wallet view. Blockstream Jade can use different script types, derivation paths, passphrases, and multisig policies. A script-assisted recovery is therefore less about cracking a wallet and more about reconstructing the exact wallet metadata that Jade used. This guide explains a safe, offline workflow for legitimate owners who need to recover access to their own Jade wallet.

Security first: Work offline, use a trusted open-source tool, and never paste a real mnemonic into a website, chat, cloud note, or unknown script. If the funds are significant, test the workflow with a small amount or on testnet first.

What Jade mnemonic script recovery really means

Jade stores or restores a BIP39 mnemonic. That mnemonic becomes a seed, and the seed becomes a BIP32 master key. From there, a derivation path and a script type determine which Bitcoin addresses belong to the wallet. A recovery script simply automates the deterministic steps:

  1. Validate the mnemonic checksum.
  2. Convert the mnemonic and optional passphrase into a seed.
  3. Derive the correct account, change, and address keys.
  4. Generate addresses or a descriptor.
  5. Compare those addresses with known Jade addresses or balances.
  6. Import the descriptor into a trusted watch-only wallet and sweep funds if needed.

The hard part is not the math. The hard part is choosing the same parameters Jade used when the wallet was created.

Before you start: a practical safety checklist

  • Use an air-gapped computer or a live Linux USB with networking disabled.
  • Prefer well-reviewed open-source tools such as Bitcoin Core, Sparrow Wallet, Electrum, or a small script built on a maintained BIP39/BIP32 library.
  • Keep the mnemonic on paper or metal. Do not photograph it or store it in a password manager.
  • Record the Jade firmware version, wallet type, and any passphrase you used.
  • If the wallet is multisig, collect the other xpubs and the threshold before deriving addresses.

BIP39 recovery

  • Never send recovered funds to an address generated by an untrusted script. Generate the destination address in a trusted wallet.

Step 1: Verify the mnemonic offline

Start by checking the BIP39 checksum and word count. A valid Jade backup is usually 12 or 24 words, though 15, 18, and 21 words are also possible in BIP39. A checksum error usually means a transcription mistake, not a damaged wallet.

If you use a script, keep it minimal and readable. The script should accept the mnemonic from a local file or standard input, not from a command-line argument that may be saved in shell history. It should print only public information such as the master fingerprint, xpub, and derived addresses.

Step 2: Match Jade's script type and derivation path

Jade can create or restore several common single-signature wallet types. The same mnemonic will produce different addresses under different paths. Use the table below as a starting point, then confirm against your own records or a known Jade address.

| Wallet type | Common derivation path | Address format |
|---|---|---|
| Legacy | m/44h/0h/0h | P2PKH |
| Nested SegWit | m/49h/0h/0h | P2SH-P2WPKH |
| Native SegWit | m/84h/0h/0h | P2WPKH |
| Taproot | m/86h/0h/0h | P2TR |

For testnet, replace the coin type 0h with 1h. For multisig, the account path is often m/48h/0h/0h followed by a script-type component, such as 2h for native SegWit multisig. Do not guess silently: write down every path you try and label it.

Step 3: Use a small script to derive addresses

The safest script is one you can read. In pseudocode, a native SegWit recovery looks like this:

BIP39 recovery

mnemonic = read from local file
passphrase = read from local prompt
seed = BIP39_to_seed(mnemonic, passphrase)
root = BIP32_from_seed(seed)
for change in [0, 1]:
    for index in range(0, 20):
        path = m/84h/0h/0h/change/index
        pubkey = root.derive(path).public_key()
        address = P2WPKH(pubkey)
        print(path, address)

This is not a complete recovery program. It is a conceptual outline. A production script must handle checksum validation, network selection, address encoding, and descriptor export correctly. If you are not comfortable reviewing those details, use a reputable wallet's built-in recovery flow instead.

For descriptor-based wallets, export something like:

wpkh([fingerprint/84h/0h/0h]xpub.../0/*)

Then import the descriptor into a watch-only wallet. This lets you scan the chain without exposing the mnemonic to the watch-only device.

BIP39 recovery

Step 4: Compare addresses before moving funds

Do not trust the first address a script prints. Compare a range of addresses, including change addresses, with any address you previously received from Jade. If you have a transaction history, check the first and last known addresses. If you have no record, use a block explorer only with public addresses, never with the mnemonic.

A match on multiple addresses is strong evidence that the script type, derivation path, and passphrase are correct. A single match can be a coincidence only in theory, but multiple matches across receive and change chains are much safer.

Step 5: Sweep with a trusted wallet

Once you have the right descriptor or wallet import, create a new receiving address in a trusted wallet and sweep the funds. If the old wallet used a passphrase, the new wallet should be created with a fresh backup and, ideally, a new seed. Reusing a compromised or uncertain recovery environment is not a good long-term plan.

For multisig, a mnemonic alone is not enough. You need the wallet descriptor, the other cosigner xpubs, and the threshold. Jade's multisig registration file or your own backup notes may contain this information. Without it, a script can derive your cosigner key but cannot reconstruct the complete multisig wallet.

Common pitfalls

  • Wrong passphrase: A single typo creates a valid but empty wallet.
  • Wrong script type: Native SegWit addresses will not appear under a legacy path.
  • Wrong account index: Most wallets use account 0, but some setups use another account.
  • Address gap limit: Wallets stop scanning after a gap. Increase the gap limit if the wallet was used heavily.
  • Multisig metadata loss: The mnemonic is only one part of a multisig wallet.
  • Online seed entry: A website that asks for 24 words is a theft risk, even if it looks professional.

Conclusion

Jade mnemonic script recovery is a deterministic reconstruction problem, not a magic recovery trick. The safe method is to work offline, verify the checksum, identify the exact script type and derivation path, derive public addresses, compare them with known Jade addresses, and then sweep funds through a trusted wallet. Treat the mnemonic as the master secret it is, and use scripts only when you can read and verify them.