Addresses
Tested in a fixed case
Owned legacy P2PKH, nested SegWit and native SegWit addresses restored.
Plan a Litecoin wallet migration
Compare the evidence for moving a backup: addresses, history and signing are separate checks. Choose a route and download a blank action plan.
Planner release 2026-10-12.1 · reviewed 2026-10-12 · Published recovery experiments
A restored address list, a discovered balance and the ability to sign answer different questions. This planner shows which parts of a route have evidence and which still need checking.
Choose names and a backup format only. This tool has no secret input, upload, wallet connection or payment action. Your choices stay in this page's memory. Tested versions identify the evidence; they are not software recommendations or proof that your funds will recover.
Which backup are you moving?
If the format is uncertain, select “Another format / format unknown”. A wallet name or the number of recovery words does not settle compatibility. The Trust Wallet Core option is a research library, not the Trust Wallet application.
Showing the recorded Core encrypted-file case. JavaScript enables route selection and plan downloads.
An encrypted Core file restored on the same test chain
The exact same-version RPC experiment restored three standard address types and spending authority.
- Source evidence version
- 0.21.5.8 · Windows RPC · legacy wallet · isolated regtest
- Destination evidence version
- 0.21.5.8 · Windows RPC · legacy wallet · isolated regtest
History and balance discovery
Tested in a fixed case
Three confirmed regtest payments, 3 LTC total, restored on the same already available test chain.
Signing authority
Tested in a fixed case
Three signed candidates passed regtest mempool checks; one candidate was broadcast and mined.
Conditions behind this result
- Litecoin Core 0.21.5.8 on Windows, legacy wallet-file backup, RPC workflow.
- The test chain was already available. The backup included the receiving keys used in this case.
- The restored encrypted copy remained locked; the experiment used its known test password to sign.
What it does not establish
- No cross-version or other-wallet file migration, graphical interface, mainnet resync, pruned-history, mnemonic, MWEB or hardware test.
- This result does not validate your backup, funds, application version or current security of the tested release.
Keep a blank action plan
The download contains the selected route, evidence releases, conditions and an empty checklist for your own checks. No address, seed, password, key or balance is collected or added. Fill non-secret configuration and actual software versions locally; keep recovery material separately.
Follow the backup verification learning path · Why a restored wallet can show zero
Inspect the finite evidence cases
These classifications index published experiments and primary documentation. No new wallet experiment was run for this planner. “Not tested” means the cited case does not establish that result; it does not mean an application is incapable of it. An “unsupported” finding below is limited to the named backup and signing condition.
Recovery release 2026-09-27.1 used synthetic wallets: Core 0.21.5.8 on isolated regtest, Electrum-LTC 4.2.2.1 through an offline Windows CLI and Wallet Core 4.8.4 through WebAssembly. History release 2026-09-27.2 and the separate legacy 2-of-3 signing experiment have their own scopes. Cake documentation was reviewed on 12 October 2026 without testing a pinned application build.
Litecoin Core → Litecoin Core · Encrypted legacy Core wallet file
An encrypted Core file restored on the same test chain
The exact same-version RPC experiment restored three standard address types and spending authority.
Addresses
Tested in a fixed case
Owned legacy P2PKH, nested SegWit and native SegWit addresses restored.
History and balance discovery
Tested in a fixed case
Three confirmed regtest payments, 3 LTC total, restored on the same already available test chain.
Signing authority
Tested in a fixed case
Three signed candidates passed regtest mempool checks; one candidate was broadcast and mined.
Conditions
- Litecoin Core 0.21.5.8 on Windows, legacy wallet-file backup, RPC workflow.
- The test chain was already available. The backup included the receiving keys used in this case.
- The restored encrypted copy remained locked; the experiment used its known test password to sign.
Limits
- No cross-version or other-wallet file migration, graphical interface, mainnet resync, pruned-history, mnemonic, MWEB or hardware test.
- This result does not validate your backup, funds, application version or current security of the tested release.
- Core encrypted-file observations · 2026-09-27.1
- History and backup-coverage experiment · 2026-09-27.2
Electrum-LTC → Electrum-LTC · Native Electrum seed · no extension
Native Electrum seed restored through the offline CLI
Address matching and a message signature were tested; finding funds online was not.
Addresses
Tested in a fixed case
20 receiving and 10 change addresses matched the fresh native-seed restore.
History and balance discovery
Not tested in this case
The executable stayed offline; transaction history and balance discovery were not tested.
Signing authority
Tested in a fixed case
The restored wallet signed a message verified by the executable. No transaction was spent.
Conditions
- Electrum-LTC 4.2.2.1 signed Windows executable, offline CLI.
- The matching and signing fixture used no seed extension; it was a native Electrum seed, not BIP39.
- Separate imported keys need their own backup; the native seed test does not include them.
Limits
- No GUI, mainnet spend, mobile application or complete account-discovery test.
- This result does not validate your backup, funds, application version or current security of the tested release.
Electrum-LTC → Electrum-LTC · Native Electrum seed + extension
A seed extension changes which wallet you restore
One extension variation changed the first address. A full extended-wallet recovery was not tested.
Addresses
Not tested in this case
No two independent restores with the same nonempty extension were compared. The variation only showed a different first address.
History and balance discovery
Not tested in this case
No history or balance scan was performed for the extended fixture.
Signing authority
Not tested in this case
The published message-signing check used the no-extension native fixture.
Conditions
- Identify the exact native seed format and whether the original used an extension.
- The experiment compared the empty extension with one fixed public test extension; do not enter an extension here.
Limits
- Successful word entry or a valid address does not prove the intended wallet was recovered.
- This result does not validate your backup, funds, application version or current security of the tested release.
- Exact Electrum restore method · 2026-09-27.1
Electrum-LTC → Electrum-LTC · Electrum master public key · watch-only
A public-key backup restores a view, not a signer
The known master public key reproduced addresses but contained no account private key.
Addresses
Tested in a fixed case
20 receiving addresses matched the original native Electrum fixture.
History and balance discovery
Not tested in this case
Offline address preparation did not establish transaction or balance discovery.
Signing authority
Cannot do this with this backup alone
This master-public-key-only backup had no account private key and produced no message signature.
Conditions
- Electrum-LTC 4.2.2.1 Windows CLI and the native fixture's master public key.
- To regain spending authority, locate the corresponding signing backup or device separately.
Limits
- The CLI returned a generic error, not a friendly watch-only explanation.
- No claim about other extended-public-key formats, multisig policy or online history.
- This result does not validate your backup, funds, application version or current security of the tested release.
- Electrum-LTC native seed and account-key observations · 2026-09-27.1
Trust Wallet Core · research engine → Trust Wallet Core · research engine · BIP39 recovery phrase
A BIP39 phrase recreated fixed derivations in the engine
This was a wallet library experiment, not a Trust Wallet mobile restore.
Addresses
Tested in a fixed case
42 fixed derivations matched after fresh restores across the fixture's passphrases, accounts, branches and indices.
History and balance discovery
Not tested in this case
No blockchain connection, app account discovery or balance scan.
Signing authority
Not tested in this case
This engine experiment did not sign a message or spend a transaction.
Conditions
- Trust Wallet Core 4.8.4 WebAssembly engine.
- Preserve the intended BIP39 passphrase, script type, account, receive/change branch and address index.
- The derivation fixtures cover P2PKH and P2WPKH; another passphrase or account produces another wallet view.
Limits
- No Trust Wallet mobile/extension interface, hardware, MWEB or general derivation coverage.
- This result does not validate your backup, funds, application version or current security of the tested release.
Trust Wallet Core · research engine → Electrum-LTC · BIP39-derived account private key
Two derived account keys matched across implementations
An account-key bridge was tested. Importing BIP39 words into Electrum's graphical wizard was not.
Addresses
Tested in a fixed case
Ten fixed receive/change addresses matched for P2PKH and P2WPKH account 0.
History and balance discovery
Not tested in this case
Electrum remained offline; no account, balance or transaction-history discovery.
Signing authority
Tested in a fixed case
Each imported account signed a verified message; no mainnet transaction was submitted.
Conditions
- Wallet Core 4.8.4 WASM → Electrum-LTC 4.2.2.1 Windows CLI.
- Exactly m/44'/2'/0' (P2PKH) and m/84'/2'/0' (P2WPKH), with the empty BIP39 passphrase in the bridge fixture.
- This evidence concerns sensitive derived account private keys, which this planner never accepts or exports.
Limits
- Not a whole-wallet transfer, Electrum BIP39 seed-wizard test, other account or script type, mobile app or history test.
- This result does not validate your backup, funds, application version or current security of the tested release.
- Ten cross-implementation address comparisons · 2026-09-27.1
- Electrum-LTC native seed and account-key observations · 2026-09-27.1
Trust Wallet Core · research engine → Electrum-LTC · BIP39 recovery phrase
Direct BIP39 seed entry is outside the tested bridge
The recorded cross-implementation match used account private keys, not this backup format.
Addresses
Not tested in this case
The graphical BIP39 seed wizard was not exercised. Native default CLI restore rejected the public BIP39 fixture.
History and balance discovery
Not tested in this case
No online recovery or history scan for direct BIP39 seed entry.
Signing authority
Not tested in this case
No signing check followed a direct BIP39 phrase restore.
Conditions
- Native Electrum seeds and BIP39 phrases are different restore formats.
- Do not infer that the entire application cannot restore BIP39 from a rejection in the default native CLI mode.
Limits
- The tested account-key bridge does not establish this seed-entry route.
- This result does not validate your backup, funds, application version or current security of the tested release.
- Electrum-LTC native seed and account-key observations · 2026-09-27.1
Cake Wallet → Cake Wallet · BIP39 recovery phrase
Cake documents BIP39 restoration
Documentation describes the format and path. No pinned application restore was tested here.
Addresses
Documented · no application test
Litecoin BIP39 restoration is documented with account path m/84'/2'/0'; no restored-address comparisons were run.
History and balance discovery
Not tested in this case
The documentation review did not measure history, address-gap or balance discovery.
Signing authority
Not tested in this case
No restored Cake application signed a test message or transaction in this review.
Conditions
- Documentation reviewed 12 October 2026; the application build and device were not pinned.
- Keep the exact BIP39 passphrase and original account/path configuration. Record the actual app version before proceeding.
Limits
- This route is documented, not experimentally verified; it does not establish cross-app or MWEB recovery.
- This result does not validate your backup, funds, application version or current security of the tested release.
Cake Wallet → Cake Wallet · Native Electrum seed · no extension
Cake also documents Electrum-format restoration
Choosing the correct format matters; an application-level round trip was not tested.
Addresses
Documented · no application test
The Litecoin documentation supports Electrum-format restoration and records m/0' for that format.
History and balance discovery
Not tested in this case
No network history or restored balance measured in Cake.
Signing authority
Not tested in this case
No signing test in a restored Cake wallet.
Conditions
- Documentation reviewed 12 October 2026; application build not pinned.
- Identify the original seed type. This documentation alone does not prove that every Electrum-LTC seed variant or extension transfers.
Limits
- No Cake↔Electrum-LTC application compatibility test, imported-key backup, mobile device or MWEB migration test.
- This result does not validate your backup, funds, application version or current security of the tested release.
Litecoin Core → Litecoin Core · One cosigner key for the tested 2-of-3 policy
One key did not satisfy the tested 2-of-3 policy
This is a signing constraint from a separate experiment, not a multisig recovery test.
Addresses
Not tested in this case
No multisig backup was restored to compare addresses.
History and balance discovery
Not tested in this case
No restored multisig history or balance discovery test.
Signing authority
Cannot do this with this backup alone
Each single-key candidate was incomplete and rejected for the known legacy P2SH 2-of-3 output.
Conditions
- Separate Litecoin Core 0.21.5.8 regtest legacy P2SH 2-of-3 signing experiment.
- The known threshold was two distinct cosigner keys plus the script/policy; one cosigner backup was insufficient.
Limits
- No generic multisig migration, seed-only policy recovery, other threshold, address type or wallet application claim.
- The eight candidates were not broadcast.
- This result does not validate your backup, funds, application version or current security of the tested release.
- Core legacy P2SH 2-of-3 signing combinations · 2026-09-23
Litecoin Core → Litecoin Core · Full multisig policy + enough cosigner keys
Policy and enough keys are necessary; recovery remains untested
All three two-key pairs could sign the known output, but no multisig backup was restored.
Addresses
Not tested in this case
The experiment did not restore a multisig backup or compare recovered address lists.
History and balance discovery
Not tested in this case
It did not test restored multisig history or a discovered balance.
Signing authority
Tested in a fixed case
AB, AC and BC each completed a candidate accepted by regtest policy with the known redeem script.
Conditions
- Separate Core 0.21.5.8 legacy P2SH 2-of-3 experiment, known previous output and policy.
- Preserve the full policy/script and enough independent signing backups; record key order and threshold where relevant.
Limits
- This signing result does not verify a user's multisig backup or establish whole-wallet migration.
- No candidate was broadcast; no restored multisig wallet was tested.
- This result does not validate your backup, funds, application version or current security of the tested release.
- Core legacy P2SH 2-of-3 signing combinations · 2026-09-23
Editorial responsibility: Jarosław Wasiński. Experimental results are AI-assisted scripted checks; no independent human review is claimed. The planner verifies neither real backups nor recovery success rates.