How to import UniSat Wallet to a new device? (Recovery Guide)

Understanding UniSat Wallet Recovery Process

1. UniSat Wallet is a non-custodial Bitcoin Ordinals wallet designed for the Bitcoin blockchain. It does not store private keys on remote servers. All cryptographic material resides solely with the user.

2. Recovery relies entirely on the 12-word mnemonic seed phrase generated during initial wallet setup. This phrase must be recorded offline and kept secure before any funds are received.

3. The seed phrase is mathematically deterministic—entering it correctly in any compatible BIP-39 implementation will regenerate the exact same set of addresses and private keys.

4. UniSat Wallet uses the standard BIP-39 wordlist and follows BIP-44 derivation path for Bitcoin addresses: m/44'/0'/0'/0/i.

5. No account credentials, passwords, or biometric data can substitute for the seed phrase. Without it, wallet access is permanently lost.

Step-by-Step Import Procedure

1. Download the official UniSat Wallet application from its verified website or trusted app store. Avoid third-party links or unofficial APK/IPA files.

2. Launch the app and select “Import Wallet” instead of “Create New Wallet” on the welcome screen.

3. Enter the full 12-word seed phrase exactly as written—case-insensitive but order-sensitive. Spaces between words must be preserved; no extra characters or punctuation allowed.

4. Confirm the phrase by re-entering it in the designated field. Some versions may require selecting words from a scrambled list to verify attention.

5. Set a new local password or PIN. This encrypts the wallet file on the device but does not affect seed-based recovery across devices.

Verifying Imported Balance and Addresses

1. After import completes, the wallet automatically scans the Bitcoin blockchain for transactions associated with derived addresses.

2. Check the main balance display. If zero appears despite prior activity, manually trigger a rescan using the “Resync Blockchain” option in settings.

3. Navigate to the “Receive” tab and compare the first receiving address with one previously used. Matching addresses confirm successful derivation.

4. Open the “Transactions” history and validate that past inscriptions and BTC transfers appear chronologically and with correct amounts.

5. Send a small test inscription or satoshis to a known external address to confirm signing capability and network broadcast functionality.

Security Considerations During Device Migration

1. Never type or paste your seed phrase into web browsers, chat apps, cloud notes, or email—even encrypted ones. These environments are outside UniSat’s security boundary.

2. Ensure the new device is free of malware. Use reputable antivirus tools and avoid rooted or jailbroken systems where keyloggers may intercept input.

3. Disable clipboard sharing features between devices. Some operating systems synchronize clipboard history across logged-in accounts, exposing sensitive data.

4. After confirming full functionality, delete any temporary screenshots or text files containing the seed phrase from both old and new devices.

5. Never share your seed phrase with anyone—including UniSat support staff, developers, or community moderators. Legitimate representatives will never ask for it.

Frequently Asked Questions

Q: Can I import UniSat Wallet using only my password or fingerprint?A: No. Passwords and biometrics only unlock the local encrypted wallet file. They cannot reconstruct private keys without the original seed phrase.

Q: What happens if I mistype one word in the seed phrase?A: The wallet will derive completely different addresses and balances. There is no partial recovery—the entire phrase must match exactly.

Q: Does UniSat support importing from other wallets like Xverse or Leather?A: Only if those wallets use identical BIP-39 + BIP-44 derivation for Bitcoin. UniSat does not support Ethereum-style keystore files or non-standard paths.

Q: Can I import the same seed phrase into multiple devices simultaneously?A: Yes. Each instance operates independently. However, concurrent usage may cause transaction conflicts or double-spending if uncoordinated.