On a machine, not just a tab
The browser is the easy ticket. Close the tab, it dies. On a computer you leave the miner running and talk to the same pool — nickname, wallet, aligned ranges.
CPU on Node
Download the miner, set a nick. It talks to this pool — https://6btc.blog — not some other site. CPU threads, 65,536 keys per lease, retries if the API blips. A real GPU lands when someone plugs a solver into the HTTP below. If the key hits, it writes FOUND.txt and stops.
node miner.mjs --origin https://6btc.blog --nick your_nick --wallet bc1... --threads 4
The pool over HTTP
If you have BitCrack, VanitySearch, or another Puzzle 71 solver, point the worker here. No account. The token comes back from join and is valid for claim/finish.
- POST /api/pool/join — nick, optional wallet, token if you already have one
- POST /api/pool/claim — token → startHex + count
- POST /api/pool/finish — token, leaseId, keys
- GET /api/pool/stats — this house's board
Range 0x4000…–0x7fff… · 65,536 keys per aligned lease on the machine (4,096 in the browser). If the key lands, the miner writes FOUND.txt. It does not go to the mempool on its own.
