Proof of work, in one minute
Miners race to find a hash below a target. It is pure trial and error, so more hashes win more often, and that cost is what makes the chain hard to rewrite.
How the pool fits inBitcoin (XBT / BTCB2) · BLAKE2b · DATUM · TIDES · Proverbs 11:1
Bitcoin now runs on BLAKE2b, so any Siacoin ASIC can mine it. Point yours here and every payout lands straight in the block’s coinbase.
Run your own node and DATUM gateway: you build the block and pay 0%.
Set up a DATUM gateway. Pick one from our tested list.
Custody fee: from block 977,665, make-goods for pool-only or partial coinbases pay 10% less to miners whose own out-of-date gateway produced them. Miners on current gateways are paid in full.
Live
Straight from Prime and the node, refreshed every ten seconds.
Hashrate by path
DATUM by gateway
Live credited hashrate, same as the pool figure above — not TIDES window share.
Of DATUM hashrate only — same live credit as the chart to the left. Largest gateways listed; the rest are in Other.
Prime is not answering right now. Window, gateway and payout figures are the last ones it published.
Next payout
The coinbase Prime is handing out right now. Whoever finds the next block, this is who it pays and how much.
—
—
—
—
—
—
Window % is each address’s share of accepted work; XBT is its output after fees. Amounts use the base subsidy; transaction fees scale every output up.
Get connected
One way in: a DATUM gateway you run. Your username is the address that gets paid.
Pick one of these. All three speak BLAKE2b and connect here with no patch. Keep whichever you run up to date.
mining.pool_address to your own address. Setup guide.
Want a full walkthrough? CONVOY’s get-started guide (中文) covers Knots and the gateway. Then use the host, port and pubkey below.
You build the block. We only split the coinbase. Run Bitcoin Knots and a DATUM gateway, point the gateway at Prime, and point your miners at the gateway. Which gateway to run.
stratum + datum sections of datum_gateway_config.jsonserver=1 and a cookie or RPC user the gateway can read.stratum and datum sections above into its config, and set mining.pool_address to your payout address. Keep stratum.vardiff_min at 4096: stock DATUM defaults to 16384, and Prime cannot lower it.stratum+tcp://127.0.0.1:23334). Username: just a machine name, like rig1. Payouts go to mining.pool_address.v0.4.1-beta build (no +lazarus-split)? Update it: it can leave the window out of a block.| Gateway setting | Username the pool receives | Paid to |
|---|---|---|
pool_pass_full_users: true |
the miner’s own stratum username, unchanged | each miner’s address, so miners behind one gateway are paid separately |
pool_pass_workers: truepool_pass_full_users: false(the config above) |
the gateway’s mining.pool_address, then . and the miner username |
the gateway address; the worker name still reaches the pool |
both false |
the gateway’s mining.pool_address alone |
the gateway address; no worker name reaches the pool |
Our public endpoint on :23334 is itself a DATUM gateway on Prime (see Gateways), so its work lands in the same window under your address. Sessions start at difficulty 4096; vardiff doubles about every 20 s toward your hashrate.
Solo is a bet, not a wage. Your shares buy you nothing — they only prove you are working. When one of them is a block, that block’s entire reward goes to the address in your username, less our fee, paid in that block’s own coinbase. Until then you earn nothing, however long you mine. Pooled mining pays you a steady share of every block the pool finds; solo pays you rarely and enormously. Most miners should stay pooled.
Solo work is kept out of the TIDES window on purpose. Point some miners at solo and others at the pooled ports if you want both; the pooled ones keep earning their window share while the solo ones chase a whole block. Your solo shares will never appear under Miners or in Next payout — look under Solo instead.
Already running your own node? Then solo mine against it directly — you do not need us for that, and you should not pay us for it. These ports are for miners who want to solo without running a node.
Buy a miner
Any Siacoin ASIC mines Bitcoin (XBT): it is the same BLAKE2b hardware. Machines and prices come from BT-Miners’ BTCB2 collection. Earnings assume your own DATUM gateway at 0% fee, before electricity.
Could not load the catalog. Open BT-Miners’ BTCB2 collection directly.
Lazarus Pool is not responsible for BT-Miners customer support or quality of service.
Rent hashrate
Rent BLAKE2b rigs on RouteHash and point them at your own DATUM gateway’s public stratum port. Pay in BTC or XBT. Each card compares the rental cost with what that hashrate would earn here. Or buy a machine.
36 TH/s · live 37.764 TH/s · 3–24 h
Rent on RouteHash
26 TH/s · live 23.847 TH/s · 3–24 h
Rent on RouteHash
25 TH/s · live 27.365 TH/s · 3–6 h
Rent on RouteHash
24 TH/s · live 28.694 TH/s · 3–24 h
Rent on RouteHash
0.55 TH/s · live 0.547 TH/s · 3–72 h
Rent on RouteHash
0.543 TH/s · live 0.559 TH/s · 3–24 h
Rent on RouteHash
No BLAKE2b rigs listed right now.
List your BLAKE2b miner on RouteHash to earn between your own mining.
Lazarus Pool is not responsible for RouteHash customer support or quality of service. Rentals are paid to RouteHash in BTC or XBT; XBT amounts use the NeoxEX best bid. Estimates exclude luck, transaction fees and electricity.
Your stats
Hashrate, window share, next payout and every coinbase that has paid you.
Prefer to ask? Connect any AI assistant to our MCP server. Read-only, no login.
Miners
Hashing now, then everyone else we have seen. Window % is next-block pay, not hashrate: an idle address is still paid while its work is in the window.
Online now
Relayed to other pools
Recently seen · not hashing right now
Gateways
Every DATUM gateway connected right now, ours included, plus any that have found a block even if they are offline. Block counts are lifetime.
Solo
Separate from the pool’s window — none of this work is paid a share of anything.
Hashing now
Blocks found solo
Blocks & payouts
Every payout is an output of the found block’s coinbase: open a block to see them all. Outputs are spendable after 6,481 confirmations (100 for blocks before 973,440). Also on the Lazarus Mempool.
Found by Lazarus
Recent on this chain
Learn
Six short answers. Mining here needs only a payout address: no account, no sign-up.
Miners race to find a hash below a target. It is pure trial and error, so more hashes win more often, and that cost is what makes the chain hard to rewrite.
How the pool fits inAt block 961,640 (30 August 2026) this chain switched from SHA-256d to BLAKE2b. Supply, halvings, addresses and history are unchanged, and Siacoin ASICs now mine it.
The fork, and BIP-110On an ordinary pool, the pool picks what goes in the block. With your own DATUM gateway and Knots node, you build the template and the pool only splits the reward. Here that costs 0%.
Set up a DATUM gatewayTIDES pays on a rolling window of about eight network-difficulties of work. When the pool finds a block, every address with work in the window is paid its share. No rounds, no resets.
TIDES explainedEach payout is an output of the block’s own coinbase, sent straight to your address. No balance, no threshold, no withdrawal, and every payout is on chain.
Non-custodial payoutsThe public stratum is capped at 15% of network hashrate; past that, new connections are relayed to other pools. Your own DATUM gateway never counts toward the cap.
The 15% self-capserver=1 and a cookie or RPC user your gateway can read. Your node is what chooses the transactions in your blocks.mining.pool_address to your address.address.worker.How it works
For newcomers and operators alike. Your ASIC never sees any of this — it hashes a plain BLAKE2b header.
Point your machines at your own DATUM gateway. Prime rebuilds and checks every share, and credits accepted work to your address in the TIDES window.
The window holds the last 8 × network difficulty of accepted work — days of pool work at typical hashrate, not the last hour. A found block pays each address in proportion to its share of that window, less its fee. A new rig starts near 0% and ramps as its work enters and older work ages out.
Prime hands every gateway the same coinbase output list — the one shown under Next payout. A share whose coinbase pays anything else is refused, so whoever finds the block, it pays the window. There is no pool balance to withdraw and no operator to trust with your coins.
Decentralize the hashrate
No single pool should hold a third of this chain. We cap our own stratum at 15% of the network (own-gateway hashrate doesn’t count); past that, new stratum connections are relayed to one of these pools. All five support DATUM and TIDES. Keep one as a failover.
0% DATUM · 1% stratum, variable
Maveth’s TIDES pool. Zero fee through your own gateway; the SV1 skim is variable (currently 1%) and half of it goes back to live DATUM miners as STRATUM BOOST. Prefers a CONVOY gateway with the largest-coinbase patch.
1% DATUM · 2% failover
The pool behind the CONVOY DATUM gateway. Non-custodial TIDES; DATUM is their standard 1% fee, and mining on their failover stratum (they build the template) is 2%.
0% DATUM · 1% TIDES
DATUM on 28915 is 0%. Shared TIDES on 3333 is 1% over a window of four times difficulty; solo on 3334. Regions in Frankfurt, Helsinki, Chicago, Los Angeles, Kyiv and Hong Kong.
1% DATUM · 2% pooled stratum
Bitcoin Xor’s TIDES pool. Coinbase-direct payouts, DATUM-first: you build the template at 1%, or mine on their pooled stratum (they build the template) at 2%. xorpool.com.
0% DATUM · 10% their public gateway
Omega Pool, run by iohzrd, the author of Ratum. Own gateway is 0%; their public gateway is 10%. Miners connect through ratum-gateway or CONVOY and are paid from a TIDES window of eight times difficulty.
Relayed miners are paid by the pool they land on: see Relayed to other pools. Own-gateway miners are never relayed. Fees as each pool published them on 18 September 2026; check before you point hashrate.