Solo pool: a winning block's full subsidy is paid directly to the finder's address, freshly minted in the coinbase — bsv.cx takes only that round's transaction fees.
Live · last update 17s ago
Rolling 1-hour average hashrate, sampled every pusher cycle
| Address | Hashrate (5m) |
|---|---|
1JtLXNYy7Rmyp4NLeyEn2dugYh2CKo7GGJ | 4.93 PH/s |
1BTyryTK9Uqdq7fBtR73hvMWh5cEXX9MtS | 70.67 TH/s |
16FG6cEEZ7fz1qEyVa6411RiEbo3CqZ5gU | 17.39 TH/s |
16g8eMJV9pFWnyvh8BM6uvJL6AZ9V6oHE7 | 11.96 TH/s |
1JtLXNYy7Rmyp4NLeyEn2dugYh2CKo7GGJ.allo1JtLXNYy7Rmyp4NLeyEn2dugYh2CKo7GGJ.allo03b0e20e4c4d6273762e6378202d204e6f7468696e67207573657320757020616c636f686f6c20666173746572207468616e20706f6c69746963616c20617267756d656e742e20e28094204865696e6c65696e0c000119701a8a430000000000 2026-11-15T00:35:13Z by 1BTyryTK9Uqdq7fBtR73hvMWh5cEXX9MtS.s19a1BTyryTK9Uqdq7fBtR73hvMWh5cEXX9MtS.MRR2a1BTyryTK9Uqdq7fBtR73hvMWh5cEXX9MtS.s19a1BTyryTK9Uqdq7fBtR73hvMWh5cEXX9MtSThis is solo mining, not shared-payout pooled mining: if your miner finds a block, the full consensus subsidy is paid straight to your address, freshly minted into the coinbase transaction right then — bsv.cx never holds, custodies, or redistributes it. bsv.cx only keeps that round's transaction fees, in a separate coinbase output. Protocol is Stratum V1 over a bridge native to BSV SV Node's GetMiningCandidate (GMC) interface, with version-rolling (AsicBoost) and per-connection variable difficulty.
Solo mining is high-variance. Unlike a shared pool, you're only paid when
your own miner finds a block — depending on your hashrate and luck that could be
hours, or it could be weeks, with nothing in between. If you want smaller but steadier
payouts instead, a shared pool is a different trade-off than what this service offers —
GorillaPool
(stratum+tcp://bsv.gorillapool.io:3333, PPLNS, ~2% fee) is one established
BSV shared-pool option.
Status: open. Connect your Stratum V1-compatible miner to
stratum.bsv.cx:3333. Login is your BSV payout address plus an optional worker
name, e.g. 1YourAddressHere.worker1 — the password is ignored. Difficulty is
assigned automatically per connection and adjusts to your hashrate.
This is a single-node solo pool (no node failover yet) — a small, known risk for now; a second node for redundancy is planned.