The old Litecoin backup still spent after a password change
An earlier encrypted copy unlocked with its known old password and spent the test output. Twelve Core cases separate local file encryption from on-chain control.
AI-generated editorial illustration of a Litecoin coin, two symbolic wallet-file copies and an old key beside the earlier copy.
On this page
Dotted-underlined terms open a quick definition. Close it to keep reading.
A can stop someone opening the file on your computer. It cannot reach into an older copy and change the keys already stored there. To test that distinction, we used two copies of an encrypted Core wallet and gave the older copy its original password. The copy signed and , which we confirmed in a test after the password change.
The original password was known in this experiment. We did not crack an encrypted backup. That detail matters: an encrypted file with an unknown password presents a different problem from a copied , exposed or backup whose password is already known.
The older file keeps its own password
Think of a wallet file as a container for signing material. Changing the password changes how that particular container opens. Litecoin checks whether a transaction satisfies the output's spending conditions; it does not ask which wallet file supplied the signature.
In the pinned Core implementation, walletpassphrasechange re-encrypts the existing master encryption key. It does not replace the spending keys with an independent set. That is why changing local encryption and changing control of an output are different operations. Core 0.21.5.8 implementation.
What we tested in Core
We used Core 0.21.5.8, wallet A and a consistent backupwallet snapshot loaded as B. Both copies were already encrypted before A's password change. The test funds existed only on regtest, Core's private test network. We recorded the password checks, signing responses and transaction-acceptance results separately. A successful unlock alone is weaker evidence than a signed transaction that the accepts.
Observed results for the original wallet and its earlier encrypted copy. Password labels are synthetic test credentials.
Check
Current wallet A
Earlier copy B
Unlock with the original password after A's password change
Rejected: RPC error -14
Unlocked
Unlock with the replacement password
Unlocked
Rejected: RPC error -14
Sign the controlled original output
Not tested in this signing step
complete: true
Node accepts the copy's signed candidate
Not a password check
allowed: true
Each password check started with walletlock. A changed its opening password; B retained its original one. The funded 's and the reported HD seed identifier remained unchanged.
Mechanism illustration for a known-password encrypted copy. The tables distinguish observed signing, admission and confirmation. On narrow screens, scroll the diagram. Open full-size SVG.
These cases concern one wallet copy and a known password. They do not measure password strength, theft frequency or response time during a real leak.
Four different things people call a password
Before resetting anything, identify the secret involved. A password field can look similar while controlling a different part of the system.
Which secret changes which layer? Only the Core encryption row was tested in this experiment.
Secret
Its role
What changing it does not establish
Core wallet encryption password
Unlocks signing material stored in that wallet file.
Another copy has stopped holding the old signing material.
BIP39 recovery passphrase
Participates with the recovery words in deriving a seed.
Funds have moved from the wallet derived with the previous passphrase.
Hardware-device PIN
Controls access to the device under its specific security design.
A recovery backup disclosed elsewhere has been invalidated.
Exchange-account password
Authenticates access to an account with a service.
A self-custody private key has changed, or every active session and withdrawal permission has been removed.
uses the optional in seed derivation. Entering a different one normally selects different key material; it is not a reset button for the wallet containing your existing coins. Core's file-encryption password is not this BIP39 feature. If your wallet uses that optional recovery passphrase, distinguish exposure of the words alone from exposure of the words and the passphrase together. BIP39 specification.
For a hardware example, Trezor documents that the device PIN is independent of its recovery backup. Coinbase's password-reset instructions concern access to a service account. Neither workflow was performed here. Trezor PIN documentation · Coinbase account-password documentation.
A new receiving address may still belong to the copied wallet
A fresh address is useful for avoiding unnecessary . It is not, by itself, evidence that the underlying secrets are independent of an old backup. Hierarchical wallets can derive many keys from one seed, and a saved wallet file can contain keys prepared for future use. BIP32 key-tree construction.
After changing A's password, we requested another address from A. B reported that it owned this address and produced a message signature that Core verified. This case concerns the copied wallet's particular . It does not show that every backup contains every future address. A backup containing only an individually imported key has a different scope from one containing the wallet's derivation material.
Ask whether the destination has independent recovery material, rather than whether its address looks new. See our receiving-address guide for normal address changes and our recovery experiments for backup contents and discovery limits.
What changed after the transfer to an independent wallet
We created a separate wallet C. B spent the controlled 1 LTC input to C, delivering 0.9999 LTC with a 0.0001 LTC fee. We broadcast that transaction and mined one confirming block. We checked two different objects: the original output after its confirmed spend, and the new output controlled by wallet C.
Moving the funds changes the output being spent. A spent-input failure and a missing-signature result answer different questions.
Candidate
Recorded result
What it establishes
Copy B attempts to spend the original output after the transfer confirms
Signature complete; rejected: missing-inputs
The original input was spent, although its old key could still create a signature.
Copy B attempts to sign the new output belonging to C
complete: false; candidate rejected
Whether B supplied the required signing material for that specific new output.
Independent wallet C signs a candidate spending its new output
complete: true; mempool allowed
A valid-signature and mempool-admission control; this second candidate was not mined.
B still signed a different candidate for the already-spent input. It could not sign C's new output; C could, and its candidate passed the check. We did not broadcast that second candidate. The old key is not revoked across the network. If someone later pays its address again, that creates another output under the old spending conditions. Update saved withdrawal destinations, payment requests and recurring invoices as part of a migration.
A real transfer needs a checked destination, suitable fee and . We did not test an attacker racing the owner or malware substituting an address. A small destination check does not protect the old key while you wait.
Changing a future transaction's date also leaves its ordinary input under the same key holder's control. Our timelock experiment tests that distinction and compares it with a condition actually required by an output's script.
A status message was not enough to prove new keys
While reviewing the source, we found another reason to check the actual operation. The encryptwallet response includes the phrase “new HD seed was generated”, while the pinned implementation comments out seed replacement for MWEB key management. During setup, the reported hdseedid was also identical before and after initial encryption. This is one observed setup case, not a claim of a security vulnerability. RPC response · corresponding implementation.
The password-change experiment still uses an already-encrypted snapshot. Neither its method nor its spending proof relies on the initial-encryption status message.
Match the response to what was exposed
Incident triage. These are practical distinctions, not a tested incident-response success rate.
Situation
First distinction to make
Do not assume
Someone saw a public receiving address
Public information versus signing material.
The address alone lets them spend your LTC.
An encrypted backup file may have escaped
Whether its original password was also exposed; preserve the file's encryption context.
A password change updates the escaped file.
A private key or complete recovery material was disclosed
The affected keys, accounts and spending policy.
A new PIN or address within the same wallet removes the disclosed secret.
The computer may still be compromised
Whether it can observe new secrets or substitute payment details.
Creating another wallet on it establishes a clean destination.
Do not upload recovery words, wallet files or private keys to a “revocation”, “validation” or rescue website. A public is enough to inspect a transfer in our transaction checker; it cannot establish that your devices or backups are secure.
A migration checklist you can keep
Write down what may have escaped: a public address, encrypted file, old password, individual key or recovery material. Keep secrets out of the incident notes you share.
Identify the affected wallet and backup format. Use our recovery-plan checklist when the format is unclear.
If replacing control, prepare independent recovery material through a trusted wallet procedure on a suitable device. Check its backup before depending on it.
Verify the complete receiving address through a trusted display or channel. Do not rely on the first and last characters.
Record the actual transaction ID, destination output, fee and confirmed status. Confirm the intended amount arrived; a broadcast notification is not a completed migration.
Replace old payment requests and saved destinations. Keep the old backup's original password context in mind if you must retain it for historical records.
A forgotten password without suspected copying is a different problem. Identify your backup and the wallet's documented recovery procedure first. This experiment does not tell every person who forgets a password to move funds.
Files and reproduction
Recorded password-test results · runner · offline verifier · migration worksheet · instructions · complete research package. The 6 October 2026 release records 12 password-study cases. A repeat in another fresh test directory matched all 12 case outcomes. The package contains the controlled setup, recorded results and reproduction instructions. Tests used synthetic wallets and regtest funds; no customer's wallet, seed phrase, account or hardware device was accessed. Do not send real LTC to any test address.
The hero is an AI-generated editorial illustration, not a photograph of the experiment. Research, code and drafting were AI-assisted; the original diagram explains the mechanism. No independent external review is claimed. Report a reproducible discrepancy through our corrections page.
Wallet Encryption
In brief Password protection for a wallet's stored secrets, separate from a recovery passphrase and unable to replace a backup.
Protection of a wallet's stored secrets with an encryption password. It does not encrypt blockchain records or replace a backup. A wallet-file password is distinct from a BIP39 passphrase, which changes the derived keys.
For example Unlocking an encrypted Core wallet allows signing for a limited time; it does not move its LTC.
Common mistake Assuming a wallet-file password can recover a missing file, or protects a seed phrase already exposed elsewhere.
Compare: Wallet password vs recovery passphrase
Wallet Encryption
An encryption password unlocks a particular wallet's stored secrets; it does not replace a missing backup file or encrypt blockchain records.
Passphrase
A BIP39 recovery passphrase is used with recovery words to derive a seed; a different passphrase derives a different valid seed.
One example An incorrect unlock password is rejected by an encrypted Litecoin Core wallet; an incorrect BIP39 recovery passphrase can instead produce an empty-looking wallet with different addresses.
Remember: Check each secret's role in the original wallet: changing a local encryption password does not change a BIP39 recovery passphrase or move the coins.
In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.
Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.
For example One wallet can generate several receiving addresses and still show them as a single combined balance.
Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.
In brief A peer-to-peer cryptocurrency with its own Scrypt proof-of-work network and a maximum issuance of 84 million LTC.
A peer-to-peer cryptocurrency launched in 2011. Litecoin uses Scrypt proof of work, targets an average 2.5-minute block interval and has an issuance schedule capped at 84 million LTC. Individual block times and payment acceptance times vary.
For example Sending 0.1 LTC on Litecoin transfers a fraction of one coin; you do not need to buy a whole LTC first.
Common mistake Assuming a token with LTC in its name on another network is automatically native Litecoin.
In brief Submitting a signed transaction to a node for checking and sharing, without proving it has been confirmed.
Submitting a signed transaction to a node for validation and possible relay to peers. A signed file and its identifiers can exist before submission. Acceptance by one node does not establish that all peers saw it, a miner included it or a service credited it.
For example An offline signer can prepare a payment that remains outside the mempool until the approved transaction is submitted online.
Common mistake Treating a TXID or signed file as proof of broadcast, or treating a local submission response as a confirmation.
In brief A group of transactions linked to the previous block under the network's rules.
A batch of transactions accepted under the network rules and linked to the previous block. Litecoin targets one new block every 2.5 minutes on average; a particular block may arrive sooner or much later.
For example Your payment may wait unconfirmed and then receive its first confirmation when a miner includes it in an accepted block.
Common mistake Treating the 2.5-minute target as a countdown or a maximum wait for your payment.
In brief Secret data a wallet uses to sign spending; one key may cover only part of a wallet and must never be shared.
Secret data used to authorize spending under the conditions attached to coins. In a simple single-key wallet, anyone with that key can spend the coins it controls. A wallet may manage many keys; never share them.
For example A wallet signs a spend using a private key; the recipient only needs your payment, not that secret key.
Common mistake Sharing a key with support or assuming one exported key necessarily backs up every address in a wallet.
Compare: Seed phrase vs private key
Seed Phrase
Recovery words used by many wallets to rebuild key material; the correct format, optional recovery passphrase and wallet settings still matter.
Private Key
A secret used to authorize spending under its key conditions; one exported private key is not necessarily a backup of every key a wallet uses.
One example A fictional simple HD wallet can derive several receiving keys from one recovery setup; exporting just one of those private keys does not preserve the others.
Remember: Identify the complete backup method for the original wallet, keep secret recovery material offline and never paste it into this website.
In brief Secret recovery words that need the right wallet format, settings and any extra passphrase; keep them offline.
A sequence of secret recovery words that some wallets use to rebuild keys. Recovery must match the original wallet's word format, settings and any extra passphrase; other wallets use different backup methods. Keep the words offline and follow the original wallet's official recovery instructions.
For example In a BIP39 wallet, the same words with a different extra passphrase produce a different seed and can show different addresses.
Common mistake Entering recovery words into a website, sharing them with support or assuming every Litecoin wallet uses the same word format.
Compare: Seed phrase vs private key
Seed Phrase
Recovery words used by many wallets to rebuild key material; the correct format, optional recovery passphrase and wallet settings still matter.
Private Key
A secret used to authorize spending under its key conditions; one exported private key is not necessarily a backup of every key a wallet uses.
One example A fictional simple HD wallet can derive several receiving keys from one recovery setup; exporting just one of those private keys does not preserve the others.
Remember: Identify the complete backup method for the original wallet, keep secret recovery material offline and never paste it into this website.
In brief Recorded in accepted blockchain blocks, unlike account changes a service may make only in its own records.
Recorded in the blockchain's accepted blocks. For transparent Litecoin, many transaction details are publicly visible, but an exchange's internal account changes need not create an on-chain transaction. Blockchain records alone do not establish an owner's identity or why funds moved.
For example A confirmed ordinary LTC payment appears in Litecoin blocks; an exchange moving balances between its own customer accounts may not.
Common mistake Assuming every account activity creates a blockchain transaction or that every large transfer is a trade.
In brief A participant running network software; a full node checks rules but need not keep all old block files.
A participant running network software. A full node independently validates rules; a pruned full node can discard older block files after validation. Not every node stores the complete historical blockchain.
For example A pruned full node checks the chain but later discards old block files to reduce disk use.
Common mistake Assuming every node is a miner, or that pruning means it skipped consensus validation.
In brief An encoded payment destination whose network, owner and wallet compatibility still need checking.
An encoded destination for a payment. Common transparent Litecoin addresses begin with L, M or ltc1; MWEB uses a different address format. An address is not a bank account or proof of identity. Check network and wallet compatibility before sending.
For example To receive LTC, copy a Litecoin receiving address from your wallet and check it against the address shown to the sender.
Common mistake A valid-looking address does not prove that it belongs to the intended person or uses the network the sender selected.
In brief Data derived from a private key that verifies signatures, rather than a secret key, address or proof of identity.
A cryptographic value derived from a private key and used to verify signatures. Addresses encode destinations or spending conditions and are not always a direct public-key hash. Public keys are not personal identities.
For example A node can use a public key to check a signature without learning the private key that created it.
Common mistake Confusing a public key with a private key, a receiving address or proof of the owner's real identity.
In brief A recovery-word standard used by some wallets to derive a seed from the words and an optional passphrase.
A specification that turns generated randomness into recovery words and derives a seed from those words plus an optional passphrase. It does not define every wallet's backup format or the complete address-discovery process. Not every recovery phrase is BIP39.
For example The same BIP39 words with two different passphrases produce different seeds and can open different wallets.
Common mistake Assuming twelve words identify the format, or that every Litecoin app will restore the intended accounts from those words alone.
In brief A wallet-specific secret that can unlock stored keys or change the seed derived from recovery words.
A secret whose role depends on the wallet. A local encryption passphrase unlocks stored signing material. A BIP39 recovery passphrase is combined with recovery words to derive a seed. Changing the local unlock password does not by itself change that BIP39 recovery setup or move coins.
For example A typo in a BIP39 passphrase can derive a different valid wallet, whereas a wrong local encryption passphrase normally fails to unlock the file.
Common mistake Treating an app password, device PIN and recovery passphrase as interchangeable, or assuming a password change invalidates every old backup.
Compare: Wallet password vs recovery passphrase
Wallet Encryption
An encryption password unlocks a particular wallet's stored secrets; it does not replace a missing backup file or encrypt blockchain records.
Passphrase
A BIP39 recovery passphrase is used with recovery words to derive a seed; a different passphrase derives a different valid seed.
One example An incorrect unlock password is rejected by an encrypted Litecoin Core wallet; an incorrect BIP39 recovery passphrase can instead produce an empty-looking wallet with different addresses.
Remember: Check each secret's role in the original wallet: changing a local encryption password does not change a BIP39 recovery passphrase or move the coins.
In brief Receiving multiple payments at one address, which can link transparent payment records.
Receiving multiple payments at the same address. For transparent Litecoin payments, this can link receipts and complicate invoice matching. A fresh receiving address helps separate payment records, but does not by itself make a transaction anonymous.
For example Two invoices using one receiving address need another reliable identifier to distinguish their payments.
Common mistake Believing that reusing an address is required to keep funds in one wallet, or that fresh addresses guarantee anonymity.
In brief A wallet's reserve of prepared keys or address-generation entries, rather than a reserve of LTC.
A wallet's reserve of prepared keys or derivation entries for new receiving and change addresses. It is not a pool of LTC. Refill behavior and what an old backup can recover depend on the wallet and its format.
For example A wallet can take a fresh receiving key from its keypool instead of reusing an earlier address.
Common mistake Confusing keypool size with an address-discovery gap limit, or assuming an old backup includes every later imported key.
In brief One node's local collection of accepted but unconfirmed transactions, which may differ from other nodes' collections.
A node's local collection of unconfirmed transactions it currently accepts. Nodes can see, retain or remove different transactions, so there is no single global waiting room. Appearing in a mempool is not confirmation or a guarantee of later inclusion.
For example One explorer may see your unconfirmed transaction while another node has not received it or has already removed it.
Common mistake Assuming that absence from one mempool proves the payment was never broadcast or that a seen transaction must confirm.
In brief A transaction gains confirmations as blocks build on its inclusion, but those confirmations can fall if chain history changes.
A transaction receives its first confirmation when included in a block in the accepted chain. Each block then built on top adds another. A chain reorganization can reduce or remove the count. The recipient decides how many confirmations it requires. Litecoin targets an average 2.5-minute block interval; individual blocks can arrive sooner or much later.
For example A transaction in the latest accepted block has one confirmation; the next block raises that count to two.
Common mistake Confusing a wallet's sent message, a TXID or mempool visibility with the first confirmation.
In brief A transaction identifier for looking up outputs and confirmations, which alone does not prove that a payment arrived.
The identifier used to look up a transaction. For an ordinary transparent Litecoin transaction it is shown as a 64-character hexadecimal string. Use it to inspect the transaction's outputs and confirmations; the ID alone does not prove a payment is confirmed.
For example Copy the TXID from your wallet's payment details into a Litecoin explorer to check the recipient output and confirmation count.
Common mistake Sharing a seed phrase to trace a payment, or treating a screenshot or TXID alone as proof that the expected amount arrived.
In brief A service for trading currencies or assets, whose custodial account balance does not give you control of its private keys.
A platform or service for buying and selling cryptocurrencies against fiat currencies or other assets. Trading methods, custody, supported pairs and withdrawal rules vary by service. A balance on a custodial exchange is an account claim; it does not mean you control the wallet's private keys.
For example After buying LTC on a custodial exchange, you request a withdrawal if you want it sent to your own wallet.
Common mistake Assuming an account balance means you possess the private keys, or overlooking the selected withdrawal network.
Downloadable data or code · Controlled wallet / regtest.
Content review recorded: 2026-10-06. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.
12 controlled Core cases with a known-password encrypted legacy wallet copy, one copied-keypool address and independent-wallet transfer. Signing, mempool admission and confirmed migration are separate; no cracking, real compromise or hardware device tested.
The earlier encrypted copy kept its old password and confirmed a spend; changing the current file password did not replace the copied key.
Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.