FAQ · XBT / BTCB2Questions, answered plainly

It is Bitcoin's ledger continued under a different proof of work. Every block up to 961,640 is shared with SHA-256 Bitcoin; from that height this chain hashes with BLAKE2b. Balances from before the fork exist on both chains at the same addresses.

To reset the hardware race and put block building back with miners. SHA-256 mining concentrated in a few industrial operations, and a handful of pools chose the transactions for most of the network. On BLAKE2b the hardware is new to everyone, and most hashrate here runs DATUM, where each miner's own node builds the block.

Bitcoin's: 21 million coins, halving on the same schedule. The subsidy at current heights is 3.125 XBT a block, with ten-minute target spacing and a retarget every 2016 blocks.

No. SHA-256 hardware cannot hash BLAKE2b. You need a BLAKE2b miner: purpose-built hardware, a GPU, or a CPU for testing.

History is shared up to the fork, so the key that controls an address on Bitcoin controls the matching address here. Receiving XBT to an address that holds real BTC ties your activity on the two chains together and invites mistakes with wallets that cannot tell them apart. Make a wallet used only for XBT.

Yes, at the same address, controlled by the same key. Moving those coins means exposing that key to this chain's software, which is a decision to make carefully and never with a hot wallet you also use for bitcoin.

A pool paying in the coinbase does not: each block it finds pays miners directly inside that block, so there is no balance, no withdrawal button and nothing owed if the pool disappears. Pools that pay from their own wallet do hold your coins until they send them — the galaxy map shows which do which.

That is each pool's own business. On Lazarus, your own DATUM gateway is 0%. The public stratum is a donation, validation and fallback endpoint at 100%, with a grace at 25% for 24 hours (96 hours if the address had DATUM work on Lazarus in the prior 30 days), then 100%. Current figures are on the Lazarus Pool fee table.

A payout scheme built on a rolling window of accepted work. When a block is found, everyone with work in the window is paid from that block's coinbase in proportion to their share of it, so your hashrate is not your cut: a new rig starts near zero and rises as its work enters the window. The pool site shows the window live.

Coinbase outputs always mature before they can be spent. Under the long coinbase maturity soft forks a coin mined from block 973,440 to 979,918 waits 6,480 blocks (about 45 days) and one mined from block 979,919 on waits 25,920 blocks (about 180 days, Knots 29.4.3), each counted from its own block. Your pool page counts it down per block.

The public stratum stays up as a donation, validation and fallback endpoint at 100%, with a grace at 25% then 100%. To be paid, move to your own node and DATUM gateway. Accepted work is keyed to your address, so your place in the payout window carries over. The pool site has the DATUM setup steps; the node sync is the only slow part.

Any build that speaks this chain: the C datum_gateway forks (iohzrd, CONVOY, FlyTheElephant, StartOS) or ratum-gateway, iohzrd’s Rust rewrite, which reads the same config file and ships as one binary for Linux, macOS and Windows. Lazarus tests each release of Ratum against its Prime before recommending it; the Ratum guide has the install, a full config and the results.

If you have a Bitkey hardware device, Lazarus Key signs XBT with it and protects your sends against replay on the other chain. Otherwise an Electrum wallet pointed at a server for this chain (electrum.lazarus-xbt.xyz:50002:s), or your own Knots node. Either way, a wallet created fresh for XBT.

Third-party markets exist; none are run by or affiliated with Lazarus, and none are endorsed here. Check the ticker before sending anything, and do not leave coins on an exchange.

The Discord, where the miners and operators are. Announcements are on X, and pool questions belong on the pool site.