What happens to an old seed backup after a full wallet migration?

An old seed phrase remains able to sign for every address derived from it after assets leave those addresses. Moving assets does not invalidate the key tree or cancel existing approvals. Keep the backup until you confirm all balances, NFTs, liquidity positions, and protocol claims were handled. Once the old addresses hold nothing needed, archive or destroy the backup under your documented retention plan.

Does changing a DeFi wallet password change its seed phrase?

Changing a wallet password does not change the seed phrase or any address derived from it. The password encrypts one application's local vault, while the seed rebuilds the key tree on another compatible installation. Store the password where it supports ordinary device access, and store the seed as an offline recovery asset. If you add a BIP-39 passphrase, record its existence separately because it participates in seed derivation and creates a different set of addresses on every compatible chain.

How long does a DeFi wallet recovery take?

A basic seed restore takes the time needed to install a compatible wallet, enter the words, derive accounts, and check addresses. Onchain waiting starts if you then move assets, revoke approvals, or change smart-account owners. Wallet indexing can delay the display of tokens or positions, but key derivation itself is local. Measure completion by the expected address appearing, not by a populated dashboard.

Where should heirs find DeFi wallet recovery instructions?

Recovery instructions for heirs should identify the wallet type, backup standard, network names, public addresses, and location of the offline material without placing every secret together. A seed phrase by itself may omit a BIP-39 passphrase, Safe threshold, hardware-wallet requirement, or separately imported key. Keep instructions understandable to the intended person and review them after migrations. Test the instructions before any planned handoff or device retirement. Legal ownership, access timing, and estate procedures belong in an appropriate local estate plan.

Must a DeFi protocol be online while the wallet derives its keys?

No DeFi protocol needs to be online while a standard seed phrase derives keys in a compatible wallet. BIP-39 and BIP-32 calculations run locally; a network connection then queries balances and positions. If Aave or Uniswap interfaces are unavailable, the address and contracts still exist, although another compatible interface may be needed to manage them. Recovery begins with address control, not a specific application screen.

What happens to ERC-20 approvals after restoring the same address?

Existing ERC-20 approvals remain attached to the recovered address because the approval lives in the token contract's onchain state, not in the wallet installation. Restoring the same key therefore restores authority to change or use that address, while a new application may not display every approval automatically during recovery. Review approvals by chain before retiring a wallet. Moving tokens to a new address does not itself erase allowances granted by the old address, although empty balances limit their practical effect.

Could one seed phrase recover both tokens and NFTs?

One compatible seed phrase regenerates the private keys for addresses holding ERC-20 tokens, ERC-721 NFTs, ERC-1155 assets, and DeFi positions. Asset standards do not create separate seed phrases. Visibility still depends on wallet support for the relevant chain and contracts. A Bitcoin account derived from the same mnemonic follows another coin type and address scheme, so cross-chain recovery requires more than accepting the words.

When should a seed phrase backup be replaced instead of recopied?

Replace a seed backup when it is incomplete, unreadable, exposed beyond the intended control boundary, or tied to a key set you plan to retire. Merely recopying the same words preserves the same keys. To change the key tree, generate a new wallet backup, verify the new receiving addresses, migrate each token and DeFi position across every relevant network, and retain the old material until all remaining claims are resolved. A fresh physical copy alone improves durability, not cryptographic separation.

DeFi wallets are recoverable only when their seed backup survives

DeFi wallets are self-custody interfaces whose seed phrases rebuild the private keys used to sign onchain transactions after the loss of a phone, browser profile, or hardware device. Recovery succeeds only when the words, their order, the wallet standard, any added passphrase, and the account derivation path match the original setup. An offline copy therefore matters more than the application password, because that password unlocks one local installation while the seed recreates the underlying key tree. This page examines the recovery boundary: phrase lengths, offline storage, restoration costs, missing-account causes, hardware choices, and smart-account alternatives for Ethereum and other EVM networks.

One missing backup can erase the recovery path

A missing or unreadable seed phrase leaves a standard self-custody wallet without a deterministic route back to its private keys.

The critical distinction is between device access and key recovery. A browser password, biometric unlock, or PIN opens a specific installation; none reconstructs a deleted key vault by itself. If one working device remains, generate a replacement wallet with a checked backup, then move tokens and protocol positions under fresh keys before retiring the old setup. If no device works and the phrase is incomplete, the blockchain offers no reset process. ERC-20 balances, Uniswap liquidity positions, and Aave deposits remain assigned to the original address. The same boundary governs all seed-based DeFi wallets, making recovery stricter than restoring a custodial exchange login.

Recovery costs versus onchain transfer costs

Seed phrase restoration itself costs zero gas because a wallet derives keys locally without submitting a transaction to any blockchain.

Costs begin only when recovery changes onchain state. Reading addresses and balances through an RPC provider carries no protocol fee, while transferring ETH, ERC-20 tokens, or Uniswap v3 liquidity-position NFTs consumes gas. Ethereum, OP Mainnet, Base, and Arbitrum One charge gas in ETH; Polygon PoS charges POL. The total then follows the transaction gas used and the network fee market at submission. Removing an ERC-20 approval, moving a Uniswap position, or changing a Safe owner each creates its own contract call, so a complex wallet rotation costs more than a local restore.

