Node context, proof-of-work measurements, and the boundary between device and pool observations. This topic collection connects 4 field guides across the Mining Lab so you can follow the implementation question rather than reading every article in publication order.
Begin with the guide closest to your current task, then follow its links to related concepts and the relevant API topic page. The articles keep examples separate from live services and point to one primary technical reference for further detail. Use the public JSON fixtures to test presentation and validation before connecting your own authorized environment.
As you read, keep a short record of the assumptions that matter to your application: the source of an observation, the response version, the expected units, and the behavior when a request fails. That record makes the examples easier to adapt without inheriting claims that do not apply to your system.
Hashrate and Difficulty: Read Mining Data Correctly
Understand measurement scope, averaging windows, unit conversions, and why a missing observation should never become an invented zero.
Read the field guide 6 min ↗
Bitcoin Miner API: A Practical Developer Guide
Separate node, device, and pool data. Build a read-only integration with explicit units, fresh observations, and reliable failure states.
Read the field guide 6 min ↗
Mining Pool APIs and Stratum: Know the Difference
Design a source-aware pool view that keeps job transport, worker identity, share observations, and account reporting in their proper places.
Read the field guide 6 min ↗
Proof of Work vs. Wallet APIs: Clear Boundaries
Mining equipment, blockchain nodes, wallet connections, and AI prompt workflows serve different roles. Give each a clear data contract.
Read the field guide 7 min ↗