Cabinet wallet
Keep WIF and hex keys in an encrypted vault on this device and watch the addresses they control. The vault is encrypted with a passphrase you choose; the server never receives the passphrase, a private key or a WIF.
The vault lives in this browser's IndexedDB. Losing the passphrase loses the keys: there is no recovery and the server cannot help. Export an encrypted backup and keep it somewhere safe. EVM keys can send native coin and ERC-20 tokens on Ethereum Sepolia and, after you arm mainnet for the session, on Ethereum, BNB Chain, Arbitrum, Optimism, Base, Polygon, Avalanche and zkSync. Bitcoin keys can send on Bitcoin testnet. The page builds and reviews the transaction, signs it locally in WASM and broadcasts the signed raw transaction directly to a public provider. This phase covers native-coin transfers, the ERC-20 transfer(address,uint256) method, and ERC-20 approvals read, grant (approve(spender, amount)) and revoke (approve(spender, 0)); granting is dangerous because it lets the spender move your tokens, so use the smallest allowance that works and revoke it when done. Other token methods and Bitcoin/TRON mainnet are not part of it. Per-transaction fee caps: 0.05 ETH on Ethereum mainnet and 0.01 native on every other mainnet chain.
Create a vault
Use at least 8 characters. The passphrase derives the AES key with PBKDF2-SHA256 (600,000 iterations); it is kept only in memory while the vault is unlocked.
Unlock the vault
A wrong passphrase cannot decrypt anything. The vault locks itself after 10 minutes without activity and whenever this page is hidden.
Restore an existing wallet
Choose what you already have. A seed phrase and a single private key are both first-class here: most wallets accept only a seed phrase, this vault accepts keys too. Either path derives locally in the WASM core and stores only the encrypted result in this browser. The key or phrase is never sent to the server, logged or put in the URL.
Create or unlock the vault first; the choice opens the matching form.
Vault
Top assets
The ten largest assets with a balance path on the networks this wallet supports, by market-cap rank from data/assets.json. A value is read only for a network where this vault holds an address, and only after you allow public balance lookups. Prices come from the same public Binance ticker as the key explorer, cached for up to six hours; USDT uses its explicit $1.00 peg. A row that did not load says “not loaded” or “lookup failed” and is never counted as zero; an asset with no balance read path says “unavailable”.
No vault key matches a top-10 network yet. Import a key above to see its balance here.
| Asset | Network | Balance | USD |
|---|---|---|---|
| Total | — | ||
Import a key
A WIF is checked and mapped by its version byte: Bitcoin mainnet compressed WIFs use native SegWit and uncompressed ones use legacy P2PKH, Bitcoin testnet WIFs (version 0xEF) use testnet native SegWit (tb1), Litecoin uses native SegWit and Dogecoin uses legacy. Dogecoin testnet (0xF1) is not supported. Any 64-character hex key needs an explicit chain; choose Bitcoin testnet to derive a tb1 address. The address is derived with the local WASM core first (testnet through derive_report_network); a key whose address cannot be derived is not stored.
Generate a seed phrase
12 words · 128-bit entropy · generate or paste a phrase
128 bits is 3.4×10^38 keys. At 10^12 guesses per second that is about 1.1×10^19 years — roughly 780 million times the age of the universe. A 24-word phrase is 256 bits (about 3.7×10^57 years).
The phrase is generated and shown in this tab only; it is never stored, sent or logged. The vault stores only the derived key for one chain, with the default BIP44 path of the selected chain. Zcash, Solana, Sui and TON have no BIP44 preset here: import a WIF or hex key for those chains instead.
Addresses
Lookups are off by default, and enabling them makes the Balance and History buttons send only the public address of that row to a public provider, never a key, WIF or passphrase. Bitcoin history is read from mempool.space; TRON history goes through this site's coordinator to TronScan; EVM history is unavailable without an indexer or API key, so no provider is called for it.
Portfolio summary
Only balances that actually loaded are counted; loading, failed or missing rows are not zero. Chains without a public price (for example Bitcoin testnet) are excluded from USD and named. The ticker is the same public Binance source as the key explorer, cached for up to six hours; a stale or offline ticker shows — while the native totals stay.
No balances loaded yet. Use Refresh to read the public addresses you allowed above.
No keys in this vault yet. Import a WIF or a hex key above.
Transaction history
No transactions found for this address.
| Time | Direction | Amount | Counterparty | Status |
|---|
Shows the latest 50 transactions. Bitcoin is read from mempool.space directly; TRON is read through this site's coordinator (TronScan). EVM chains need an indexer or an API key, which this build does not ship, so no provider is called for them. Amounts are in each chain's native unit; a token transfer that moves no native value shows 0. Bitcoin rows are an observer view of one address: a transaction that mixes inputs from several owners shows the full value sent to other outputs, which can be more than this address contributed.
Sign in to the monitor account
Signing in proves that you control the EVM address derived from a key in this vault. The local WASM core signs the coordinator's one-time challenge in this tab and only the EVM address, the challenge and its signature leave it: the key never does. The account identity is that EVM address. Bitcoin, TRON and Solana addresses in this vault stay wallet-derived addresses; this sign-in does not prove control of them. Keys stored only on ed25519 (Solana, Sui, TON) have no EVM derivation and are not listed here.
No EVM-capable key in this vault yet.
Security status
This panel checks only entries stored in this vault. The advisory list is public data; loading it sends no address. A local check derives addresses in this tab and never sends them anywhere. The Milk Sad scan covers compressed BIP44 derivations only; an uncompressed WIF entry is shown as not checkable. A no-match result covers only the seed range you enter and is not a guarantee that a key is safe.
No reviewed advisory applies to the entries in this vault.
Send an EVM transaction
The transaction is built from this form, reviewed field by field, signed in this tab by the local WASM core and then broadcast as a signed raw transaction. Public reads and the broadcast go directly from this browser to the chosen public RPC with the browser's real Origin; the server never sees a key and does not proxy these requests.
Review before signing
Unsigned EIP-1559 type-2 transaction — the exact bytes that will be signed:
Confirm signs these exact reviewed values in the local WASM core and sends only the signed raw transaction to the selected RPC. No key leaves this tab.
Broadcast result
Transaction hash:
Open the transaction in the chain explorer
Signed raw transaction:
ERC-20 approvals
See which addresses can spend an ERC-20 token you hold, grant a new allowance and revoke one. The scan reads Approval(address,address,uint256) logs and then reads the current allowance(owner,spender) for each spender, so the list shows the live value rather than the value in the log. It uses the network, public RPC and owner selected in “Send an EVM transaction” above, and a mainnet grant or revoke needs the same session arm. There is no indexer: the list covers only the scanned block window, so an approval older than that window needs a larger window on an archive RPC or an indexer. Granting a new allowance is dangerous: it lets another address move your tokens, so only approve a spender you trust, for the smallest amount that works, and revoke it here when you are done.
| Spender | Type | Current allowance | Action |
|---|
No Approval logs for this owner were found in the scanned window.
Review revoke before signing
Unsigned EIP-1559 type-2 transaction — the exact bytes that will be signed:
Confirm signs these exact reviewed values in the same local WASM core and sends only the signed raw transaction to the selected RPC. The transaction calls approve(spender, 0); the calldata is built locally and the signature covers the reviewed spender.
Broadcast result
Transaction hash:
Open the transaction in the chain explorer
Signed raw transaction:
Send a Bitcoin testnet transaction
Only Bitcoin testnet is enabled here; Bitcoin mainnet signing is not available on this page. UTXOs and the recommended fee are read from mempool.space/testnet/api and the signed raw transaction is posted back there, directly from this browser with its real Origin. The server never sees a key and does not proxy these requests.
Review before signing
Unsigned P2WPKH transaction — the exact bytes that will be signed:
Confirm signs these exact reviewed values in the same local WASM core and sends only the signed raw transaction to mempool.space testnet.
Encrypted backup
Restore a backup
Importing replaces this browser's vault. Only an encrypted Crypto wallet blob is accepted.
What is stored
IndexedDB database rotor-wallet, store vault: one versioned record with a random 16-byte salt, PBKDF2-SHA256 with 600,000 iterations, AES-GCM-256 and a fresh 12-byte IV on every save. The record holds only ciphertext; the passphrase and the keys are never written to localStorage, the URL, logs or the network.
This page can sign and broadcast EVM transfers on Sepolia and, after you arm mainnet for the session, native-token transfers on eight EVM mainnets, plus Bitcoin testnet transactions. The signatures and the raw transactions are created in this tab; only signed raw transactions are sent to public providers. Watch-only still means address display and opt-in balances without signing.
Related: cabinet dashboard, key explorer, documentation.