Field note

What hashprice means for a small operation

18 January 2026 · Hae-won Choi

Abstract view of networked hardware suggesting hash work

Hashprice compresses network reward and fee conditions into a revenue-per-hash figure. For a small fleet, the useful step is converting that figure into expected daily revenue after uptime and pool fees—not quoting the market number in isolation.

Start from your online terahash

Nameplate hashrate is not online hashrate. Subtract known maintenance windows and the hours you curtail for tariff peaks. The remaining terahash is what multiplies against hashprice in a sober model.

Subtract fees before celebrating

Pool fees, stale shares, and occasional orphan effects belong in the revenue line. Operators who apply fees only in a footnote often discover break-even slipping by weeks once the cost map is written cleanly.

Keep power on its own axis

Hashprice does not know your night rate. In App Grove Core sessions we plot revenue from hashprice assumptions on one axis and power cost on another so a soft market and a hard tariff are not blamed on the same cause.

Use it in monitoring

During a cost monitoring checkup, compare realized daily revenue to the hashprice case you selected in the last advisory. Persistent gaps usually point to uptime, not to a mysterious market force.

← All field notes