Stratum is the communication protocol that connects a Bitcoin miner to a mining pool. The ASIC miner does the SHA-256 hashing, but Stratum is how the machine receives work from the pool and sends completed work back.
From an IT perspective, Stratum is one of the most important invisible systems in a mining facility. A miner can have healthy hashboards, a working PSU, good temperatures, and a live Ethernet link—but if its Stratum session to the pool is broken, that machine is not doing useful pooled mining work.
Stratum Sits Between the ASIC and the Mining Pool
The physical mining chain is straightforward. The network interface on the control board connects the miner to Ethernet. The switch forwards that traffic upstream. The router or firewall provides the path out of the site. Then Stratum carries mining-specific messages between the miner and the pool.
The official Stratum V2 specification describes the Mining Protocol as the direct communication layer between mining devices, proxies, and pool servers. Its job is to distribute mining work and accept proof-of-work submissions.
The Pool Sends Jobs to the Miner
A mining pool has to tell connected miners what to hash. That assignment is commonly called a mining job. It contains the information needed for the miner to search a valid portion of the Bitcoin proof-of-work space.
Under Stratum V2, the Mining Protocol specification defines standard and extended jobs, channels, targets, previous-block hashes, job IDs, and the search space assigned to mining devices. The pool or proxy has to make sure miners are not wasting energy by repeatedly searching the same work.
The ASIC Searches the Job at Massive Speed
Once the control board receives a job, it prepares work for the hashing hardware. The ASIC chips on the hashboards then test enormous numbers of candidate hashes by changing values such as the nonce and other permitted fields.
The mining pool does not need every hash the ASIC computes. That would create an impossible amount of network traffic. Instead, the miner only submits results that meet a lower pool-defined target called a share.
Shares Prove the Miner Is Doing Work
A pool share is proof that the miner performed a statistically meaningful amount of hashing. Most shares are not valid Bitcoin blocks, but they let the pool estimate how much work each miner contributed.
BitcoinVersus.Tech’s guide to accepted, rejected, and stale shares explains the accounting side. Stratum is the transport path that carries those share submissions from the miner back to the pool.
Vardiff Changes How Hard a Share Must Be
Variable difficulty, or vardiff, lets the pool assign a share target appropriate for the miner’s hashrate. A very fast ASIC needs a harder share target so it does not overwhelm the pool with submissions. A slower miner can use an easier target and still send enough samples for the pool to estimate performance.
That target is separate from Bitcoin’s full network difficulty. The pool share difficulty is an accounting and communication tool; only an exceptionally rare hash that also satisfies the Bitcoin network target becomes a valid block.
Worker Names Tell the Pool Which Miner Gets Credit
Mining-pool configuration usually includes a pool address plus a worker identity. A farm might use names such as siteA-row12-miner04 so operators can identify where hashrate is coming from.
The Stratum V2 specification includes a user_identity field for identifying or authorizing a mining channel. BitcoinVersus.Tech’s pool settings, worker names, and failover guide shows the operational side of the same concept on AxeOS.
Pool URLs Are More Than Just Web Addresses
A mining configuration often contains a hostname, port, worker identity, and protocol scheme. Depending on the pool and firmware, an operator may see forms such as stratum+tcp://, encrypted variants, or Stratum V2-specific connection strings.
The hostname still depends on normal IT services. The miner may need DNS to resolve the pool name, an IP route to reach the server, and a firewall policy that allows the connection. That is why mining-pool connectivity can fail even when the ASIC hardware itself is healthy.
TCP Keeps the Mining Session Ordered
Stratum mining traffic is commonly carried over a connection-oriented transport such as TCP. The Stratum V2 specification requires ordered delivery of protocol messages and describes TCP as a normal transport choice.
This is where ordinary networking becomes mining economics. If a site has unstable uplinks, bad cabling, packet loss, or repeated reconnects, the pool connection can suffer even though the hashing silicon is running perfectly.
Packet Loss and Latency Can Turn Into Stale Work
When Bitcoin finds a new block, pools need to move miners onto new work quickly. A miner that keeps hashing an old job for too long may submit a stale share after the pool has already moved on.
That is why packet loss and jitter matter in a mining operation. Bitcoin mining traffic is tiny compared with AI or storage traffic, but timing and reliability still matter because stale work earns less or nothing depending on the pool’s rules.
A Pool Proxy Can Aggregate Many Miners
Large farms do not always need every ASIC to maintain a completely independent upstream relationship with the pool. A mining proxy can sit between a group of miners and the pool, aggregate connections, distribute work locally, and reduce repeated upstream traffic.
The Stratum V2 protocol explicitly defines the Mining Proxy role. A proxy can relay or aggregate channels from many downstream mining devices, which is useful when a site has hundreds or thousands of ASICs behind the same infrastructure.
Stratum V1 Became the Industry Workhorse
Stratum V1 emerged as Bitcoin mining outgrew earlier getwork-style communication. Braiins’ history of mining protocols describes V1 as the protocol that became the de facto standard for pooled Bitcoin mining as network hashrate expanded from tiny early deployments into industrial ASIC fleets.
Its longevity is impressive, but V1 was never designed as a precise modern industry standard. Different implementations evolved, security was limited, and pool operators retained most of the control over block-template construction.
Stratum V2 Is the Modern Upgrade
Stratum V2 is the next-generation protocol designed to improve efficiency, security, scalability, and miner autonomy. Its specification separates the system into a Mining Protocol, Job Declaration Protocol, and Template Distribution Protocol.
The open Stratum V2 specification describes the redesign as an effort to improve mining-job distribution and result submission while adding stronger security and support for miner-selected transaction sets.
Stratum V2 Encrypts Remote Mining Communication
One of Stratum V2’s major IT improvements is authenticated encryption. The protocol security specification uses authenticated encryption with associated data and supports a Noise Protocol Framework handshake for secured communication.
That matters because mining traffic contains information about work assignments, share submissions, user identities, and hashrate. Protecting that connection reduces the risk of an attacker reading or manipulating the traffic between a miner and its upstream pool infrastructure.
Stratum V2 Can Let Miners Choose Transactions
Stratum V2 also includes Job Declaration. Instead of requiring the pool to choose every transaction in the candidate block, a mining operation can construct a custom block template and declare that work to a compatible pool.
The Job Declaration Protocol was designed specifically so pools do not have to unilaterally impose the transaction set. BitcoinVersus.Tech has followed that decentralization effort through Stratum V2 and open-source mining infrastructure development.
The Miner Still Needs Ordinary IT Before Stratum Can Work
Stratum sits high enough in the stack that several lower-level systems must already be healthy. The miner needs a working Ethernet interface, cable, switch port, IP address, subnet, gateway, and usually DNS.
A failed pool connection can therefore be caused by the miner, switch, router, firewall, DNS resolver, upstream internet provider, pool endpoint, or Stratum configuration. This is why a good mining technician troubleshoots from the physical layer upward instead of immediately replacing hardware.
SNMP Can Show the Infrastructure Around the Stratum Session
The ASIC itself may expose mining-specific telemetry, while the surrounding network can be monitored separately. BitcoinVersus.Tech’s SNMP mining-infrastructure guide shows how switches, PDUs, UPS systems, and sensors can be monitored alongside miner APIs.
That combination is powerful. Miner telemetry can say “pool disconnected,” while SNMP counters can reveal that an uplink started dropping packets at the same moment.
Failover Pools Keep a Miner From Sitting Idle
Most mining firmware allows operators to configure more than one pool endpoint. If the primary pool becomes unreachable, the miner can attempt a secondary or tertiary destination.
This is simple network resiliency applied to mining economics. An ASIC that loses its preferred endpoint should not sit powered on and hashing useless work if another valid pool is available. Pool failover belongs in the same operational category as redundant uplinks, spare switches, and monitored power systems.
Stratum Errors Often Look Like Hardware Problems at First
A technician may see low pool hashrate, rejected shares, repeated reconnects, stale work, or a miner that appears “offline” in the pool dashboard. None of those symptoms automatically prove the hashboard is bad.
The right workflow is to check local hashrate, logs, network reachability, switch state, pool configuration, worker credentials, DNS, routing, latency, and error counters before opening the machine. BitcoinVersus.Tech’s coverage of Braiins OS startup diagnostics shows why firmware telemetry belongs beside physical troubleshooting.
The Simple Way to Remember It
The pool creates or coordinates work. Stratum delivers the job. The control board feeds the job to the ASICs. The hashboards search it. Stratum sends qualifying shares back to the pool.
That makes Stratum the bridge between Bitcoin-mining hardware and ordinary IT networking. It depends on Ethernet, TCP, DNS, routing, switches, worker identities, and reliable internet connectivity—but the data moving across that infrastructure is specialized for proof-of-work mining.
Stratum V1 made industrial pool mining practical. Stratum V2 is the modern effort to make that connection more efficient, more secure, and more decentralized.
Editor’s Note
Pool URLs, port numbers, authentication formats, encryption support, proxy behavior, and Stratum V2 feature support vary by mining pool and firmware. Always use the current connection information provided by the specific pool and miner software.
Featured image: Canaan AvalonMiner A10 Bitcoin Mining Machines, Canaan / Wikimedia Commons, CC BY-SA 4.0; cropped to 1200×630 for BitcoinVersus.Tech. In-body mining-hardware image: Steve Rainwater / Wikimedia Commons, CC0.
Support and donation options are available through BitcoinVersus.Tech.
BitcoinVersus.tech is not a financial advisor. Content is provided for informational purposes.
Leave a comment