Scarcity alone, with nothing else attached
The claim is one sentence. A capped supply, on its own, can pull work. Whatever it pulls is on Cardano's ledger, block by block, at the target it was won at.
The ledger reports two things about it: how much work arrived, and how long it kept arriving. Neither figure presupposes a market price. Nothing in the protocol holds a miner here — nothing is signed, there is no minimum term and no notice — so every block is a fresh choice, and the reasons an operator makes it are their own. Whether it makes sense for you is a different question, and it has its own page.
That is what the name asks. Proof of work shows that work was done. It does not show what the work was for.
Four things this is not claiming
- That a hashpower switch can rewrite, challenge or change Bitcoin's rules
- The rules each node enforces bind miners, not the other way round. A majority of hashpower running modified rules forks off a minority-priced chain, which is what SegWit2x and the UASF episode showed.
- That anything here is an attack
- WHAT does not double-spend, inflate or reorganise anything. No chain is targeted and nothing is taken from anyone.
- That WHAT's own hashpower secures WHAT
- It does not, in any degree. All three security properties are Cardano's, and the only thing the work determines is which miner collects the reward.
- That proof of stake is better than proof of work
- We are not making that comparison. Bitcoin's design choices are deliberate, and its security argument is the cost of an attack — the premise this project borrows rather than disputes.
What a market price for WHAT would settle, and what it would not
A sustained non-zero price is evidence for the argument that scarcity alone can sustain market demand. A zero price is not evidence against it, because obscurity and no liquidity produce zero regardless.
The two halves are not symmetrical and the test does not pretend they are. One outcome tells you something; the other tells you only that not many people were looking. Saying so now, while there is no price either way, is the difference between a fair test and a number everybody argues about afterwards.
What moves the hardware is not only what the coins fetch today. A token is worth part its market price and part what somebody thinks that price will be later, so a miner mining here is pricing an expectation rather than collecting a settled rate. That runs in both directions. Hashpower can arrive while WHAT pays little per terahash, if the operator means to hold the coins; and good pay during a speculative run is not evidence that work can be bought at that rate for long. What the record establishes is that hashpower moved at a published reward and a published difficulty.
LIMIT
The claim above still holds once you allow for not knowing where the hashpower came from. A stronger one would not: nothing here supports a statement about how much of Bitcoin's security budget moved. See where arriving hashpower came from.
Having said what is claimed, the next question is a fair one: who arrived at this mechanism first, and what is actually new here.