[{"data":1,"prerenderedAt":44},["ShallowReactive",2],{"blog-content-en-how-to-test-your-seed-phrase-backup":3},{"slug":4,"title":5,"excerpt":6,"description":7,"bodyHtml":8,"faqItems":9,"howToSteps":19},"how-to-test-your-seed-phrase-backup","How to Test Your Seed Phrase Backup Without Risking Your Funds (Software Wallet Dry Run)","A backup you never tested is not a backup. This is the software-wallet version of a hardware dry run: restore your seed phrase on a second device, compare the first address on each chain, delete the test copy, and know what to do if it fails.","How to test a seed phrase backup safely: restore on a second device, compare addresses on each chain, never type it online, then delete the copy.","\u003Cblockquote>\u003Cstrong>A backup you never tested is not a backup.\u003C\u002Fstrong> To test one safely, keep your original wallet untouched. Restore from the written phrase only, on a second device (or, for an extension, a separate browser profile) while the original stays installed, then check that the first address on each chain you use (EVM, Solana, TON) matches the original exactly. Never type the phrase into a website or \"seed checker\". Delete the test copy afterwards, and if the addresses do not match, fix the backup or move your funds to a new wallet with a verified one.\u003C\u002Fblockquote>\n\u003Ch2>Why should you test a seed phrase backup before you need it?\u003C\u002Fh2>\n\u003Cp>You should test it because a bad backup only shows itself when you need it, and by then it is too late to fix. Typical failures are a misspelled word, two words swapped, a skipped word, handwriting that reads as a different letter (for example rn and m, or l and i), or an optional passphrase (sometimes called a 25th word) that was never written down. KeepKey's documentation lists examples such as \"flat\" written instead of \"float\".\u003C\u002Fp>\n\u003Cp>A BIP-39 checksum catches many typing errors but not all of them. A 12-word phrase carries only 4 checksum bits and a 24-word phrase carries 8, so some wrong phrases still pass as valid and simply open a different, empty wallet. BIP-39 also says every passphrase produces a valid wallet, so a wrong or forgotten passphrase gives no error, only an empty wallet. That is why you compare addresses instead of trusting \"phrase accepted\".\u003C\u002Fp>\n\u003Cp>Events in 2026 show when this matters. Exodus ended support for its Web3 Wallet extension on 1 October 2026, and Trust Wallet removed a batch of built-in networks on 15 September 2026. Moves like these push people to restore a seed phrase in another wallet, which is exactly when a bad backup comes to light. See what to do \u003Ca href=\"\u002Fblog\u002Fwallet-dropped-network-or-shut-down-what-to-do\">when a wallet drops a network or shuts down\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>What do hardware wallets do, and why do software wallets need a manual version?\u003C\u002Fh2>\n\u003Cp>Many hardware wallets offer a backup check, while software wallets usually only quiz you on a few words at setup and have no check you can run later. Trezor's \"Check backup\" (a dry run) asks you to re-enter your words, compares them with the backup stored on the device, and does not keep the re-entered words. Ledger introduced a RecoveryCheck app in 2018 to confirm a 24-word phrase without resetting the device (check Ledger's current support pages for the present method). KeepKey asks you to enter words from your paper backup rather than from memory.\u003C\u002Fp>\n\u003Cp>The manual equivalent for a software wallet is a parallel restore: restore on a separate instance while the original stays intact, then compare the derived addresses. One rule is non-negotiable. Never delete or reset your only working wallet to test the backup, because if the backup is bad, that deletion is what loses the funds.\u003C\u002Fp>\n\u003Ch2>Which test environment is safe?\u003C\u002Fh2>\n\u003Cp>The safest environment is a device you control with no unknown extensions or remote-access tools. Use a second phone or computer if you have one. If you do not have a second phone, use a second computer, or on a desktop use a separate browser profile with a fresh install of the official extension from the official store or website (see \u003Ca href=\"\u002Fblog\u002Ffake-wallet-apps-how-to-avoid\">how to install only the official app\u003C\u002Fa>). Never uninstall or reset the original app to make room for the test. On a single phone with no other device, do not run the test on that phone. Go offline during the restore where practical.\u003C\u002Fp>\n\u003Cp>The trade-off is that every test restore creates another copy of your keys on that device for as long as it exists. Delete it right after, and never use a shared, work or public computer.\u003C\u002Fp>\n\u003Cp>Never use online \"seed validators\", \"BIP39 checkers\" or \"wallet sync\" sites, and never put the phrase in chats, cloud notes, screenshots, email or AI chatbots. Anything that receives the phrase can empty your wallet, and this is a classic \u003Ca href=\"\u002Fblog\u002Fhow-to-spot-crypto-phishing\">phishing pattern\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>How do you run a dry-run restore, step by step?\u003C\u002Fh2>\n\u003Cp>A dry-run restore means restoring your wallet from the written backup on a separate instance, only to compare addresses, and then deleting that copy. It moves no funds.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Prepare.\u003C\u002Fstrong> Choose the test environment above and leave the original wallet untouched.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Record the originals.\u003C\u002Fstrong> In the original wallet, note the first receiving address (account 1) on every chain you hold funds on: one EVM address (in most wallets the same on Ethereum, Arbitrum, Base and other EVM networks, but check each network you use), one Solana address and one TON address. The first and last 6 characters are enough, and addresses are public. If you use more than one account, also compare each account that holds funds. An account you imported with a private key is not recovered by the seed phrase and needs its own backup.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Restore from the paper.\u003C\u002Fstrong> Type the words only from the written or metal backup, not from memory and not from the original app's reveal screen. Testing the physical copy is the whole point.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Compare.\u003C\u002Fstrong> Check every character, or at least the first and last 6. For TON, one wallet can appear as EQ… (bounceable) or UQ… (non-bounceable), and the two forms differ in their prefix and checksum characters, so compare in the same format (see \u003Ca href=\"\u002Fblog\u002Fcrypto-address-formats-explained\">crypto address formats explained\u003C\u002Fa>). Optionally confirm that the restored wallet shows the same balance instead of sending a test transaction.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Troubleshoot a mismatch.\u003C\u002Fstrong> If any address differs, work through the next section.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Wipe the copy.\u003C\u002Fstrong> When the test is finished, delete the test wallet from the second device and clear clipboard and app data.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Replace a backup you cannot fix.\u003C\u002Fstrong> Create a new wallet with a verified backup and move your funds to it.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Re-test later.\u003C\u002Fstrong> Repeat after any change to the backup and on a calendar reminder.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>What if the restored addresses do not match?\u003C\u002Fh2>\n\u003Cp>A mismatch usually means the paper and the original wallet differ somewhere, so suspect human error first. Check word order, spelling against the 2,048-word BIP-39 list (the first 4 letters identify each word), the word count, and whether a passphrase was used.\u003C\u002Fp>\n\u003Cp>If the EVM address matches but Solana or TON differ, the cause is often a different derivation path or TON wallet version (v4R2 versus W5) between wallets, not a bad backup. See \u003Ca href=\"\u002Fblog\u002Fimported-seed-phrase-wallet-empty-derivation-path\">different derivation paths and TON wallet versions\u003C\u002Fa>. If the wallet rejects the phrase as invalid, or no address matches even after you check word order, spelling, word count and passphrase, treat the backup as failed.\u003C\u002Fp>\n\u003Ch2>What should you do after a failed test?\u003C\u002Fh2>\n\u003Cp>Your funds are still safe while the original wallet works, and the danger is losing that device later with a broken backup. If you can re-check the phrase in the original app, correct the paper backup and re-test.\u003C\u002Fp>\n\u003Cp>If you cannot produce a backup that passes, create a new wallet, write down its phrase, verify it with this same test, and then \u003Ca href=\"\u002Fblog\u002Fhow-to-move-crypto-to-a-new-wallet-safely\">move your funds to a new wallet with a verified backup\u003C\u002Fa>. Trezor's guidance is the same: if the backup fails and you cannot enter the correct one, move your funds to a new wallet right away. Do not wait for a lost phone; see \u003Ca href=\"\u002Fblog\u002Fwhat-happens-if-you-lose-phone-crypto-wallet\">what happens if you lose your phone\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>How do you clean up, and when should you re-test?\u003C\u002Fh2>\n\u003Cp>Delete the test wallet in the app, uninstall it or clear the extension data, and clear any clipboard history. Re-test after any change to the backup (a new metal plate, a copy for inheritance, a new location) and on a calendar reminder, such as once a year. For storage advice, read \u003Ca href=\"\u002Fblog\u002Fwhat-is-a-seed-phrase\">how to store and protect your seed phrase\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>How this applies to WATS Wallet\u003C\u002Fh2>\n\u003Cp>WATS Wallet, made by Alltoscan LLC, is fully non-custodial and not seedless. WATS never holds a key, so your recovery phrase is the only way to restore the wallet, which is why testing it matters. Run the dry run above on a second device, or a separate browser profile for the extension, while the original stays installed and untouched, and compare the EVM address, the Solana address and the TON address that WATS Wallet shows, on each network you hold funds on.\u003C\u002Fp>\n\u003Cp>The optional WATS NFC Metal Card holds no private keys and is not a backup or cold storage. It is tap-to-authenticate in the mobile app and is not part of this test. Restoring and comparing needs no transaction. If you later move funds, EVM fees are charged in ATS from one BSC balance (see \u003Ca href=\"\u002Fats-fee\">how ATS fees work\u003C\u002Fa>), while fees on TON are paid in ATS too and Solana pays in SOL.\u003C\u002Fp>\n",[10,13,16],{"q":11,"a":12},"Is it safe to type my seed phrase into a seed phrase checker website?","No. Any website, form, browser validator, chat or AI tool that receives your phrase can empty your wallet, and this is a common phishing pattern. Test only by restoring in the official wallet app on a device you control, then delete that copy. Nobody legitimate, including wallet support, will ever ask for your phrase.",{"q":14,"a":15},"Can I test my backup by deleting my wallet and restoring it on the same phone?","Avoid it. If the backup is wrong, deleting your only working copy is exactly how funds are lost. Restore on a second device, or a separate browser profile for the extension, while the original stays installed and untouched, compare the addresses, and delete the test copy only after you have your result.",{"q":17,"a":18},"How often should I test my seed phrase backup?","Test once right after creating it, again after any change to the backup (a new metal plate, a new copy, a new location or passphrase), and periodically, for example once a year on a calendar reminder. Re-test before relying on the backup in a migration such as moving to a new wallet.",[20,23,26,29,32,35,38,41],{"title":21,"body":22},"Choose a safe test environment","Use a second device you control, or a separate browser profile for the extension, offline where practical. Keep the original wallet installed and untouched, and never uninstall or reset it to make room for the test.",{"title":24,"body":25},"Write down the original addresses","In the original wallet, note the first receiving address on each chain you use: one EVM address, one Solana address and one TON address. The first and last 6 characters are enough.",{"title":27,"body":28},"Restore from the written backup only","Type the words from the paper or metal backup, never from memory, and never into a website, form, chat, cloud note or seed validator.",{"title":30,"body":31},"Compare the addresses","Check the restored addresses against the originals character by character, or at least the first and last 6 characters. Compare TON addresses in the same EQ or UQ format.",{"title":33,"body":34},"Troubleshoot a mismatch","Check word order, spelling, word count and passphrase, then derivation paths and TON wallet versions if only Solana or TON differ.",{"title":36,"body":37},"Delete the test copy","When the test is finished, delete the test wallet from the second device and clear clipboard and app data.",{"title":39,"body":40},"Replace a backup that cannot be fixed","If the backup cannot be corrected, create a new wallet with a verified backup and move your funds to it.",{"title":42,"body":43},"Re-test on a schedule","Re-test after any change to the backup and on a calendar reminder, such as once a year.",1792535018607]