Tom Lee called it:
“So, we're pretty bullish. I think Ethereum, which is around 3,000, can easily get to 9,000, 7,000 in early 2026.”
On the record 0 days and counting. Nobody can edit it, including Tom.
This will never resolve. No objective test could be drawn from these words without inventing criteria the speaker never set, so it is preserved rather than scored. It stays on the record as something said on a date, and is never counted for or against anyone.
Tom Lee: “So, we're pretty bullish. I think Ethereum, which is around 3,000, can easily get to 9,000, 7,000 in early 2026.”
No objective test could be drawn from these words without inventing criteria the speaker never set, so it is preserved rather than scored.
No objective test could be drawn from these words, so nothing can settle it. The statement is preserved and dated, and 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
Watch what they said — from 1:43 ↗
- ✓ Video and channel verified by YouTube
- ✓ Statement located at 1:53
- — Transcribed and timestamped by the submitter, who confirms they listened to the passage
Tom Lee: And that's going to bring a lot of efficiencies to Wall Street, but it really brings the use case forward for something like Ethereum. Tom Lee: So, we're pretty bullish. I think Ethereum, which is around 3,000, can easily get to 9,000, 7,000 in early 2026. Tom Lee: And then over time, as it starts to be competitive with payment rails, could get to the 20,000 level. So I'm pretty bullish.
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. Watch the full moment →
From "Tom Lee's 2026 Crypto Prediction" (Fundstrat).
History — append-only
Proof
3 hashes from this record to the anchored root
- 0x7b32cd8fd52525204a38046ab43904ffe88e3720081f396d84c462d862a15412
- 0xf98d08bb7614c52c9a5dc7f1795fc46f375ae6fc2cca874ef13b9604184eb103
- 0xd8a1a78199f3edb35150d5c900d620e50718eb8231048d7e68166119c076c6d7
batch #34 manifest · 8 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
0xd6867dc5…e1a1ad on block explorer
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.