WalletRead the docsLaunch app
New: verify in your browser

Recompute any closed batch from its ciphertexts and the drand beacon

The browser wallet

A full Monero wallet in a browser tab, built on monero-ts, which is Monero's own wallet2 code compiled to WebAssembly.

What runs where

The wallet code loads into a web worker in your tab. Key generation, scanning outputs and building transactions all happen there. The page talks to the worker; nothing about your keys goes to our server.

This tabpage: balance, send, subaddressesweb worker: wallet2 in WASMholds the keys while openIndexedDB: keys + cache filesencrypted with your passphraseMonero node (HTTPS)sees block and tx requestsRPC, no keys
What lives where

Nodes

The wallet syncs from a public remote node over HTTPS. You can pick one of the listed nodes (Cake Wallet, Seth for Privacy, cryptostorm) or enter your own. A custom node must allow cross-origin requests from this site. The node learns which blocks your wallet asks for and sees the transactions you broadcast, as with any light wallet setup. For the strongest privacy, run your own node.

Storage and passphrase

After every sync the wallet's keys file and cache file are saved in this browser's IndexedDB. wallet2 encrypts both with a key derived from your passphrase. To unlock, you type the passphrase again; a wrong one fails to decrypt. Clearing site data or removing the wallet deletes the files from this browser.

Subaddresses and sending

You can create as many subaddresses as you like, one per counterparty. To send, enter an address and an amount, review the network fee, then broadcast. The transaction is built and signed in the worker; only the signed transaction leaves the tab.

Back up your seed

A new wallet shows its 25-word seed once. Write it down offline. To restore, enter the seed and a restore height (the block to scan from); 0 rescans the whole chain, which takes a long time in a browser.