Wallet resilience
Replacing a device is different from creating a new wallet
By Jolly Ledger editorial · Published · Reviewed · 4 min read
Short answer
Restoring an existing backup on compatible hardware gives another device access to the same wallet. Creating a new wallet generates different keys and requires a separate, carefully verified transition if you want existing assets controlled by them.
“I need a new wallet” can mean two very different things. You may want a replacement screen and buttons, or you may want different keys controlling your assets. Clarifying that intention before setup helps avoid assuming a hardware purchase changes a secret that might already be exposed.
The device is a signer; the wallet is not its casing
In a typical single-signature setup, a hardware device holds or derives the private keys needed to approve transactions. A compatible backup can reproduce those keys on another device. The original device and replacement can therefore access the same wallet, even when they have different PINs or come from different manufacturers.
BIP-39 describes how a mnemonic and optional passphrase determine a seed. The device PIN controls local device access; changing it does not change the seed. A different BIP-39 passphrase produces a different wallet, but passphrase changes should not be treated as a casual fix: exact recovery requirements and exposure circumstances still matter.
Compare the two decisions
| Question | Replace a device using the existing backup | Create a new wallet |
|---|---|---|
| Which keys? | The existing wallet’s keys. | Different keys with their own backup requirements. |
| Existing assets? | Accessible through compatible recovery and account settings. | Do not automatically appear under the new keys. |
| Old device access? | Not revoked merely by replacement. | Old keys still control anything left under them. |
| Typical purpose? | Replace failed hardware or add a spare. | Establish a separate wallet or respond to a justified need for different keys. |
A newly generated wallet does not automatically take over balances from an older one. Any intended transition involves separate on-chain actions and may involve network fees, account-specific rules or asset-specific complications. This article is not a universal transaction recipe. Use the relevant vendor’s official instructions for your exact wallet and networks.
Choose based on what happened
If the hardware failed but there is no evidence of secret exposure, compatible replacement may meet the need. If a device is missing, assess its access protections and the circumstances separately. A suspicious email alone does not establish key compromise; revealing a recovery phrase is materially different. See what to do after sharing a phrase for the right route to official guidance.
A second device restored from the same backup is useful redundancy, not a new security boundary for that secret. Read two devices with the same seed if your goal is availability. Conversely, generating an unrelated backup creates a new recovery responsibility that must be documented and protected independently.
Before you proceed
- State the goal: replacement access, a spare, or different wallet keys.
- Identify any verified exposure rather than assuming compromise from a warning alone.
- Confirm backup format, passphrase needs and account compatibility.
- Find official model-specific setup or incident instructions.
- Preserve the existing working access route while verifying the plan.
- Keep old and new records clearly distinguished, without putting secrets into ordinary notes.
Do not erase first and work out the distinction later
Keep the old device and protected recovery material available until the relevant access and transition checks are complete. A reset does not revoke a backup copied elsewhere, and destroying a device does not change blockchain ownership. For ordinary damage or loss, review the available recovery options before taking an irreversible step.
Never enter recovery words into a website or software utility to “upgrade” or “migrate” them. A legitimate plan should identify the exact hardware workflow, the intended wallet and what evidence will show the goal has been met. Buying another device is only one part of that decision.
Sources
- BIP-39: Mnemonic code for generating deterministic keys — Bitcoin BIPs contributors
- Passphrase FAQ: what every passphrase user should know — Trezor
Reported facts are attributed to their sources. Spotted an error? Read our corrections approach.
Turn this into a preparation plan
Answer 16 calm questions about your setup. Get findings, scenario walkthroughs and a family briefing — on your own device, no account, no wallet connection, no recovery words.