Keep enough native gas on each affected network before migration. A same-address recovery avoids those rotation transactions; new keys require them.

How many seed words should a DeFi wallet have?

A BIP-39 DeFi wallet accepts one of five defined lengths: 12, 15, 18, 21, or 24 ordered words.

BIP-39 maps 128, 160, 192, 224, or 256 bits of entropy to 12, 15, 18, 21, or 24 words. Its checksum contributes 4, 5, 6, 7, or 8 bits respectively, and every word indexes an 11-bit group from a 2,048-word list. A 12-word phrase therefore carries 128 bits of original entropy, whereas a 24-word phrase carries 256 bits. Selecting words manually abandons wallet-generated randomness and may fail the checksum, so the phrase produced by the wallet is the recoverable backup.

The six-stage backup and restoration path

A reliable recovery path preserves six linked stages, from wallet-generated entropy through address verification on the intended network.

Summary: The six-stage backup and restoration path
Stage	Backup or recovery standard
Wallet generation	BIP-39 mnemonic from device-generated entropy
Phrase transcription	Ordered offline copy with exact spelling and word count
Backup verification	Built-in phrase confirmation or device recovery check
Seed derivation	BIP-39 derivation with the original optional passphrase
Account derivation	BIP-32 path and SLIP-44 coin type
Address confirmation	Restored public address matched on the intended chain ID
End state	Original signing authority confirmed before DeFi use resumes

During a restore, the wallet does not retrieve coins from a device. It recreates the same seed, derives the same child keys, and queries public chain state for the resulting addresses. Token balances, Aave positions, and Uniswap v3 position NFTs then reappear through wallet indexing or protocol interfaces. Local labels, address-book entries, custom token lists, and manually added networks belong to application data, so the seed alone does not rebuild them. Record those items separately, because successful key recovery and a familiar dashboard are different outcomes.

Offline copies and physical separation

An offline seed backup works only when every word remains legible, ordered, private, and available after device loss.

Paper handles a one-time setup cheaply, while stainless-steel storage better tolerates water, heat, and fading. The BIP-39 English list contains 2,048 entries arranged so the first four letters identify each word uniquely, although recording full words reduces reading ambiguity. Two complete copies in separate controlled locations reduce one-location failure, yet each additional copy expands the access boundary. A photograph, synced note, email, or ordinary cloud document stops being an offline backup even when the original sheet remains offline.

Manually dividing a 24-word BIP-39 phrase into two halves creates two incomplete records, not a threshold backup. Trezor offers 21-word SLIP-39 shares with configurable thresholds, making them the structured alternative to hand-splitting one phrase.

Derived accounts, chain IDs, and missing balances

Restoring the seed rebuilds keys, while wallet configuration decides which derived accounts, networks, and token lists appear on screen.

Ethereum Mainnet uses chain ID 1, OP Mainnet 10, Polygon PoS 137, Base 8453, and Arbitrum One 42161. The same EVM address can exist on all five networks, but each network keeps separate balances and contract state. A restored interface showing zero ETH on Ethereum may still control ETH on Base or an Aave position on Arbitrum One. Re-add the intended network and token contract before judging the recovery. Chain IDs identify execution environments; they do not change the private key derived from the seed.

MetaMask may require creating derived accounts in sequence until the original address reappears. A separately imported private key restores one account, unlike the mnemonic-backed key tree.

Why does the correct phrase restore the wrong-looking wallet?

A closer look is available in DeFi eligibility breakdown. The correct seed phrase looks wrong when the wallet applies a different derivation path, passphrase, account index, or network view.

Many Ethereum wallets derive the first externally owned account at m/44'/60'/0'/0/0, where SLIP-44 assigns coin type 60 to ETH. Another client may begin at a different index or expose another supported path. BIP-39 derives a 512-bit seed with PBKDF2-HMAC-SHA512, 2,048 iterations, and the exact optional passphrase as salt input. Every passphrase produces a valid seed, so a spelling or spacing difference reveals a different address set instead of reporting an error.

An Ethereum externally owned account uses a 20-byte address, displayed as 40 hexadecimal characters after the 0x prefix. Compare that address before signing. If it differs, return to the original path, passphrase, and account order; importing an individual 32-byte private key is the narrower alternative.

Software, hardware, and multisignature recovery models

Wallet choice changes the recovery interface, phrase format, and accounts restored even when several products share the same seed standard.

A seed-based MetaMask setup uses a 12-word Secret Recovery Phrase and restores accounts derived from that phrase; separately imported private keys and hardware accounts need their own recovery material. Rabby focuses on EVM networks and adds automatic chain selection plus transaction simulation. Its interface accepts seed-based or hardware-wallet accounts, yet a seed import recovers only the key tree represented by those words. Neither product turns local account labels into blockchain data.

