A useful explanation of what share rejection metrics can indicate must connect terminology with evidence. Here, the evidence is organized around network latency, job changes and hardware errors.
Pool statistics describe submitted work and payment rules; blockchain statistics describe accepted blocks and network consensus. Confusing these layers leads to incorrect conclusions about shares and rewards.
Network Latency
Use network latency as a testable input, not a general description. Record what produced the value, the interval it covers and any exclusions. Compare the record with job changes only after both use compatible boundaries; otherwise the apparent difference may come from definitions rather than performance.
- Evidence: a dated record for network latency.
- Cross-check: compare it with job changes.
- Review trigger: repeat the check after a material change affecting network latency.
Job Changes
Treat job changes as one layer of the system. Ask who controls it, how often it changes and which record can verify it. Its connection to hardware errors should be explained explicitly, because two correlated values do not automatically prove that one caused the other.
- Evidence: a dated record for job changes.
- Cross-check: compare it with hardware errors.
- Review trigger: repeat the check after a material change affecting job changes.
Hardware Errors
Evaluate hardware errors with a small evidence chain: source, timestamp, unit, boundary and calculation. Follow the same chain for network latency. This prevents a precise-looking result from combining incompatible observations and makes future updates less dependent on undocumented assumptions.
- Evidence: a dated record for hardware errors.
- Cross-check: compare it with network latency.
- Review trigger: repeat the check after a material change affecting hardware errors.
What share rejection metrics can indicate: evaluation sequence
- Write the exact decision involving network latency.
- Collect job changes using the same observation period.
- Test how the conclusion changes when hardware errors moves.
- Save the source values, conversions and date of review.
Reference for Pools and Network
Verify the underlying context with Bitcoin Developer Guide: pooled mining. For values that change over time, use a current source and record its retrieval date.
