How to mine Bitcoin with a Sia ASIC

You need three things: an ASIC that hashes BLAKE2b, a fresh address on this chain to be paid to, and a DATUM gateway running beside a Bitcoin Knots node. If you already own a Siacoin miner you have the first one — this is the same algorithm, so stock firmware works. The gateway is how you mine here: point its datum section at datum.lazarus-xbt.xyz:28915 with the pool pubkey below, set your payout address, and point your miners at the gateway. Each ASIC hashes a plain BLAKE2b header with a Sia-style framing, not SHA-256d; new sessions start at difficulty 4096 and vardiff steps up toward your hashrate from there.

Running your own node and gateway costs 0%, because you are building the templates yourself. Tested gateways with full configs: Ratum and FlyTheElephant. For a longer Knots + DATUM walkthrough, use CONVOY’s get-started guide (also in 中文), then come back here for this pool’s host, port, and pubkey.

The public stratum, stratum+tcp://stratum.lazarus-xbt.xyz:23334 (username your address, optionally address.worker; password x), is the donation, validation and fallback endpoint at 100%, with a 24 h / 96 h grace at 25%, then 100%. Point a miner at it to confirm it connects and submits shares while your gateway is still coming online, or as a fallback if your gateway goes down. Bitcoin Knots has announced a rule to invalidate payouts to addresses that hash through any pool's stratum, so it is not a way to be paid. Both routes land in the same TIDES window under your address, so switching keeps the accepted work you already have.

One warning worth reading twice: this chain shares every block of history with SHA-256 Bitcoin up to block 961,640, so an address holding real BTC should never be used here. Generate a fresh address for this chain. Payouts arrive as outputs in the coinbase of blocks the pool finds, with no balance to withdraw. Coinbase outputs normally spend after 100 confirmations; under the temporary Knots #419 rule a newly mined coin waits 6,480 confirmations, and nodes will not relay any coinbase spend below that, so a payout takes about 45 days to become spendable. Which machines work · how the payout is calculated.

Get connected

One username: your address.

One way in: a DATUM gateway you run. Your username is the address that gets paid.

Which DATUM gateway

Pick one of these. All three speak BLAKE2b and connect here with no patch. Keep whichever you run up to date.

  1. Recommended CONVOY The reference BLAKE2b DATUM gateway, and the most actively maintained. Run the v0.5.0beta release; v0.4.1-beta builds are out of date. Every miner gets the whole split, so a found block pays the whole window.
  2. FlyTheElephant CONVOY’s code plus FlyTheElephant’s own work. Every miner gets the whole split, so a found block pays the whole window. Setup guide.
  3. Ratum iohzrd’s Rust gateway: one binary for Linux, macOS and Windows, with the same config file. Set 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.

Host
datum.lazarus-xbt.xyz
Port
28915
Pubkey
—
Fee
0% of your window share — no cut versus the public stratum

stratum + datum sections of datum_gateway_config.json


          
  1. Run Bitcoin Knots for this chain with server=1 and a cookie or RPC user the gateway can read.
  2. Build the gateway, merge the 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.
  3. Point miners at your gateway’s stratum (usually stratum+tcp://127.0.0.1:23334). Username: just a machine name, like rig1. Payouts go to mining.pool_address.
  4. Watch your gateway appear under Gateways and your address under Miners. Running an older FlyTheElephant / OCEAN-lineage v0.4.1-beta build (no +lazarus-split)? Update it: it can leave the window out of a block.
Who gets paid, by gateway setting
Gateway settingUsername the pool receivesPaid 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: true
pool_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