Settlement schedule and on-demand.
The fastest path from "I have a GPU or ASIC" to "shares are landing" on the testnet demo. Five steps.
01 How the software batches settlements
Rather than send a separate on-chain transaction every time a miner’s attributed balance ticks up, the stack batches settlements. On each cycle it gathers every miner whose attributed balance has reached the settlement threshold, then settles them together.
Batching matters because each settlement is an on-chain transaction with a network fee. Grouping many miners into one settlement run keeps the per-miner fee overhead low, so more of the attributed testnet coin units · no monetary value reach each destination address. The pool is non-custodial — a settlement is the software transferring units to a miner’s own wallet, never the pool holding them.
02 The regular cycle
The software runs settlements on a regular cycle — daily is a common default. When the cycle fires, the stack looks at every miner’s pending attributed balance, selects those at or above the threshold, builds the settlement transactions and broadcasts them. Miners below the threshold roll forward to the next cycle, as covered in the thresholds doc.
A daily cycle keeps settlements predictable and bounds how long a qualifying miner waits, while still batching enough together to keep fees sensible.
03 On-demand once over threshold
Alongside the regular cycle, a miner who is already over the threshold can request an on-demand settlement from the dashboard rather than wait for the next scheduled run. The software validates that their attributed balance still meets the threshold, then settles it on its own.
On-demand settlements skip the wait but not the threshold — a miner below it cannot force one, because a sub-threshold on-chain transaction would burn an outsized fee for the units moved.
04 Confirmations before a settlement is final
Broadcasting a settlement is not the end. A transaction is only final once the chain has buried it under enough confirmations — additional blocks mined on top of the one that included it. Until then the dashboard shows the settlement as pending.
You set how many confirmations are required. An example settlement log line looks like this:
The amounts in any such log are testnet coin units with no monetary value — they are not money, a price, or a balance worth anything in fiat.
05 Configuring the cadence
The cadence is yours to set. As the operator you control how often the regular cycle runs, whether on-demand settlements are enabled, and how many confirmations a settlement needs before it is marked final.
Tighten the cycle for faster settlements, loosen it to batch more per run, and raise the confirmation count where you want extra certainty before a settlement counts as done.