About the numbers on this page

This is the PPS-classic build of simplepool, paying out in Thunder (BIP300 drivechain sidechain #9). Every accepted share credits your worker a fixed number of sats — currently 1 000 sats × share difficulty — whether or not that share becomes a block. Accruals accumulate under your Thunder address in pps_credits.

When a share becomes a block, the coinbase pays the pool's own Bitcoin wallet (a normal P2WPKH output) for the miner-share of the reward, and the operator address for a small fee (1%). The pool operator then periodically batches accumulated BTC into Thunder via a canonical BIP300 deposit transaction — this is the step that actually moves value onto the sidechain. Once the pool's Thunder reserve is funded, the payout worker sends Thunder transactions to each miner's Thunder address on a cadence to drain their owed balance.

Why the two-step deposit? The LayerTwo-Labs enforcer only credits deposits that spend real, spendable UTXOs. Coinbases don't qualify; embedding the deposit directly in the coinbase results in a stranded output. Standard drivechain mining pools all route through a pool BTC wallet.

Connect a miner

stratum+tcp://pool.drivechain.info:3334
username:  <your-Thunder-address>[.<rig_label>]
password:  (ignored — any value)

The username must be a valid Thunder address — base58 of a 20-byte hash, e.g. 3Z6z1hPySNkFeB7HiKPCgqu4TZez. Generate one with thunder-cli get-new-address on any Thunder node. Using a Bitcoin address is rejected with "invalid thunder address" and no shares accrue. The optional .<rig_label> groups multiple rigs paying the same address as separate rows on the per-worker page.