Arthur Hayes called it:
“Btw just because I dumped my entire $HYPE bag, doesn't mean I still don't have faith $HYPE will best $SOL by year end. Sometimes you gotta go down to go up.”
We find out by Dec 31, 2026. 129 days to go
Arthur Hayes: “Btw just because I dumped my entire $HYPE bag, doesn't mean I still don't have faith $HYPE will best $SOL by year end. Sometimes you gotta go down to go up.”
MET if the percentage change in HYPE-USD price is at or above the percentage change in SOL-USD price on the deadline date, before 2026-12-31 23:59 (UTC).
Settles automatically from the locked data source — no judgment call, no human vote.
The original wording did not settle the timing on its own. The reading above was chosen at registration and locked with the claim — it was not decided after the fact.
Test details
Settled at the close of 2026-12-31 UTC: the claim is TRUE if the percentage change in the price of HYPE from 2026-06-05 (the statement date) through 2026-12-31 is greater than or equal to the percentage change in the price of SOL over the same window; FALSE otherwise.
Quote verified against the source
Added by Thonest from a public source. The person quoted did not submit, approve, or endorse this record; the wording is verified against the source itself.
Post on X in which Hayes disclosed selling his entire HYPE position while maintaining that HYPE would outperform SOL by the end of 2026.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x407e228244ac58a9656f1e7774e52d3f4bcbb9aa13ad41dabc6992f8c50c84d5
- 0x74d5625359dc2aacc65b52d5b802e5e578f93ec18b737f74a4191010ea2f34c2
batch #74 manifest · 4 entries
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
0xfb3d7075…960d78 on block explorer
This platform blocks archiving services, so no independent copy exists.
reported by the platform itself, not by the submitter
view the canonical capture · the platform's own API response, kept verbatim and covered by the evidence hash
✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.
The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.
Disputes
No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.
Related