Peter Wildeford called it:
“My assessment is that there’s roughly a 30% chance of a significant AI-driven market correction with at least a >20% drawdown in AI-heavy stocks, sometime within the next three years.”
We find out by Oct 29, 2028. 800 days to go
Peter Wildeford: “My assessment is that there’s roughly a 30% chance of a significant AI-driven market correction with at least a >20% drawdown in AI-heavy stocks, sometime within the next three years.”
MET if A significant AI-driven market correction in which AI-heavy stocks fall more than 20% peak-to-trough: a decline of more than 20% from a prior peak in a widely followed AI-focused equity benchmark (an AI/semiconductor index, or a market-cap-weighted basket of leading AI infrastructure names such as NVIDIA, Microsoft, AMD, Broadcom and Oracle), described by reputable financial press as an AI-driven correction/repricing. Declines of 20% or less do not count; drawdowns driven by causes unrelated to AI expectations do not count at any point, before 2028-10-29 23:59 (UTC).
Settles by documented review of public evidence against these locked criteria; the reviewer is named and the reasoning published.
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
Resolves YES if, at any time between 2025-10-29 and 2028-10-29, AI-heavy stocks experience a peak-to-trough decline of more than 20% that reputable financial press attributes to an AI-driven repricing/correction. A decline of 20% or less, or a drawdown not attributed to AI expectations, resolves NO. The stated 30% probability is recorded but is not itself scored.
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.
Read the original on blog.peterwildeford.com ↗
Concluding forecast section of Wildeford's essay 'AI is probably not a bubble', published Oct 29, 2025.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x02a26f4a9d1977faaad8a8164a610f1eb780d66cd7b05d567545e5dfd59e6faa
- 0x39679cb5c86d0e4bd8a53d988e308cdba34a7473ffd47348f202bbc1debcd158
batch #55 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
0xf6d1964d…9b2cb9 on block explorer
view the canonical capture · the page as served to us, 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