Benjamin Cowen called it:
“So I think the 200-week moving average is going to come into play by the summer of 2026, I would say October 2026 at the latest.”
On the record 0 days and counting. Nobody can edit it, including Benjamin.
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.
Benjamin Cowen: “So I think the 200-week moving average is going to come into play by the summer of 2026, I would say October 2026 at the latest.”
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 31:33 ↗
- ✓ Video and channel verified by YouTube
- ✓ Statement located at 31:43
- — Transcribed and timestamped by the submitter, who confirms they listened to the passage
And from there where I would expect it to bottom out for a while would be the 200-week moving average. And the reason for that is because the 200-week moving average is something that just seemingly comes into play for Bitcoin every three to four years, right? So I think the 200-week moving average is going to come into play by the summer of 2026, I would say October 2026 at the latest.
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 "Analyst Called Bitcoin Top; Reveals 2026 Forecast | Ben Cowen" (David Lin ).
Resolution criteria
BTC touches or breaches its 200-week moving average on or before 31 October 2026.
History — append-only
Registered wording came from the extraction model's normalized claim rather than the source itself. The statement of record is now the verbatim excerpt from the source at 1903s. Was: "I think the 200-week moving average is going to come into play by the summer of 2026, I would say October 2026 at the latest." Source says: "So I think the 200-week moving average is going to come into play by the summer of 2026, I would say October 2026 at the latest." The original record and its anchor remain in history unchanged; this correction is appended.
Proof
2 hashes from this record to the anchored root
- 0x1514466fb6df301627d83f25117757b5c3ea9a303fe41b2635d75c08d798f7af
- 0x26c537b7852897a4b43fb240d84a9499161c1272075299430330e46695e66ec7
batch #30 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
0x4c4ff55b…fbd2c3 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.