Recover control without exposing secrets.

Build a recovery plan from wallet clues, run public checks when you have a public address, then move secret material into a local vault only when the risk is visible.

Local-onlyCloud recovery forms never accept seed phrases, private keys, passwords, or wallet files.

Guided first pass

Choose what you have. UCIR will route it to the safe place.

Start from the clue in your hand. Public clues can be checked by UCIR; phrases, keys, passwords, and files stay in the local vault on this device.

No starting point selectedPick the closest option above, then follow the highlighted next action.

Recommended next move

Start with public clues. Use the local vault only after the plan is visible.

UCIR keeps the first pass cloud-safe: wallet name, chain, year, public address, and public contract clues. Secret material belongs only in the browser-local vault.

Choose your case

Pick the closest situation.

Start recovery

Use remembered facts and public clues. Keep secret material in the browser-only local vault below.

Cloud-safe

Wallet or appAsset family or networkChoose Ethereum-style for 0x wallets, including many L2s and sidechains.Last time you used it

SupportedEthereum-style wallets

Ethereum, Base, Polygon, Arbitrum, Optimism, BNB, Avalanche

Use this when the address starts with 0x. UCIR can derive and sign EVM paths locally; live public scans currently focus on Ethereum-mainnet evidence plus entered token, NFT, and approval targets.

SupportedSolana wallets

Phantom, Magic Eden, Ledger Solana, Solflare-style addresses

Use this for Solana public keys and keypair files. UCIR checks public account, token, stake, and authority evidence while keeping wallet-version gaps visible.

SupportedBitcoin wallets

bc1q, bc1p, 1..., 3..., approved xpub/ypub/zpub clues

Use this for Bitcoin addresses, approved public xpubs, or WIF imports. UCIR checks public activity and UTXOs while keeping wallet.dat archaeology marked for review.

Review firstOther or uncertain chain

Unknown appchain, historical fork, testnet, abandoned wallet, or unclear clue

Use this when the chain is not obvious. UCIR creates a secret-free support brief and blocks local derivation, signing, and automated scans until the chain is mapped.

Public clue typePublic clue, optionalCase notes for exported brief, optionalThese notes stay in this browser until you copy, email, or download the support brief.

Advanced public checksAdd a token, NFT, approval spender, or chain-specific public check only if you already know it.

Asset check, optionalEVM public addresses only.Token or NFT contractUse when you remember a specific public contract.Token IDApproval spenderChecks ERC-20 allowance for the token contract above.

EVM public checksAdd a token, NFT contract, or approval spender only if you remember one.

I will enter only public clues here; seed phrases, private keys, passwords, and wallet files belong in the Local vault.

Local vault

Derive a public address on this device. The phrase is never sent to UCIR servers.

Browser-only

Local resultNo phrase loadedPublic address will appear here after local derivation.

Local lab preflight

Route local-secret fixtures to this browser before treating lab evidence as usable.

Local-only

Known public EVM addresses, optionalUCIR compares browser-local candidate paths against each public target without uploading the phrase.

Lab routeWaiting for local public addressDerive an EVM phrase locally before running the public-target comparison.

Proof message

After local EVM recovery, sign a public control proof without moving assets.

Optional proof

Proof message

Proof outputProof not signedSign a public EVM message after local derivation or import. This does not move assets.

Asset transfer

Quote publicly, sign supported EVM, Solana, or Bitcoin transfers in this browser, then broadcast through the supported public RPC path.

Local signing

Transfer outputTransfer not preparedLoad an EVM key, enter a destination and amount, then quote the transaction before signing.

Current stateReady for safe clues

Build a plan to see ranked paths, safe public checks, local vault status, and remaining risk.

Case focus

First: confirm what can leave this device.

Check boundary

Use cloud fields for public clues only. Keep recovery phrases, private keys, passwords, and wallet files in the browser-local vault.

Safe for cloudWallet app, network, year, public address, xpub, tx, or explorer link

Keep localPhrase, private key, password, keystore, keypair, WIF, or wallet file

Case readiness

Ready for first safe clue

0 / 5 ready

1
Safe clueConfirm the public-only boundary before cloud checks.
2
Recovery planGenerate ranked paths and visible next actions.
3
Public evidenceAttach public-chain evidence or keep the gap explicit.
4
Local proofAdd browser-local output only when it helps the case.
5
Review packetCreate the descriptor-only packet for handoff.

Start with public clues. Do not enter seed phrases, private keys, passwords, or wallet files into cloud fields.

Review depth

No public scan attached

0 checks

Run a public scan to show which evidence was checked, which checks are bounded, and which residuals remain open.

Public scan waitingBuild a plan or paste a public clue, then run the public scan.

Next safe actions

Build a plan to activate this checklist.

Likely path checks

Wallet and chain clues decide the first local checks.

Public scan evidence

Run a public scan to attach live evidence.

Recovery packet

Packet typeChoose the review context before generating the support brief and audit JSON.

Packet waiting

Build a plan or run a public scan, then generate a descriptor-only packet for review or support.

No packet yetSecret phrases and passphrases are never included.

Email review request

Evidence path

Evidence first

Recovery phrase referenceRanked derivation candidatesVersioned wallet behaviorPublic EVM addressPublic Solana addressOwner authority

points toSecret: recovery phrase reference -> Path check: candidate paths

points toPath check: candidate paths -> Public address: public evm

points toPath check: candidate paths -> Public address: public solana

shows control ofPublic address: public evm -> Authority: owner

Open risks

14 open risks

wallet.dat, Berkeley DB, Armory, MultiBit, Electrum historical recovery corpushigh / needs review

Use local public xpub/ypub/zpub extraction and single-WIF text-export staging as a first pass, then create crypto archaeology entries for encrypted, private-key, wallet.dat, Berkeley DB, Armory, MultiBit, and non-public historical wallet formats.

Historical EVM wallet derivation variantshigh / needs review

Use the historical EVM first-pass candidates for local address checks, then build version-specific fixtures and documentation for MEW, early Ledger, early Trezor, Mist, Parity, imToken, Jaxx, Exodus, and mobile wallets before treating this corpus as resolved.

Magic Eden Solana derivation and export behavior by wallet versionhigh / needs review

Use the inferred Magic Eden first-pass and fallback Solana derivation contracts for local checks, then verify exact app-version behavior with documentation, app behavior, and local test vectors before moving assets.

Knowledge files12

Recovery rules19

Safe scans4

Recover control without exposing secrets.

Choose what you have. UCIR will route it to the safe place.

Start with public clues. Use the local vault only after the plan is visible.

Pick the closest situation.

Start recovery

Local vault

Local lab preflight

Proof message

Asset transfer

First: confirm what can leave this device.

Ready for first safe clue

No public scan attached

Next safe actions

Likely path checks

Public scan evidence

Recovery packet

Action planner