Alex Thorn called it:
“BTC will hit $250k by year-end 2027. 2026 is too chaotic to predict, though Bitcoin making new all-time highs in 2026 is still possible. Options markets are currently pricing about equal odds of $70k or $130k for month-end June 2026, and equal odds of $50k or $250k by year-end…”
We find out by Dec 31, 2027. 494 days to go
Alex Thorn: “BTC will hit $250k by year-end 2027. 2026 is too chaotic to predict, though Bitcoin making new all-time highs in 2026 is still possible. Options markets are currently pricing about equal odds of $70k or $130k for month-end June 2026, and equal odds of $50k or $250k by year-end…”
MET if BTC-USD price is at or above 250,000 at any point, before 2027-12-31 23:59 (UTC).
Settles automatically from the locked data source — no judgment call, no human vote.
Test details
Resolves TRUE if the Coinbase BTC-USD spot price trades at or above $250,000 at any point between the statement date (2025-12-21) and 2027-12-31 23:59:59 UTC. Any single print at or above $250,000 within that window settles it TRUE; otherwise FALSE.
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 Thorn gave a Bitcoin price target for year-end 2027 while declining to forecast 2026, citing options-market pricing.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x33847b346483ae92db1decff9eee54ea97975e59783bd16b9ab73028d4f5aed7
- 0x134eb724e4a671470debf2f4131db20ea122ef7e7d9df1432b533f00bac88ae3
batch #73 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
0xd0ad5d6c…c60080 on block explorer
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