Verify Signing
Check that transaction signing stays local.The client-server split is deliberate: the selected node provides unspents, fee estimates, and broadcast, while the browser prepares, reviews, and signs the transaction. Broadcast sends only signed raw transaction hex after explicit user action.
Signing Flow
Prepare, review, sign, broadcast.Normal review
- Load a private wallet or address-only source.
- Refresh Unspents for the selected network; the selected node sees the spend address and returns spendable outputs.
- Enter destination, amount, fee rate, and optional test-network message.
- Prepare the unsigned transaction from node data and review inputs, outputs, fee, change, and message.
- Sign locally in the browser, then broadcast only the signed raw transaction hex.
Offline signing check
- Prepare the unsigned transaction while online using node data.
- Disconnect before signing for stronger key isolation.
- Sign in the saved or loaded wallet page.
- Reconnect only when you are ready to broadcast signed hex.
Transmission Boundary
What the server sees.Not sent
- Seed words and passphrases.
- WIFs, private keys, and xprv values.
- Signing material or private key data.
Sent only by action
- Addresses for Refresh Unspents.
- Fee and status requests without wallet secrets.
- Signed raw transaction hex for explicit broadcast.
Mainnet uses real BTC. Use a small amount first and review destination, change, and fee before broadcast.