Your Sia ASIC already speaks BTC BLAKE2b.
This is a mining pool for the BLAKE2b fork of Bitcoin (BIP-110) — Bitcoin Knots changed proof-of-work at block 961,640 to the algorithm the Siacoin miners in your rack have hashed for years. We mine BLAKE2b here, not SHA-256. No new firmware, no new hardware, just a new place to send the work.
- Pool hashrate
- —
- Network hashrate
- —
- Block height
- —
- Miners
- —
- Workers
- —
- Blocks found
- —
Two pools, one node.
Shared mining pays every block across a rolling window of the pool's recent work, so a share keeps earning after the block that found it. Solo pays you the whole block or nothing at all. Both run off the same synced Knots node, and you can switch by changing a port.
Shared pool · TIDES
—measuring…
Hashrate, last 24 hours
Every block pays across the last few days of work — not only the shares since the previous one.
Solo
—measuring…
Hashrate, last 24 hours
Full block reward to the finder, minus the pool fee.
stratum+tcp://.b2pool.io:3333
de · hel · ord · lax · ua
GPUs on 4444, CPUs on 5555, solo on 3334 · same ports in Helsinki, Chicago, Los Angeles and Kyiv · your payout address is your username
How a share becomes a block.
Your miner never learns that it is mining Bitcoin. It receives a work header in the shape its firmware already expects, and the pool handles the translation in both directions.
- 01
Template
Our Knots node assembles a BLAKE2b block template from the mempool every few seconds.
- 02
Work header
The pool folds that template into the Sia-style work header your ASIC's firmware understands.
- 03
Share
Your unit rolls the nonce until a hash lands under the share target, then submits it.
- 04
Credit
Your share enters the TIDES window — the pool's last four network difficulties of work. Every block found while it is still in the window pays it.
Point a miner at it.
There is no signup. Your payout address is your account — set it as the worker name and the pool starts tracking you on the first accepted share.
- Stratum URL
- stratum+tcp://de.b2pool.io:3333Frankfurt. Same ports on hel.b2pool.io (Helsinki), ord.b2pool.io (Chicago), lax.b2pool.io (Los Angeles) and ua.b2pool.io (Kyiv). hkg.b2pool.io (Hong Kong).
- Which port
- 3333 ASIC · 4444 GPU · 5555 CPUThey differ only in the share difficulty you start on. Solo is 3334.
- Worker
- <your-payout-address>.<rig-name>e.g. bc1q…7k4f.shed-01
- Password
- xAny value — it is not checked. It is also the one place you can ask for a starting difficulty: put d=8192 there instead, and the pool starts you on that rather than on the port's default. It is rounded to the nearest power of two and never goes below the port's floor.
- Payout address
- A bech32 address from a wallet dedicated to this chainDo not reuse an address that holds coins on the other chain.
- Reward scheme
- TIDES, 1.0% feeEvery block pays out across a rolling window of the pool’s recent work, worth four times the network difficulty. A share earns from each block found while it is still in that window, so nothing resets to zero when a block turns up. Only the subsidy is shared.
- Stratum compatibility
- V1 · V2 · DATUMStratum V1, Stratum V2 with Job Declaration, and DATUM — all of them, in every region. Which port is which.
Questions worth asking first.
Do I need to reflash my miner?
No. BLAKE2b is the algorithm Siacoin ASICs were built for, so stock firmware connects and starts hashing. Point it at port 3333; GPUs and CPUs use 4444 and 5555, which run the same protocol and differ only in the difficulty you start on.
Why do some sites call this BTCB2?
Because a ticker has to be unique. Exchanges, rental markets and block explorers list this chain's coin as BTCB2 to keep it apart from the SHA-256 chain, which keeps BTC. It is the same chain either way: Bitcoin with BLAKE2b proof of work, the hardfork described in BIP-110. If you are renting hashrate, rent it under Blake2B — that is the algorithm, and it is sometimes still listed as Sia or SC.
Is this the same as SHA-256 Bitcoin?
No. This is the chain Bitcoin Knots follows after the BLAKE2b hardfork at block 961,640; the SHA-256 chain carried on and is unaffected. The two share every block of history before that height, which is exactly why you must use a fresh wallet and a fresh address here — an address holding SHA-256 BTC should stay well clear of this chain.
What is the difference between the two ports?
Port 3333 is the shared pool: every accepted share earns a slice of every block the pool finds, so your income tracks your hashrate closely. Port 3334 is solo: your shares only pay if one of them is the block. With a single ASIC, shared is almost always the right answer.
How does the shared pool decide what I get?
By TIDES: a rolling window of the pool’s most recent work, worth four times the network difficulty. Every block the pool finds is divided across the shares in that window, so one share earns a little from several blocks instead of everything from one — and no block resets your work to zero. At the pool’s present hashrate that window reaches back roughly sixteen hours — your statistics page shows the exact span. You start earning from your first share and keep earning for a while after you stop.
What is DATUM?
On the ordinary ports we choose the transactions that go into your block. With DATUM on 28915 you choose them, from your own node — we only send back a list of who gets paid. We never see your block, and we could not censor a transaction in it if we wanted to. It costs you a synced node and the gateway from github.com/ocminer/ratum, and it is the difference between renting your hashrate to a pool and being part of one. We would rather you mined that way, and we say so plainly. How to set it up.
I am in mainland China — which endpoint should I use?
hkg.b2pool.io in Hong Kong. It is not just the nearest one, it is on a CN2 direct line
into China Telecom's network, so the path avoids the congested ChinaNet backbone and holds up at
peak hours. Measured from the host, ten pings to each: around 60 ms to Beijing (57–67 ms)
against around 180 ms to Frankfurt, and less than that from southern China. Every share you submit pays that round trip, so it is worth
the move — but measure it from your own network first, with ping and
mtr against hkg.b2pool.io.
Which region should I mine to?
Whichever has the lowest ping to you: de.b2pool.io in Frankfurt, hel.b2pool.io in Helsinki, ord.b2pool.io in Chicago, lax.b2pool.io in Los Angeles, or ua.b2pool.io in Kyiv. hkg.b2pool.io in Hong Kong is the one to use from mainland China: it sits on a CN2 direct route, around 60 ms to Beijing against around 180 ms to Frankfurt. That host runs the stratum endpoint you connect to, and a shorter round trip means less time between finding a share and having it counted. They carry the same ports and feed one pool, so your shares and balance follow you across them and a failover costs nothing.
When do I get paid?
Coinbase rewards need 100 confirmations before they can be spent, so payouts follow block maturity rather than a fixed clock. Depending on how the block was found you are paid straight from its coinbase or by transaction from the pool once your balance passes 10,000 sat. Balances are visible on your miner page from the first share.
Is the pool running yet?
Yes — B2Pool is mining the BLAKE2b chain, and it has found blocks. Every region is open for shared and solo mining, over both Stratum V1 and V2, and every figure on this site comes from the pool's own node and its own share records rather than from an estimate. Point your miner at whichever region answers fastest.