Find the right wallet path
Start with the wallet, year, and chain you remember. UCIR ranks likely derivation paths before asking for anything sensitive.
Private wallet recovery desk
Recover wallet control without handing over your secrets.
UCIR turns wallet clues into an evidence-backed recovery path, checks public chains first, then keeps seed phrases, private keys, and wallet files inside your browser when local action is needed.
- 0
- secret values accepted by cloud forms
- 3
- major asset families covered
- 7
- secret-free packet workflows
When UCIR fits
For high-stakes wallet recovery where guessing is expensive.
- You remember the wallet app but not the derivation path.
- You found an old phrase, key, wallet file, or hardware wallet.
- You need to revoke approvals or move assets after control is proven.
- You are helping a family, founder, or team recover without exposing secrets.
What UCIR does
A practical recovery flow for people who only remember fragments.
Check public evidence
Run balance, token, approval, and UTXO checks from public descriptors so the next step is grounded in live network data.
Recover control locally
Derive addresses, prepare transfers, sign, and broadcast supported actions from a browser-local vault after explicit consent.
Recovery sequence
Public evidence first. Local action last.
Map what you know
Start with wallet name, chain, year, public address, token contract, or approved xpub.
Check public state
UCIR probes public-chain evidence first so the recovery path is based on current network data.
Generate a packet
Export a descriptor-only packet for review, support, or handoff without including secret values.
Act locally
Only then use the browser vault to derive, prove control, sign transfers, or revoke approvals.
Ethereum / EVMNative ETH, ERC-20, ERC-721, ERC-1155 quote and local signing paths
SolanaSOL, SPL token, Token-2022 quote paths with wallet-based token account discovery
BitcoinBIP44, BIP49, BIP84, and BIP86 recovery, UTXO selection, and local signing
Private review readiness
Know what to bring before you ask for help.
UCIR is built for cases where enough public context exists to create a safe brief before anyone touches secret material.
Bring safely
- Wallet app, hardware wallet, chain, and approximate year
- Public address, transaction, explorer link, or approved xpub
- Exchange ticket, bridge receipt, public support case, or public contract
Keep local
- Seed phrase, mnemonic, private key, or secret share
- Wallet password, keystore password, wallet file, or signing material
- Unsigned requests from unknown support desks or unverified recipients
Review outcome
- Secret-free support brief and machine-readable packet
- Visible public evidence, blocked checks, and open residuals
- A clear split between supported local actions and private review needs
Not sure where your case fits?Start with public clues in the app. Unsupported chains and unresolved checks stay marked for review instead of becoming unsafe instructions.Build readiness packet
How to engage
Pick the case path, generate the packet, then decide who reviews it.
Start in minutes
Self-guided evidence packet
For owners who want a safe first read before touching a phrase, key, or wallet file.
- Public-clue plan
- Open-risk checklist
- Secret-free support brief
For shared responsibility
Family or founder handoff
For estates, founders, and teams that need a reviewable case file without exposing secrets.
- Role-safe case summary
- Evidence and uncertainty split
- Machine-readable audit JSON
For time-sensitive risk
Compromise response
For wallets that may need approvals revoked, assets moved, or custodian support evidence.
- Public exposure scan
- Local-action boundary
- Exchange or custodian brief
For support desks
Exchange or custodian support
For cases that need a clean public-evidence brief before talking to an exchange, custodian, or platform team.
- Support-ready timeline
- Public descriptor summary
- Uncertainty and open-check list
For cross-chain trails
Bridge activity review
For wallets with wrapper, bridge, or pending-message questions that need to stay separate from final proof.
- Bridge evidence frame
- Pending-state checklist
- Review-safe support brief
For historical claims
Fork claim review
For fork, airdrop, or historical eligibility checks where unverified claim paths must stay marked as open.
- Claim-path checklist
- Public evidence packet
- Open-risk markers
For overlooked value
Forgotten asset review
For old wallets that may still have unlisted assets, staking leftovers, NFT holdings, or payout traces.
- Asset-lead checklist
- Coverage-sensitive review
- Secret-free audit JSON
Safety model
Cloud forms reject secret material.
The public service accepts wallet hints and public descriptors. When a phrase, private key, or wallet file is needed, the app switches to a local vault and signs on this device.
- No seed upload.Recovery phrases never go to UCIR servers.
- Evidence first.Public checks and open risks are visible before local signing.
- Consent gates.Asset-moving actions stay disabled until destination and signing consent are explicit.
Private review
Send the case file, not the secret.
Generate the UCIR support brief from public clues first. If the case needs a person, request a private review with that brief and keep seed phrases, private keys, passwords, and wallet files out of email.
- Create the briefUse public clues to generate the secret-free support brief and audit JSON.
- Request reviewSend the brief without phrases, keys, passwords, wallet files, or signing material.
- Scope the caseSeparate supported local actions from risks that still need evidence or outside records.
- Act locallyUse the browser vault only when destination, fee, and consent checks are visible.
Start safely
Leave with a case file, not a guess.
Bring the wallet app, chain, year, public address, token contract, or approved xpub you already have. UCIR turns those clues into a secret-free packet you can copy, download, and review before any local action.