A zero-custody solo BCH2 pool. Whoever solves the block takes 98% of the 50 BCH2 reward, less a 2% fee. Winner takes it all. Paid straight into the block's coinbase: no wallet, no withdrawals, nothing to trust.
Standings for the block being mined right now, ranked purely by the single luckiest hash each miner has submitted since the last block. It resets the moment the tip moves — nothing carries over.
| # | Miner | Luckiest hash | Shares | Would receive |
|---|---|---|---|---|
| No shares yet for this block. | ||||
This board pays nobody. It shows who has come closest to solving the block being mined right now — interesting to watch, but only the miner who actually solves it is paid. Nothing carries over: when the tip moves, the board is wiped.
Every accepted share the pool has taken, newest at the bottom. reached is the difficulty the hash actually hit; set is what that miner was asked for. A block is simply a share that reaches the whole network's difficulty.
| Height | When | Found by | Finder got | Block |
|---|---|---|---|---|
| loading… | ||||
Every row is verifiable on-chain. Open the block and read its coinbase: the finder's 98%, and our 2% fee — all in one transaction.
To whoever solves the block — 49 BCH2, straight to their address. Solo mining: you are paid for the block you find, and only for that block.
Pool fee. That's it — verifiable in every block's coinbase, on-chain, forever.
Paid directly into each block's coinbase, straight to your address — no pool wallet, no balance, no minimum, nothing to withdraw.
BCH2's network is a tiny fraction of Bitcoin Cash's, so blocks are genuinely findable by ordinary hardware. A Bitaxe or a single ASIC has meaningful odds here — and whoever solves the block takes 49 of its 50 BCH2, alone. Every other miner that round is paid nothing.
Same trustless payout engine as our BCH pool, but not the same split: BCH pays the finder half and shares the rest among everyone else, while here the finder takes all of it bar the 2% fee. Either way the payout is written into the coinbase by the block itself, so there's no operator balance to trust and nothing to withdraw.
stratum+tcp://bch2.0x.al:7333YOUR_BCH2_ADDRESS.WORKER_NAMEanything (not checked)Same pool on every port — pick the row for your protocol and the column for your difficulty. Every port pays the same 98% / 2% split.
| Protocol | Auto (vardiff) | Fixed 1M | Fixed 10M | Fixed 50M |
|---|---|---|---|---|
| Stratum V1 plain TCP |
7333 | 7301 | 7310 | 7350 |
| Stratum V1 + TLS encrypted |
7433 | 7401 | 7410 | 7450 |
| Stratum V2 Noise encrypted |
7533 | 7501 | 7510 | 7550 |
Stratum V2 encrypts the connection with a Noise handshake, so your miner needs one extra thing besides the port: the pool's authority public key. That key is what lets your miner confirm it is talking to this pool and not to somebody sitting in the middle. Nothing else about mining changes — same address as your username, same 98% / 2% split.
bch2.0x.al7533 / 7501 / 7510 / 7550
auto / 1M / 10M / 50M4a2b93c507dd1ef7925078fbd64f03e03bfe4a1f0419eb04c9bdc12631a93353YOUR_ADDRESS.WORKER_NAMEWith the Stratum V2 reference implementation (SRI) — point the translator or job-declarator at:
bch2.0x.al:7533and set the pool authority key to the value above. In
SRI's toml config that is the authority_public_key field of the
upstream you are adding.
Firmware support is thin, and that is not our doing. Stratum V2 tooling is built around Bitcoin, so very little Bitcoin Cash mining firmware speaks it yet. These ports are here, tested and working, for anyone whose setup does — but if yours does not, use the V1 or V1+TLS ports instead and lose nothing. The payout is identical on every port.
If your V2 miner cannot connect, tell us on Discord — the handshake is verified working end to end, so a failure is worth us seeing.
Not sure? Use 7333 — it fits everything from a Bitaxe to a
farm. The Auto ports self-tune to your hashrate from rolling dual-EMA estimates, which is what you want
for small and medium miners. The Fixed ports never move, which is what rented rigs need.
On any Auto port, put d=524288 or
diff=524k in the password field and the pool locks to that instead of auto-tuning.
k / m / g suffixes work; the value is
clamped between 1,024 and 1,000,000.
Rented rigs demand an optimal difficulty range and warn if the pool sits below it. The Fixed ports never drop below their stated value, so that warning cannot trigger. Roughly: 1M suits ~100 TH/s–1.5 PH/s, 10M suits petahash rentals, and 50M is for 20 PH/s and up.
bitcoincashii:qq….bitaxeUse a BCH2 address (bitcoincashii: …) that you control the keys to — not a
BCH address and not an exchange deposit address.