Hashpower & performance
Understand delivered work, changing network conditions, and the limits of an effort estimate.
Hashpower & workers
Sol/s means Equihash solutions per second. MSol/s and GSol/s are larger units of the same measurement. Worker counts and accepted hashrate come from the pool account at the displayed source timestamp.
A marketplace order is not a pool worker reading. An unavailable pool account does not establish zero hashrate or zero ZEC received.
Difficulty & hashpower dynamics
A model should use difficulty and hashpower observations from a compatible time window. A constant-difficulty estimate cannot describe changing competition, delivery interruptions, or future network conditions.
Zebra’s contextual-difficulty reference describes Zcash adjusting its difficulty threshold after each block. Bitcoin assumptions should therefore be re-examined before being used in a Zcash model.
Performance comparisons
- Keep advertised, marketplace-reported average, and pool-accepted hashpower separate.
- Align order start/end times, source timestamps, and available pool measurements.
- Record delivery gaps, unavailable histories, and the observation window.
- Compare costs in their original currency until a documented settlement rate is available.
The shift calculator
The calculator estimates the chance of at least one discovery from hypothetical hashpower, duration, and network difficulty. It assumes constant difficulty and hashpower with no downtime.
Expected blocks = Sol/s × seconds ÷ (difficulty × 8,192)
Chance of at least one block = 1 − exp(−expected blocks)