Which miners actually work.

Hashrate and power are the manufacturers' figures. The share cadence is ours, and it is arithmetic rather than a promise: a share at difficulty D costs D × 2³² hashes, so the interval follows from the rate. The two faster units all end up at the same cadence, because the pool's own difficulty control moves each machine to the level that produces it. The port starts everyone at 16,384 so the first share arrives in seconds rather than minutes, and the control takes it from there — up for the faster units, down for the smaller ones, as far as the port's floor of 1,024. Nothing needs configuring.

Innosilicon S11 SiaMaster

4.3 TH/s at 1380 W, and the fastest of the four. On port 3333 it lands a share roughly every 16 seconds at the starting difficulty, then the pool's control moves it up. It was sold as a SIACOIN miner and still says so on the label; the algorithm underneath is BLAKE2b, which is what this chain uses.

iBeLink BM-S3 and BM-S3+

4.4 TH/s, a shade ahead of the S11. The BM-S3+ is the later revision and behaves identically here. Point it at the pool the way you pointed it at a Sia pool — URL, worker, password — and it starts submitting.

Bitmain Antminer A3

815 GH/s at 1275 W. A lot of these have been sitting idle since Siacoin moved away from BLAKE2b, which is exactly why this chain is worth their while again. A share every 86 seconds at the starting difficulty; the control settles it lower so the cadence stays useful.

Obelisk SC1 and SC1 Immersion

550 GH/s at 500 W — the most efficient of the four per watt, and the quietest case to run at home. The Immersion variant is the same silicon in a different shell.

What any of them earns per day depends on the network difficulty at the moment you ask, so it is not printed here. The calculator works it out from the live figure, and it shows the arithmetic.

FPGA and GPU

port 4444

Starting difficulty

128

CPU

port 5555

Starting difficulty

1

A graphics card around 2 GH/s lands a share roughly every four and a half minutes; one at 6 GH/s, about every ninety seconds; an FPGA around 20 GH/s, every twenty-seven. On the CPU port the difficulty is 1, which is the floor of the chain rather than a courtesy: one such share costs 2³² hashes and nothing smaller exists. Measured on this pool's own benchmark, one core does 6.66 million BLAKE2b hashes a second, so eight cores land a share about every 81 seconds and sixteen about every 40.

Work out your own: seconds per share = difficulty × 4.295 × 10⁹ ÷ your hash rate. The full protocol, including the exact hash construction, is published at stratum-protocol.md.

The BLAKE2b hardfork changed the proof of work at block 961,640. Before that height the chain is Bitcoin's, hash for hash; after it, a block is valid only if its BLAKE2b hash meets the target. A SHA-256 ASIC has that function etched into silicon — there is no instruction set to reprogram and no firmware that adds a second algorithm.

What you see when you try is unmistakable, and worth recognising because rental platforms will happily take the order: the miner connects, authorises against your address, and reports itself as hashing at full rate, while the pool records a hundred percent rejects and a best share thousands of times below the difficulty it was given. If your miner page shows that pattern, the machine is on the wrong algorithm. Nothing else produces it.

If you rent hashrate, rent it under Blake2B (sometimes listed as Sia or SC), never under SHA-256.

Can an Antminer S19 or S21 mine this chain?

No. Both are SHA-256 machines. They connect and submit, and the pool rejects every share. There is no setting or firmware that changes this.

Do I need to reflash my Sia ASIC?

No. Stock firmware is enough. Enter the pool URL, your payout address as the worker and anything as the password — the same three fields a Siacoin pool wanted.

Is a Goldshell or other Sia miner supported?

Any machine that computes BLAKE2b and speaks Stratum V1 works, whether or not it is listed above. The table names the models people ask about most; it is not a compatibility list. If in doubt, connect to the CPU port with any BLAKE2b miner first and see whether shares are accepted — that costs nothing and answers the question in a minute.

How much hashrate do I need?

On the shared pool, none in particular: you are paid in proportion to the shares you contribute, so a CPU earns a CPU's share of a block and an ASIC earns an ASIC's. Solo is the opposite — there a single machine against the network's petahashes is buying a lottery ticket, and the time-to-block calculator will tell you how long the average wait is.

Can I point a rented rig at this pool?

Yes, and it works — provided the rental is placed under the BLAKE2b algorithm. The platform passes the pool's difficulty straight through to the rig, so there is nothing to set on their side beyond the URL, your address as the username, and the algorithm.

Three fields and you are mining, with no account to create — your payout address is the account. The setup page has the exact values per hardware class, and measures the latency from your own browser to each region.