Rob Hadick called it:
On the record 33 days and counting. Nobody can edit it, including Rob.
No objective test could be drawn from these words without inventing criteria the speaker never set, so it is preserved rather than scored.
This is kept for what it is: something said, on a date, from a source anyone can check. No test was locked, so nothing settles it and it is never counted for or against anyone. Thonest will not invent a threshold or a date that was never said — a claim scored against criteria written afterwards would prove nothing.
Submitter-attested — no machine-readable 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.
Watch what they said — from 2:11 ↗
Reactions are about the record being worth keeping — never about whether the person was right. They are never counted for or against anyone, and never used to rank anything.
Discussion
Loading…
Andrew Ross Sorkin: What does that mean in the context of where crypto itself goes? Rob Hadick: I expect a good 2026. For token prices like Bitcoin and Ethereum, there's likely to be continued momentum macroeconomically with better monetary policy and increased adoption of tokenized assets. McKinsey said 3% of cross-border payments happen in stablecoins today, up from zero, and I expect a 10-fold increase from that. Andrew Ross Sorkin: If you could only do one thing within crypto, which part would you invest in?
Transcribed from the audio and confirmed by the submitter, who listened to this passage. YouTube confirms the video and the channel, not the words — those are checkable in one click by anyone.
History — append-only
Proof
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.
From "Dragonfly's Rob Hadick on 2026 crypto outlook, bitcoin price trends and future of prediction markets" (CNBC Television).
✓ 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.