Verify Address
Check that wallet generation stays in your browser.The Wallet page can generate, restore, or watch Bitcoin addresses in the browser. Verify both sides of the flow: the browser-derived network, address type, receive address, QR, and path, and the deliberate moment an address is sent to the selected node for Refresh Unspents.
Simple Verification Flow
Use this before trusting a wallet ceremony.Online setup check
- Open Wallet at the site root.
- Choose the intended network and address type.
- Generate or restore a wallet.
- Confirm the receive address, QR, and derivation path are shown locally.
- Use Refresh Unspents only after you are ready to share the address with the selected node.
Offline ceremony check
- Save the Wallet HTML from the browser.
- Disconnect the network or use airplane mode.
- Open the saved HTML file.
- Generate or restore the wallet while offline.
- Record the address, path, and public branch key if needed.
Client And Node Check
Prove the local part before asking the node.Browser check
- Derive the address, QR, path, and public branch key locally.
- Repeat the same seed and settings offline if you need ceremony proof.
- Keep seed words, passphrases, WIFs, private keys, and signing material local.
Node check
- Refresh Unspents only after the displayed address is correct.
- The selected node sees the address you ask it to check.
- The selected node does not need your seed, WIF, private key, or signature material.
Address Privacy Boundary
What is safe to share.Keep private
- Seed words and passphrases.
- WIFs and private keys.
- xprv values and signing material.
May be shared deliberately
- Receive addresses for payments and Refresh Unspents.
- Branch public keys for watch-only address generation.
- Public transaction ids for Explore reports.
A branch public key cannot spend, but it can reveal derived addresses. Treat it as accounting-sensitive data.