Say which blocks the mining means were taken over

[bitcoinuniverseadmin]

Consumes the two fields added in bitcoinuniverseio/backend-apis#104, which is merged and deployed.

What was wrong

The Mining page printed this under the reward figures:

Means are measured over the last 960 collected blocks.

The mean was not measured over 960 blocks. A Zcash miner may pay its own share to a shielded address, and then neither the reward nor the fees can be derived from public data. The overlay leaves those blocks out of the mean rather than counting them as zero, which is right, and the sentence named a denominator the figure did not have.

Measured on the production history store: 643 of 19,318 recorded Zcash blocks carry no reward, spread evenly across every thousand-block bucket. About three percent of every window.

What it says now

When the counts and the window agree, exactly what it said before. When they do not:

The window is the last 960 collected blocks. The mean total reward is taken over the 931 of them that state one, and the mean fees over 931. A block whose reward cannot be derived from public data is left out of the mean rather than counted as zero.

Both fields are optional. Against an overlay released before they existed, readMeanBasis reports the window alone, which is the reading this page had and is still true.

Tests

mean-basis.spec.ts, seven cases: the agreeing window, each of the two narrower on its own, a window where nothing could be read, an overlay publishing neither, no window at all, and a count that is not a whole number.

npx vitest run src/app/universe    417 passed, 28 files
npx tsc --noEmit                   clean
npx eslint (changed files)         clean
node scripts/universe/check-text.mjs  pass

The Zcash visual fixture carries 931 of 960 so the matrix renders the sentence that only appears when the denominators differ. The Dogecoin one keeps an agreeing window, because every Dogecoin coinbase is transparent.

🤖 Generated with Claude Code