Where the hashpower came from, the chain cannot tell you
A hash carries no provenance. The blocks show how much work arrived; they cannot show where the machine was yesterday. Bitcoin's own hashrate is the only signal of migration, and it will not show a small move.
LIMIT
This limit sits beside every hashrate figure on this site, because it decides how much weight any of them can carry.
Three origins that look identical from here
- Migrated
- Was mining Bitcoin and chose better pay. This is the only one of the three that moves work off Bitcoin's security budget. Rented hashrate — bought by the hour on an open market, where the buyer supplies the Stratum URL — sits here for the diversion, because for the rental period those machines are not on Bitcoin. It does not sit here for the choice: the owner sold an hour at a market rate and never weighed this chain at all. Anybody holding WHAT can buy that, so a rented block is not evidence that a fleet judged this chain the better place to point hashpower.
- Revived
- Was idle or unprofitable and came back online for WHAT. This is the offline reserve that Bitcoin's security model assumes will never be mobilised, and the reserve §1 of the paper is worried about.
- New
- Was never performing SHA-256d at all: a rig bought or built for this, or a GPU, or a CPU. Not a hypothetical here, because difficulty is held by Cardano's clock rather than by what a hash costs and sits legitimately below 1 on a quiet chain — which is why a CPU miner is one of the things §8 commits to publishing. What a rig needs to point here is the same two fields either way.
Only the first moves anything. Revived and new capacity add to the SHA-256d work in the world rather than moving any of it — so "every hash it attracts is a hash Bitcoin's security budget does not command" holds for all three, while "diverted from Bitcoin" holds only for migration.
What the limit does and does not damage
The claim being tested survives all three, because in each case a machine that could have been doing something else was pointed here instead, and the target it was won at is on the ledger. Rented hashrate is the one to discount: it records what a buyer paid for hashpower, not what an operator judged worth doing.
What the limit does damage is any stronger claim — how much hashpower was pulled off Bitcoin specifically, or how big the idle reserve turned out to be. Those need something the blocks do not carry, and no estimator or smoothing window puts it back.
There is one more limit, and it is about the block rate rather than where the work came from.