Begin with the three-source model
Read the Bitcoin integration guide first. Keep node context, device telemetry, and pool observations separate in your contract. Write down the one operational question your first view should answer, such as which expected workers have fresh measurements.
Check the arithmetic before the chart
Use the hashrate guide to inspect scope, units, windows, and coverage. Work through its fictional calculations with a test fixture. A comparison should retain the conditions under which its values were obtained rather than relying on a matching label alone.
Add upstream context deliberately
The pool guide explains why connection state, accepted work, and account reporting belong to different parts of the model. Keep worker mappings and counter definitions explicit. When two sources disagree, give the operator their timestamps and definitions rather than merging the values into an unexplained score.
Your first implementation exercise
Fetch the ASIC sample, render its typed worker values, and add separate views for stale and unavailable observations. Then inspect the documentation to decide what an authorized collector would have to supply. Keep the fixture and the future live source clearly labeled so a collection failure cannot be mistaken for a healthy sample.