Ledger devices generate a 24-word BIP-39 phrase and keep transaction signing on the hardware. Trezor supports 12-word or 24-word BIP-39 backups and 21-word SLIP-39 backups on compatible setups. The exact format chosen during initialization governs recovery compatibility, so replacing one hardware brand with another still requires matching the original standard and derivation path.

Safe changes the model again by requiring an owner threshold rather than one seed for the smart account itself. A 2-of-3 Safe remains operable when two configured owners can sign, although every owner wallet needs its own recovery plan. ERC-4337 smart accounts also support custom validation and recovery logic, but the deployed account implementation defines those rules. Threshold ownership distributes recovery authority more deliberately than a single externally owned account.

A recovery drill before any DeFi deposit

A recovery drill succeeds only when a clean wallet reproduces the expected public address before any sizeable DeFi position is funded.

Use a compatible spare device or isolated wallet profile, enter the backup through its recovery flow, apply the original passphrase, and derive accounts in order. Confirm the full public address on the intended chain, then check a known ERC-20 balance or protocol position. Reconnect Ledger or Trezor accounts separately, because the software seed does not include those device keys. Do not erase the only working installation to create this test environment.

The drill requires zero onchain transfers when it stops after address verification. Gas becomes relevant only if the test leads to key rotation (explained in detail ).

After restoration, record the wallet standard, word count, derivation path, chain IDs, imported-account boundaries, and any Safe threshold without placing the secrets beside the inventory. Repeat the drill after changing hardware, adding a BIP-39 passphrase, or moving to a new key tree. Existing DeFi positions need no special recovery transaction when the same address returns. A verified restoration provides stronger evidence than trusting an unread physical copy until device loss forces the issue.

What to know about DeFi wallets

What happens to an old seed backup after a full wallet migration?: An old seed phrase remains able to sign for every address derived from it after assets leave those addresses. Moving assets does not invalidate the key tree or cancel existing approvals. Keep the backup until you confirm all balances, NFTs, liquidity positions, and protocol claims were handled. Once the old addresses hold nothing needed, archive or destroy the backup under your documented retention plan.
Does changing a DeFi wallet password change its seed phrase?: Changing a wallet password does not change the seed phrase or any address derived from it. The password encrypts one application's local vault, while the seed rebuilds the key tree on another compatible installation. Store the password where it supports ordinary device access, and store the seed as an offline recovery asset. If you add a BIP-39 passphrase, record its existence separately because it participates in seed derivation and creates a different set of addresses on every compatible chain.
How long does a DeFi wallet recovery take?: A basic seed restore takes the time needed to install a compatible wallet, enter the words, derive accounts, and check addresses. Onchain waiting starts if you then move assets, revoke approvals, or change smart-account owners. Wallet indexing can delay the display of tokens or positions, but key derivation itself is local. Measure completion by the expected address appearing, not by a populated dashboard.
Where should heirs find DeFi wallet recovery instructions?: Recovery instructions for heirs should identify the wallet type, backup standard, network names, public addresses, and location of the offline material without placing every secret together. A seed phrase by itself may omit a BIP-39 passphrase, Safe threshold, hardware-wallet requirement, or separately imported key. Keep instructions understandable to the intended person and review them after migrations. Test the instructions before any planned handoff or device retirement. Legal ownership, access timing, and estate procedures belong in an appropriate local estate plan.
Must a DeFi protocol be online while the wallet derives its keys?: No DeFi protocol needs to be online while a standard seed phrase derives keys in a compatible wallet. BIP-39 and BIP-32 calculations run locally; a network connection then queries balances and positions. If Aave or Uniswap interfaces are unavailable, the address and contracts still exist, although another compatible interface may be needed to manage them. Recovery begins with address control, not a specific application screen.
What happens to ERC-20 approvals after restoring the same address?: Existing ERC-20 approvals remain attached to the recovered address because the approval lives in the token contract's onchain state, not in the wallet installation. Restoring the same key therefore restores authority to change or use that address, while a new application may not display every approval automatically during recovery. Review approvals by chain before retiring a wallet. Moving tokens to a new address does not itself erase allowances granted by the old address, although empty balances limit their practical effect.
Could one seed phrase recover both tokens and NFTs?: One compatible seed phrase regenerates the private keys for addresses holding ERC-20 tokens, ERC-721 NFTs, ERC-1155 assets, and DeFi positions. Asset standards do not create separate seed phrases. Visibility still depends on wallet support for the relevant chain and contracts. A Bitcoin account derived from the same mnemonic follows another coin type and address scheme, so cross-chain recovery requires more than accepting the words.
When should a seed phrase backup be replaced instead of recopied?: Replace a seed backup when it is incomplete, unreadable, exposed beyond the intended control boundary, or tied to a key set you plan to retire. Merely recopying the same words preserves the same keys. To change the key tree, generate a new wallet backup, verify the new receiving addresses, migrate each token and DeFi position across every relevant network, and retain the old material until all remaining claims are resolved. A fresh physical copy alone improves durability, not cryptographic separation.