Formats
Identification is not recovery.
The lab inspects supported backups, explains limits honestly, and only unlocks decrypt, export, or sweep paths when gates and authorization allow.
| Format | Chains | Identify | Password verify | Fund recovery |
|---|---|---|---|---|
| Web3 Secret Storage v3 | Ethereum · BNB · TRON | Yes | Bounded MAC / decrypt | Gated export & sweep |
| BIP39 English mnemonic | Six networks (path-dependent) | Checksum + binding | Passphrase as configured | Export · discover · sweep |
| Bitcoin Core SQLite / BDB | BTC · LTC · DOGE families | Read-only inspection | Passphrase when gated | Gated when decrypt succeeds |
| Electrum JSON / BIE1 | BTC-family | Yes | Supported paths | Export / discover; 2FA noted |
| Watch-xpub | UTXO networks | Yes | N/A | Discover addresses only |
| NUR encrypted-v1 synthetic | BTC · LTC · DOGE | Yes | Known-password verify | Lab / gated paths |
| Hardware / BIE2 | — | Inspection cues | No | Inspection only |
How intake treats a file
- Operator uploads a backup into an authorized case (maximum 16 MiB).
- The lab records format identity, integrity signals, and feasibility notes.
- Unsupported or hardware-bound material stays inspection-only with an explicit reason.
- Owner authorization (time-boxed) is required before verification or Option B export.
- Privileged decrypt / export / sweep steps still need recent MFA and open runtime gates.
Honest limits
Core wallet inspection is not decryption by itself. Watch-xpub material cannot yield private keys. Electrum 2FA two-of-three setups surface cosigner constraints instead of pretending a single-key export is complete. Hardware wallet families remain out of scope for fund recovery.
Tokens
Where networks allow, discover and sweep can target USDT / USDC (and limited contract lists). Amounts stay in exact atomic units — the UI does not invent decimal displays that the provider did not justify.