Solve a block, win 50% of the reward on the spot. Everyone else splits the rest by their luckiest hash. Paid straight into the block — no wallet, no withdrawals, nothing to trust.
Get close. Get paid.
Right now · live from the pool
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 is how the 49% is paid. Whoever solves the block takes 50%, the pool takes 1%, and the rest is split between everyone else in proportion to the luckiest hash they submitted for this block. Nothing carries over: when the tip moves, the board is wiped.
Why this pool · and how it differs
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.
Everyone on the pool mines the same Bitcoin Cash block at once — each miner just searches a different slice of it, so no one duplicates anyone else's work.
Picture 100 people searching one field for a hidden key: each covers a different patch, and whoever finds it first wins it for the team — then the reward is shared out by how hard everyone looked.
Same miners, same hashes, same winner — both panels are fed an identical stream. Each bar is the luckiest hash that miner has found for the block being mined; bars jump, they never accumulate. Watch what happens to everyone who didn't solve it.
Solver takes 50%, the pool takes 1%, and the other 49% goes to everyone else by how close they got.
Everyone mines their own block with their own address in it. Win and you take it all; otherwise your hashing produced nothing at all.
Illustration, sped up. Real blocks do not arrive every few seconds. The five miners and their hashrates are an example; the real pool's size changes every time someone connects or leaves. What is not simplified is the luck: every hash here is drawn from the true distribution, so how often the smallest miner places is honest. Only the clock is compressed.
Flat bonus to the block finder — the lottery. One share is a ticket; every ticket can win.
Split among all other miners in proportion to their luckiest hash for that block. Volume buys more chances, not a bigger claim — and every block starts from nothing.
Pool fee. That's it — and you can verify it 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. Coins mature ~16 hours after a block, as on every chain.
Get started · and check the record
stratum+tcp://POOL_HOST:3333YOUR_BCH_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 50% / 49% / 1% split.
| Protocol | Auto (vardiff) | Fixed 1M | Fixed 4M | Fixed 10M | Fixed 50M |
|---|---|---|---|---|---|
| Stratum V1 plain TCP |
3333 | 3301 | 3304 | 3310 | 3350 |
| Stratum V1 + TLS encrypted |
3433 | 3401 | — | 3410 | 3450 |
| Stratum V2 Noise encrypted |
3533 | 3501 | — | 3510 | 3550 |
Fixed ports by rig size — plain Stratum V1, for rented rigs and anything that needs a difficulty that never moves. Each is sized so a rig of that size submits roughly one share every 30 seconds.
| Rig size | Port | Fixed difficulty |
|---|---|---|
| 10 TH/s | 3305 | 76,000 |
| 50 TH/s | 3306 | 380,000 |
| 100 TH/s | 3307 | 760,000 |
| 200 TH/s | 3308 | 1,520,000 |
| ~500 TH/s | 3301 | 1,000,000 |
| ~1.5 PH/s | 3304 | 4,000,000 |
| ~4 PH/s | 3310 | 10,000,000 |
| ~20 PH/s | 3350 | 50,000,000 |
Pick the closest one at or below your rig's size. Landing on a port meant for something smaller is harmless — you just submit more shares than you need to. Landing on one meant for something much bigger means long gaps between shares and a hashrate reading that swings about.
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 50% / 49% / 1% split.
bch.0x.al3533 / 3501 / 3510 / 3550
auto / 1M / 10M / 50M06908d2fcf9900b86e7938e0a3e13a1c84b1e518958754deade1c4bee5c47cbfYOUR_ADDRESS.WORKER_NAMEWith the Stratum V2 reference implementation (SRI) — point the translator or job-declarator at:
bch.0x.al:3533and 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.
Renting hashrate? Rental platforms ask for a fixed difficulty in a set range and refuse to auto-tune. use the rig-size table above to pick one. They are all plain V1 — there are no TLS or V2 twins for the fixed ports.
Not sure? Use 3333 — 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.
qqgg0z7647vgusxkal77ukvy5fw9frh7rcxkgk2ed3.bitaxeUse an address you control the keys to (not an exchange). CashAddr (q…/p…)
and legacy Base58 (1…/3…) both work, with or without the bitcoincash: prefix.
Bitaxe: works out of the box. For the cleanest Block-Header display we recommend HexOS, an AxeOS fork with proper Bitcoin Cash coinbase decoding.
The pool has no wallet at all. Rewards go from the protocol to your address inside the block — nothing we could hold, freeze, or lose.
Every payout is written into the block's coinbase. Open any block we find in an explorer and check the split matches the rules — it always will.
Yes — and more often than your hashrate alone suggests. Placings are decided by the single luckiest hash you find for a block, and luck does not care how big your rig is. The odds of holding the best hash are exactly your share of the pool's hashes, so a Bitaxe beside a 100 TH/s machine takes first place about 1% of the time — and lands 2nd or 3rd far more often than that, which pays too.
The one thing to know: nothing carries between blocks. Every standing is wiped when the network tip moves, whether or not this pool won. There is no running balance to build up and nothing to lose by stopping — you are simply in, or not in, whatever block is being mined now.
Effectively no. Everyone on the board is paid, not just a top few — there is no "top miners only" cut-off, and the coinbase holds thousands of payout slots. If a share works out smaller than the 546-satoshi dust minimum it isn't emitted as an output — such an output would cost more to spend than it is worth — and that amount goes to whoever solved the block, as part of the rounding that makes the coinbase add up exactly. It happens to roughly 0.006% of payouts.
All of them — CashAddr (q…/p…) and legacy Base58 (1…/3…),
with or without the bitcoincash: prefix. The pool pays to your address's script, so any valid
form reaches your wallet. One tip: the pool tracks your account by the exact string you type (prefix aside),
so pick one spelling and use it on every worker. Mixing, say, a legacy and a CashAddr of the same
wallet shows up as two miners and splits your stats — though not your earnings: the pool merges the two
by payout script and keeps the better of the hashes, so you place exactly where you would have anyway. Lowercase CashAddr like qqgg0z… is the tidy default.
Lightning fixes a Bitcoin fee problem that Bitcoin Cash doesn't have — on BCH, fees are ~1 sat/byte, so even a tiny payout is spendable on-chain. So we pay you the most direct way there is: inside the block itself, with no channels and no pool wallet to trust.