Wallet coverage & recovery capabilities
This page documents compatibility and routing signals for common wallet exports and recovery inputs. It is not a guarantee of recovery. Execution depends on the wallet export surface, schema versions, and data completeness.
Open desktop downloads
Offline engine, legacy schema handlers, deeper analysis.
Web flow performs initial routing and format checks. Complex cases run in the desktop tool.
| Wallet | Type | Family | Script types | Inputs | Typical exports / inputs | Notes |
|---|---|---|---|---|---|---|
|
Ledger Nano S
ledger-nano-s · UTXO
|
Hardware | UTXO | BIP49 BIP84 | Address xpub Descriptor |
xpub export (account)
App metadata (coin/purpose)
|
Desktop recommended for legacy app variants and mixed purpose accounts. |
|
Typical exports
xpub (account), address set, app/coin selection metadata.
Derivation
BIP49/BIP84 accounts; purpose mismatches are common between apps.
Known pitfalls
Wrong purpose, missing change chain, coin_type differences across apps.
Next step
Use desktop for deep scanning and legacy schema handlers.
|
||||||
|
Ledger Nano X
ledger-nano-x · UTXO
|
Hardware | UTXO | BIP49 BIP84 | Address xpub Descriptor |
xpub export (account)
Wallet app selection
|
Similar surface to Nano S; most issues are purpose / account selection. |
|
Typical exports xpub, address lists, app coin/purpose selection. Derivation BIP49/BIP84; some flows expose only account-level xpub. Known pitfalls Change chain not scanned; mixed-purpose accounts in same wallet. Next step Desktop for deeper scans and export-normalization. |
||||||
|
Trezor One
trezor-one · UTXO
|
Hardware | UTXO | BIP44 BIP49 BIP84 | Address xpub Backup |
xpub / public export
Wallet metadata / account
|
Legacy (BIP44) remains common on older setups; ensure purpose matches address type. |
|
Typical exports xpub, account selection, address type info. Derivation BIP44/49/84; purpose mismatch is the #1 issue. Known pitfalls Wrong account index, missing change chain, passphrase context. Next step Desktop if history is fragmented across purposes or exports are partial. |
||||||
|
Trezor Model T
trezor-model-t · UTXO
|
Hardware | UTXO | BIP44 BIP49 BIP84 | Address xpub Backup |
xpub / account export
Address type metadata
|
Same class as Trezor One; desktop helps with multi-account/coin_type variations. |
|
Typical exports xpub/account, address-type/purpose indicators. Derivation BIP44/49/84; passphrase may change effective seed. Known pitfalls Wrong account/purpose, missing change branch. Next step Desktop for scanning and normalization of wallet exports. |
||||||
|
Coldcard Mk4
coldcard-mk4 · UTXO
|
Hardware | UTXO | BIP84 BIP86 BIP48 Custom | PSBT Descriptor xpub |
Descriptors / policy export
PSBT signing context
|
Strong signals when descriptors are available; multisig depends on full policy/cosigners. |
|
Typical exports Descriptors (single-sig/multisig), PSBT, xpub set. Derivation BIP84/BIP86; multisig BIP48 depends on policy. Known pitfalls Missing cosigner xpubs, wrong policy, incomplete descriptor set. Next step Desktop for policy reconstruction and deeper validation. |
||||||
|
BitBox02
bitbox02 · UTXO
|
Hardware | UTXO | BIP84 BIP48 | Descriptor PSBT Backup |
Descriptor/policy export
PSBT / signing data
|
Routing is strong with descriptors; multisig requires full policy representation. |
|
Typical exports Descriptors, PSBT, xpub/policy fragments. Derivation Primarily BIP84; multisig BIP48 scenario dependent. Known pitfalls Partial exports, missing cosigner keys, policy mismatch. Next step Desktop for validation and policy reconstruction. |
||||||
|
Passport (Foundation)
passport-foundation · UTXO
|
Hardware | UTXO | BIP84 BIP48 Custom | Descriptor PSBT xpub |
Descriptor export
PSBT context
|
Descriptors provide best routing; custom policies vary by setup. |
|
Typical exports Descriptors, policy fragments, PSBT. Derivation BIP84; multisig/custom depends on policy settings. Known pitfalls Incomplete descriptor set; missing cosigner/policy detail. Next step Desktop recommended for custom policy flows. |
||||||
|
Keystone 3 Pro
keystone-3-pro · UTXO
|
Hardware | UTXO | BIP44 BIP84 BIP86 BIP48 | Address Descriptor PSBT |
Address + account info
Descriptor/PSBT (if enabled)
|
Multiple script types; ensure purpose and account match the observed address set. |
|
Typical exports Address sets, account metadata, descriptors/PSBT in advanced flows. Derivation BIP44/49/84/86; multisig BIP48 setup dependent. Known pitfalls Purpose mismatch, missing change chain, partial export surface. Next step Desktop for mixed-purpose and multisig policy validation. |
||||||
|
Electrum
Bitcoin wallet
|
Software | UTXO | Custom BIP84 BIP48 BIP86 | Backup Descriptor PSBT |
Wallet file / JSON export
Descriptor / xpub / PSBT
|
Very flexible; signals depend on whether descriptor/policy data is present. |
|
Typical exports Wallet file, descriptors, xpubs, PSBT for signing context. Derivation Can be BIP-like or custom; descriptor-based is strongest. Known pitfalls Custom paths, multisig cosigner completeness, multiple wallets/aliases. Next step Desktop for descriptor normalization and advanced scanning. |
||||||
|
Sparrow Wallet
sparrow · UTXO
|
Software | UTXO | BIP84 BIP86 BIP48 Custom | Descriptor PSBT Backup |
Descriptor / policy
PSBT flow artifacts
|
Descriptor-first wallet; multisig works best with complete policy + cosigners. |
|
Typical exports Descriptors/policies, PSBT, cosigner xpub sets. Derivation BIP84/86; multisig BIP48 is common. Known pitfalls Missing cosigner, incomplete policy, mixed descriptors. Next step Desktop for policy reconstruction and validation. |
||||||
|
Bitcoin Core
Bitcoin / UTXO
|
Software | UTXO | Custom | Backup Address Key |
wallet.dat / directory
|
Often requires desktop workflows; proprietary formats and node context may apply. |
|
Typical exports wallet.dat (and related metadata depending on version). Derivation Custom/internal; not a simple BIP-purpose mapping. Known pitfalls Missing context, encryption/passphrase, multiwallet directories. Next step Desktop tool is recommended for offline analysis. |
||||||
|
Wasabi Wallet
wasabi · UTXO
|
Software | UTXO | BIP84 BIP86 Custom | Backup Descriptor PSBT |
Wallet file / backup
Descriptor/policy (varies)
|
Coverage depends on export surface; desktop helps when schema/version differs. |
|
Typical exports Wallet file/backup; descriptors may be available depending on version. Derivation BIP84 primary; Taproot/custom varies by setup. Known pitfalls Export gaps, version changes, missing change chain context. Next step Desktop for schema handlers and offline analysis workflow. |
||||||
|
BlueWallet
bluewallet · UTXO
|
Mobile | UTXO | BIP84 BIP48 Custom | Backup xpub Descriptor |
App backup / export
xpub / multisig data (if used)
|
Multisig depends on cosigner completeness; purpose mismatches occur on migrations. |
|
Typical exports App backup, xpub, multisig configuration when applicable. Derivation BIP84 common; multisig/policies vary. Known pitfalls Missing cosigner, inconsistent export fields, wrong purpose on restore. Next step Desktop for multisig and legacy export handlers. |
||||||
|
Blockstream Green
greenaddress · UTXO
|
Mobile | UTXO | BIP48 Custom BIP84 | Descriptor Backup Address |
App export / backup
Multisig policy (scenario)
|
Policy/multisig flows are conditional; desktop recommended for multi-party reconstruction. |
|
Typical exports Backup/export; policy/descriptor surface depends on setup. Derivation Often BIP84; multisig/policy is conditional. Known pitfalls Missing policy/cosigners, partial exports, different app versions. Next step Desktop for policy validation and deeper schema interpretation. |
||||||
|
MetaMask
EVM wallets
|
Software | EVM | Custom | Address Backup Key |
Address / account list
|
EVM routing is address-first; key material coverage depends on export format availability. |
|
Typical exports Address/account identifiers; structured exports vary by environment. Derivation EVM account-based; path inference is conditional on available data. Known pitfalls Missing account indexes, multiple accounts, chain selection mismatch. Next step Desktop for deeper analysis and legacy schema handlers. |
||||||
|
Trust Wallet
Mobile · multi-asset
|
Mobile | EVM | Custom | Address Backup Key |
Address / wallet ID
|
EVM chain routing depends on address + chain context; export surface varies by platform. |
|
Typical exports Address identifiers; some scenarios provide structured backups. Derivation Account-based; path inference depends on export completeness. Known pitfalls Wrong chain selection, incomplete account mapping. Next step Desktop for deeper schema interpretation and offline analysis. |
||||||
|
Phantom
Solana
|
Software | Other | Custom | Address Backup Key |
Address / wallet ID
|
Non-UTXO/non-EVM; classification/routing is supported, execution depends on export surface. |
|
Typical exports Address identifiers; structured backups are scenario-dependent. Derivation Custom; network-specific account models. Known pitfalls Missing chain context, incomplete export fields. Next step Desktop for network-specific handlers and deeper analysis. |
||||||
|
Keplr
Cosmos
|
Software | Other | Custom | Address Key/export Seed |
Bech32 address / pubkey
Chain prefix + HD path
|
Chain prefixes and HD paths vary by zone; include target chain context. |
|
Typical exports Address/public key per chain; optional key export. Derivation Cosmos HD paths with chain-specific prefixes. Known pitfalls Wrong chain/prefix, missing account index, multisig contexts not portable. Next step Attach address + chain context; desktop for deep scan/export parsing. |
||||||
|
Exodus
exodus · Other
|
Software | Other | Custom | Backup Address Key |
App export / backup
Address / asset context
|
Multi-asset exports vary; routing can classify structure but execution depends on exported fragments. |
|
Typical exports Backup/export artifacts; per-asset fragments may be partial. Derivation Network-dependent; not a single-purpose model. Known pitfalls Partial exports, missing chain context, proprietary schema variants. Next step Desktop for legacy schema handlers and offline analysis workflow. |
||||||
|
Zeus LN
zeus-lightning · Lightning
|
Lightning | UTXO | Custom | Backup Address Key |
Node/remote config
Channel state (scenario)
|
Lightning scenarios are highly data-dependent; desktop recommended for deep diagnostics. |
|
Typical exports Config fragments; channel/state artifacts are scenario-dependent. Derivation Custom; node/channel model differs from typical BIP scanning. Known pitfalls Missing channel DB/state, incomplete config, remote node context. Next step Desktop for offline analysis and legacy handlers. |
||||||
|
Blixt (LND)
blixt-lnd · Lightning
|
Lightning | UTXO | Custom | Backup Address Key |
Config + seed container (varies)
State/channel data (scenario)
|
Lightning recovery varies by data availability; use desktop for deeper routing and checks. |
|
Typical exports Config files and state artifacts depending on setup. Derivation Custom; depends on node model and storage. Known pitfalls Missing channel DB/state, partial exports, remote dependencies. Next step Desktop for offline analysis and diagnostic workflow. |
||||||
|
BTCPay Server (Coldcard)
btcpay-coldcard · Combo
|
Combo | UTXO | BIP84 BIP48 Custom | Descriptor PSBT Backup |
Store descriptor export
PSBT signing artifacts
|
Descriptor-based setups are strongest; multisig depends on full policy and cosigner set. |
|
Typical exports Store descriptors, policy, PSBT artifacts. Derivation BIP84 common; BIP48 for multisig configurations. Known pitfalls Missing policy/cosigners, partial descriptor export. Next step Desktop for policy validation and deeper analysis. |
||||||
|
Tangem Wallet 2.0
tangem-2 · UTXO
|
Hardware | UTXO | BIP84 BIP86 Custom | Address Backup Key |
Address / wallet ID
Backup (if enabled)
|
Export surface varies by mode; routing works best with clear address context and purpose. |
|
Typical exports Address identifiers; backups depend on product mode. Derivation Scenario-dependent; purpose inference is conditional. Known pitfalls Missing purpose/context, partial export surface. Next step Desktop for deeper schema interpretation. |
||||||
|
Atomic Wallet
atomic-wallet · Other
|
Software | Other | Custom | Backup Address |
App backup / export
Address / asset context
|
Exports can be non-standard; classification works, execution depends on structured fragments. |
|
Typical exports Export/backup artifacts; per-asset content varies. Derivation Network-dependent; custom schema variants exist. Known pitfalls Partial exports, missing chain context, schema variability. Next step Desktop for legacy schema handlers and offline workflow. |
||||||
|
Cake Wallet
cakewallet · Other
|
Mobile | Other | Custom | Backup Address |
App export / backup
Address / asset context
|
Multi-asset; routing can classify, execution depends on export completeness and chain context. |
|
Typical exports Backup/export; per-network artifacts vary. Derivation Network-specific; not a single BIP-purpose model. Known pitfalls Partial exports; chain context mismatch; schema differences across versions. Next step Desktop recommended for deep analysis and legacy handlers. |
||||||
No wallets match your filters. Try clearing one of the filters or search terms.
How to read indicators
Indicators describe routing and compatibility signals. They are not a promise of recovery. Execution depends on wallet export surface, schema versions, and the completeness of the data you can provide.
- Primary — typical exports provide reliable routing signals.
- Conditional — supported in compatible scenarios; usually requires specific exports (descriptor/policy/keystore) or additional context.
- Not typical — non-standard exports; classification still works, execution often requires desktop workflow.
Never paste seed phrases. Use structured exports (descriptor, xpub, PSBT, keystore JSON, backups) where available.
Typical inputs and what they unlock
Backup file (ZIP/JSON/DAT/TXT)
Detects wallet family and extracts recognizable fragments (headers, keystore blobs, indexes, metadata).
Address / wallet identifier
Enables chain selection and completeness checks (wrong purpose, missing change chain, mismatch).
Key material
In compatible scenarios, xpub/descriptors/WIF improve path inference. Coverage varies by wallet schema.
PSBT / descriptors
Best surface for UTXO policies: descriptors encode spending conditions; PSBT reflects signing context.
Common pitfalls we flag during routing
- Passphrase enabled — correct routing often depends on passphrase context.
- Wrong purpose — BIP44 vs BIP49/84/86 mismatch changes address/script type.
- coin_type differences — wallet-specific mapping can shift accounts.
- Missing change chain — funds can be on change addresses; partial scans look “empty”.
- Multisig incomplete — missing cosigners/policy produces ambiguous reconstruction.
- Export incomplete — classifiable but not executable without required fragments.
Recommended next step
Use the web flow for fast intake, routing, and format checks. If a wallet row is Conditional or Not typical (or exports are partial), continue in the desktop tool for legacy handlers, offline analysis, and deeper schema interpretation.