docs

proof-of-work

This pool runs real Bitcoin proof-of-work — SHA-256d hashing against an actual block template, validated the same way any Bitcoin node validates a block. There's no simulation here: every accepted share is a genuine hash that met a target, and every block this pool finds is a real Bitcoin block.

Each connected device gets assigned a share difficulty — an easier target than the real network difficulty, so devices get frequent, meaningful feedback long before they'd realistically find an actual block. The pool tracks every accepted share and uses it to calculate that device's portion of any reward.

three independent tiers

Microcontroller, PC/GPU, and ASIC are fully separate pools — separate job feeds, separate share accounting, separate payouts. A block found by an ASIC has zero effect on the microcontroller tier's pot, and vice versa.

This matters because the hardware classes are wildly different in capability. Mixing them into one shared pool would mean microcontroller owners' odds get diluted into irrelevance by ASIC hashrate. Keeping them separate means each tier's economics make sense on their own terms.

payout waterfall

When any tier finds a block, the reward is split in a fixed order:

1. 2% operator fee — taken off the top of the full block reward.
2. Finder bonus — the device whose share found the block receives 5% of the block reward, capped at $20,000-equivalent, whichever is lower.
3. Remainder split — everything left over is divided among every device that contributed a share in that tier during that round, proportional to difficulty-weighted work submitted.

All payout math is done in integer satoshis — never floating point — to avoid rounding drift over many small payouts.

connecting a device

Every device connects using the Stratum mining protocol. Tier assignment happens automatically: the pool looks at a device's self-reported hardware fingerprint and its actual observed hashrate, and classifies it into the correct tier. A device that claims to be a microcontroller but performs like an ASIC gets flagged and reassigned.

See the get mining page for tier-specific connection details.

api keys

API keys link a device's mining activity to your account. Generate one from your account page, then use it as the worker password when connecting a device. Keys are stored hashed, shown in full only once at creation, and can be revoked individually at any time.