Wallet inside the encrypted vault
Restore from a seed phrase or import a private key. The wallet shares the same trust boundary as your passwords, notes, and files — the browser never becomes a second secret store.
Practical workflows
Every key operation stays on your device — the browser is just the interface.
Restore from seed phrase
Enter your seed phrase — ChromVoid creates BTC and ETH accounts inside the same encrypted vault where your passwords and notes live.
Import a private key
Add an external private key as a standalone wallet when you need access to an existing address without tying it to a seed phrase.
Preview before sending
You see the fee, warnings, and final transaction before signing. Nothing is sent until you confirm — no blind sign-and-broadcast.
Transaction lifecycle
No transaction leaves the device without explicit confirmation. Core assembles, you verify.
Create or restore in Core
Mnemonic generation, seed-phrase restore, and private key import run in Rust Core, not in the browser.
Accounts follow network rules
Bitcoin uses receive and change chains. Ethereum derives MetaMask-compatible account paths from the same seed phrase and creates accounts by network-specific rules.
Live balance comes from Core
Balances are fetched live for the selected account. The browser does not become a second persistent cache for wallet state.
Send via prepare -> confirm
Core builds the transaction, returns the preview and warnings, then signs and broadcasts only after confirm. Status reconciliation uses the tx journal instead of blind retries.
Security boundaries
Hidden system shard
Wallet data lives in `.wallet` as a hidden system shard. The password catalog, file access, WebDAV, and FUSE do not expose or edit it.
Key material stays in Rust Core memory
Seed material, private keys, and signing payloads are derived on demand, used in Core, and zeroed from memory after the operation — never stored in browser state.
Core owns transaction assembly
Core builds the canonical transaction, computes the local tx hash, and reconciles ambiguous outcomes through the tx journal — no blind rebroadcast.
Limits and prerequisites
This page describes the v1 architecture. It is an honest boundary of what exists today, not a promise of a full-featured wallet.
- Only `bitcoin` and `ethereum` are supported.
- No `solana`, hardware wallets, raw/offline signing, swaps, DEX, or smart-contract dashboard.
- An imported private key creates a standalone wallet — it does not attach to a seed-phrase wallet.
- HD export applies to seed-phrase wallets only. Recovering an imported key depends on the vault backup.
What this is not
Not a browser hot wallet, not a multi-chain trading app, not a generic key dump. A local wallet with narrow trust boundaries.
Want a BTC/ETH wallet without a second secret silo?
Start with the local vault — the wallet lives inside the same trust boundary that Core controls.