Info
Wallet, Explore, Mine, networks, and safety model.Bitpurz is a client-server Bitcoin platform with a standalone browser wallet at the front. The browser creates keys, derives addresses, signs transactions, and hashes mining work. The selected node supplies status, unspents, fee estimates, transaction reports, mining work, validation, and broadcast. No login is required, and the same split can support self-hosted enterprise node workflows.
Create, restore, watch, transact
The browser handles keys, addresses, QR, transaction review, and signing. The selected node supplies unspents, fees, and signed-hex broadcast when you ask.
Inspect and broadcast
Explore uses public data only: addresses, transaction ids, and signed raw hex. It asks the selected node for reports or broadcast and never uses wallet secrets.
Mine in your browser
Your browser does the proof-of-work by hashing block candidates. The selected node prepares current work, shows chain status, checks a winning result, and submits it to the network.
Client And Node
The browser does private work. The selected node does public network work.Browser
- Creates or restores wallet material.
- Derives receive and watch addresses locally.
- Builds QR codes, transaction review data, and signatures.
- Hashes mining work in a local worker.
- Keeps seed words, WIFs, private keys, xprv values, and signing material local.
Selected Node
- Reports network status, chain height, fees, and transaction data.
- Returns unspents for addresses you choose to check.
- Supplies mining work and validates solved work.
- Broadcasts explicitly submitted signed raw transaction hex or solved blocks.
Feature Flows
What to do and what to expect.Private Wallet
- Choose the network and address type.
- Enter 12 words, WIF, private key, or address.
- Generate or lookup the receive address.
- Refresh Unspents when you are ready to send the receive address to the selected node.
- Prepare with node unspents and fees, review, sign in the browser, then broadcast signed hex.
Public Watch-only
- Enter a branch public key in the browser.
- Derive receive addresses locally by index.
- Refresh Unspents for chosen derived addresses; those addresses are shared with the selected node.
- Export or monitor addresses.
- Watch-only wallets cannot spend.
Explore
- Paste an address, transaction id, or signed raw hex.
- Select the matching network.
- Ask the selected node to inspect unspents or transaction details.
- Broadcast only explicitly pasted signed raw transaction hex.
Mine
- Enter a payout address.
- Choose Mainnet, Testnet4, or Regtest.
- Regtest can fund and mine fake coins for testing.
- Public networks request block work from the selected node; your browser mines by hashing that work locally.
- If solved work is found, the browser sends work id, nonce, and header data for server validation before submission.
Safety Model
What leaves the browser and what does not.Never sent to Bitpurz
- Seed words and passphrases.
- WIFs, private keys, and xprv values.
- Signing material and unsigned private key data.
- Public branch keys during harmless status checks.
May be sent when you ask
- Network-only status and fee estimate requests.
- Addresses you choose for Refresh Unspents and watch-only balance checks.
- Transaction ids for transaction reports.
- Signed raw transaction hex for explicit broadcast through the selected node.
- Mining work result data when the browser finds solved work.
For real BTC, review destination, amount, change, and fee carefully. Disconnect before signing if you want maximum key isolation.
Visitor Privacy
Bitpurz uses first-party server request statistics to understand usage and protect the service. No analytics cookies, tracking pixels, or third-party tracking scripts are used.
The web-server statistics record page categories, response status, timing, size, and a daily visitor identifier derived from your connection IP using a protected secret. Raw IP addresses, full URLs, query strings, request bodies, wallet addresses, and raw browser headers are excluded from these statistics.
The identifier changes each UTC day. These are approximate, pseudonymous visitor counts, not anonymous-person counts: shared connections can combine visitors, changing connections can count someone twice, and the holder of the secret could test guessed IP addresses. Known owner/test traffic and estimated bots are excluded from visitor estimates.
Logs rotate daily or at 10 MiB, keeping at most seven archives per stream for seven days; the active file can extend coverage to about eight days. Automatic cleanup runs while the logging service is running. These logs and their secret are excluded from long-term recovery archives.
This describes web-server statistics, not the public-data processing needed for wallet lookups, transaction broadcast, or mining. Addresses you deliberately check may be retained by the node and lookup service. Wallet secrets remain in your browser.
Networks
Use the right network for the job.| Network | Use | Notes |
|---|---|---|
| Mainnet | Real BTC | Use small amounts first. Review destination, change, fee, and signed hex before broadcast. |
| Testnet4 | Newer public test chain | Useful for modern test flows before risking real BTC. |
| Regtest | Private fake coins | Best for local mining, wallet signing tests, and repeatable transaction flow checks. |
Quick Answers
Common questions.Can Bitpurz see my seed?
No. Seed words, WIFs, private keys, and signing material are handled in the browser and are not sent to Bitpurz endpoints.
Why can Refresh Unspents take time?
A newly watched address may need node import or scheduled rescan history. Future receipts should appear through the selected node once watched.
What happens if mining finds a block?
The server checks that the solved work matches the selected node tip and required target. If that node accepts submission, Bitpurz sends the reconstructed block to Bitcoin Core `submitblock`.
Is browser mining profitable?
Browser mining is useful for demonstration, regtest proof, and product engagement. Industrial mainnet mining requires specialized hardware.