all learn

Stratum: how your miner talks to a pool

Stratum is the work-delivery protocol between your miner and the pool: the pool sends candidate blocks, your miner sends back proofs of work (shares). Getting the endpoint, port, and worker name right is day-one configuration.

2026-10-19·updated 2026-10-19·3 min·pow.family research#mechanics#pools
01

The conversation

A lone miner cannot cover every nonce for a whole block, so pools farm the work out. Over Stratum, the pool sends your miner a job: a block candidate (minus the winning nonce). Your miner grinds nonces on it and reports solutions that clear a much lower bar — the share difficulty — back to the pool. The pool counts those shares to measure your contribution (see how pools work).

One connection carries it all: job updates when the block template changes (new transactions, a new previous block), share submissions, and occasional difficulty adjustments. When a submitted share also clears the network target, it is a full block and the pool claims the reward for everyone accounting.

02

Anatomy of a pool URL

PieceExampleWhat it is
Protocolstratum+tcp://Transport — V1 plaintext TCP is still common; stratum+tls or V2 encrypted exists
Hostpool.example.comThe pool's endpoint — must match the COIN, not just the brand
Port:3333Selects algorithm/protocol variant — wrong port = zero shares
Userwallet.worker1Payout address or account, plus a worker label you choose
PasswordxLegacy field — literally 'x' on most pools; never a real password
03

First-day checklist

  • Endpoint matches the coin's algorithm (a RandomX port will not pay you for scrypt work).
  • Worker name format matches the pool's docs — it becomes your dashboard identity.
  • Shares appear as *accepted* within minutes; *rejected/stale* over ~2% means latency trouble.
  • Keep the payout address and any API keys separate from worker credentials.

Failover: serious setups list 2–3 pool URLs so the miner switches automatically when one hiccups — cheap insurance against a flat earnings day.

04

See it live on pow.family

Every project page lists its live pools with fees and payout schemes — the quick-start blocks paste the exact Stratum endpoints miners used on our test fleet.

Sources

Related
More explainers
updated 2026-10-19ASIC vs GPU vs CPU: three ways to hashupdated 2026-10-19Bitcoin block rewards: subsidy, fees, and the coinbase transactionupdated 2026-10-16Emission schedules: why coins halve, decay, or never stopupdated 2026-10-16Merged mining (AuxPoW): one electric bill, two coinsupdated 2026-10-19The mining budget checklist: the true cost of a rigupdated 2026-10-19Electricity costs: the kWh math that dominates miningupdated 2026-10-19The mining glossary: every dashboard word, definedupdated 2026-10-16Pool mining vs solo mining: the variance tradeupdated 2026-10-16What is mining? The hash lottery and the block rewardupdated 2026-10-19Algorithm compatibility: hardware must match the puzzleupdated 2026-10-19Bitcoin difficulty: the 2,016-block thermostatupdated 2026-10-19Home installation: prep and the safety checklistupdated 2026-10-16How pools work: shares, the payroll ledgerupdated 2026-10-16Mining algorithms: SHA-256, Scrypt, RandomX — and why hardware differsupdated 2026-10-19Reading electricity tariffs: energy, demand, and fixed feesupdated 2026-10-16Tail emission and dilution: caps vs forever-moneyupdated 2026-10-19Airflow and temperature: the intake-exhaust loopupdated 2026-10-16Auditing supply claims: three formulasupdated 2026-10-19Halving planning: model subsidy cuts without the folkloreupdated 2026-10-16Mining difficulty: the network's thermostatupdated 2026-10-16Effort and luck: reading a pool roundupdated 2026-10-19Reading miner specifications (and their units)updated 2026-10-19Time-of-use rates: scheduling mining around the clockupdated 2026-10-19Miner vs node: who actually enforces the rulesupdated 2026-10-19Your first miner: the go/no-go checklistupdated 2026-10-19Demand charges: you're billed on your peak, not just your kWhupdated 2026-10-19Monitoring baselines and safe restartsupdated 2026-10-16PPS, PROP, PPLNS: how pools payupdated 2026-10-16Hashrate: what those TH/s numbers actually meanupdated 2026-10-19Confirmations: why 'confirmed' is a probability, not a switchupdated 2026-10-19Mine or buy? The honest comparisonupdated 2026-10-19Miner efficiency: the J/TH that decides who survivesupdated 2026-10-19Securing the operation: management access and payout custodyupdated 2026-10-16Stale shares and latency: why ping barely mattersupdated 2026-10-19Buying used miners: inspection and seller checksupdated 2026-10-19Payout address safety: the one typo that costs everythingupdated 2026-10-19Measure your miner's real power drawupdated 2026-10-19Reading profit estimates, sensitivity, and payback honestlyupdated 2026-10-19Reconciling pool payouts: expected vs actually paidupdated 2026-10-19Network difficulty vs share difficultyupdated 2026-10-19Rejected shares: the troubleshooting ladderupdated 2026-10-19Site electrical review: before you add loadupdated 2026-10-16Choosing a pool: the actual checklistupdated 2026-10-19Cooling and heat: every watt becomes heatupdated 2026-10-19Uptime, availability, and reconciling the energy model
Stratum: how your miner talks to a pool · pow.family