Every figure on this site rests on a model that was checked day-by-day against a real
mining account. This page is the running record: which days, what deviation, which source.
New entries are appended monthly; nothing old is quietly rewritten.
Model vs. real account, pure physics with per-epoch public difficulty, daily BTC fee
repricing, observed reinvestment growth (744 → 816 TH), documented $0.05/kWh lower bound,
discount 28.26%. 60 of 63 days within ±2%; weekly means below.
The three >2% days all sit at the June 27/28 difficulty boundary — the platform applies
public retargets with a ~2-day lag.
All 63 days
Day
Farm TH (fitted)
Model gross (BTC)
Account gross (BTC)
Deviation
Upcoming entries
[Placeholder — month 1, month 2 … appended as new account data arrives; each entry: account figures via the official API with retrieval date, model prediction as of that date, deviation, and what changed in the market]
Data rules
Three rules govern every number that enters this record, and they do not bend for a good story:
Account data appears only with per-figure approval. The account owner approves each figure
before it is published (as happened for the tables on this page and on Explained); approval of one figure is
not approval of the next. What has been ruled out permanently: wallet addresses, deposit addresses, and
balances of any kind — they appear nowhere on this site, in any entry, at any time.
Public figures carry their own source and date. Anything not derived from the account —
difficulty, BTC price, fee rates, discount caps, block reward — is cited to its documentation or explorer with
a retrieval date, and re-verified monthly. Where a public value is only available behind an account login
(secondary-market prices, in-app rates), the site either omits it or labels the account-session retrieval
explicitly; it never presents a logged-in number as public.
Nothing old is quietly rewritten. A published entry stays as it was written. If a later
entry contradicts an earlier one — the model improves, a platform parameter changes, an error surfaces — the
correction is appended as a new entry with its own date, and the earlier entry gets a pointer to it. The same
rule as for corrected third-party errors: history is updated, not deleted.
Feed for the payout-premium question: these entries, plus any new account windows, are the data
behind calibrate.py's continuing question — whether realized payouts ever persistently
depart from pure network physics. After the gross-vs-net resolution (see Method),
the standing assumption is that they do not; each monthly entry tests that assumption against fresh data, and
a persistent departure would get its own documented factor, not a silent one.
Source data: official read-only API, retrieved 2026-08-30.