Version history
Every immutable snapshot of Wasabi Protocol. A new version is saved each time the page changes, with the reason it changed. Pick two versions to see exactly what changed.
- v20currentTrust score: 532026-11-01 21:51:36Z
Fact-check reviewFact-check review (verdict: approve): the reviewer checked the page's claims against its sources; the trust score was recalculated from the page's findings, 52 → 53.
hash: 97b500be9f42…changes from v19 - v19Trust score: 532026-11-01 21:51:35Z
Score recalculatedRecalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 52 → 53. Problems weighed by who is responsible: incidents the subject suffered −13.2, concerns that are not fraud −6, problems around the subject, caused by others −1.1; legitimacy credit long-running +4; 1 section(s) set aside until a failed fact-check is resolved; accepted community evidence −5.9.
hash: 97b500be9f42…changes from v18 - v18Trust score: 522026-11-01 21:49:54Z
Score recalculatedRe-read and rescored after the page was re-researched (2026-11-01). Rescored under Scoring v2, the published formula (avoid.net/scoring): 53 → 52. Problems weighed by who is responsible: incidents the subject suffered −13.2, concerns that are not fraud −6, problems around the subject, caused by others −1.9; legitimacy credit long-running +4; accepted community evidence −5.9.
hash: 92dd890979d4…changes from v17 - v17Trust score: 532026-11-01 20:19:05Z
Re-researchedRe-researched in full by the investigator agent at a reader's request; the text was rewritten from new research.
hash: 954728d2ae1f…changes from v16 - v16Trust score: 532026-11-01 20:19:05Z
Before rewriteThe page as it stood just before it was rewritten; the next version says why.
hash: a9e10feb37a2…changes from v15 - v15Trust score: 532026-11-01 17:53:19Z
Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the trust score was recalculated from the page's findings, 52 → 53.
hash: 0d9e4cb35cc2…changes from v14 - v14Trust score: 532026-11-01 17:53:18Z
Score recalculatedRecalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 52 → 53. Problems weighed by who is responsible: incidents the subject suffered −13.2, concerns that are not fraud −7.2; legitimacy credit long-running +4; 1 section(s) set aside until a failed fact-check is resolved; accepted community evidence −5.9.
hash: 0d9e4cb35cc2…changes from v13 - v13Trust score: 522026-11-01 12:37:25Z
Score recalculatedRescored under Scoring v2, the published formula (avoid.net/scoring): 0 → 52. Problems weighed by who is responsible: incidents the subject suffered −13.2, concerns that are not fraud −7.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +4; accepted community evidence −5.9; fact-check adjustments (−13) now shown as page reliability, not in the score.
hash: ee3fcf336bbc…changes from v12 - v12Trust score: 02026-11-01 12:37:24Z
Before rewriteThe page as it stood just before its Scoring v2 rescore; the next version says why.
hash: d31e9e45c95c…changes from v11 - v11Trust score: 02026-10-29 16:26:34Z
Re-researchedRe-researched in full by the investigator agent at a reader's request; the text was rewritten from new research.
hash: 3e427a4c443c…changes from v10 - v10Trust score: 02026-10-29 16:26:34Z
Before rewriteThe page as it stood just before it was rewritten; the next version says why.
hash: c8907158f4ec…changes from v9 - v9Trust score: 02026-10-29 13:55:50Z
Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the judge moved the trust score from 3 to 0.
hash: 3e70843dffd2…changes from v8 - v8Trust score: 32026-10-28 04:31:48Z
Re-researchedRe-researched in full by the investigator agent at a reader's request; the text was rewritten from new research.
hash: b1e29307215b…changes from v7 - v7Trust score: 32026-10-28 04:31:48Z
Before rewriteThe page as it stood just before it was rewritten; the next version says why.
hash: 281d186ff25a…changes from v6 - v6Trust score: 32026-10-26 22:57:00Z
Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the judge moved the trust score from 8 to 3.
hash: e6c6f354ce2c…changes from v5 - v5Trust score: 82026-10-26 22:55:15Z
Re-researchedRe-researched in full by the investigator agent at a reader's request; the text was rewritten from new research.
hash: 85ef57bbe2d6…changes from v4 - v4Trust score: 82026-10-26 22:55:15Z
Before rewriteThe page as it stood just before it was rewritten; the next version says why.
hash: d4b06390b0ff…changes from v3 - v3Trust score: 82026-10-17 03:28:27Z
Community evidenceA moderator accepted a piece of community-submitted evidence: The Block confirms Wasabi Protocol was exploited for over $5M via a compromised admin key/deployer wallet, and quotes Sodot's Shalev Keren describing the zero-delay admin role as an operational design choice rather than a code bug — matching the submission's note. Trust score now 8.
hash: 766frps6xUBb…changes from v2 - v2Trust score: 142026-10-16 02:28:41Z
Community evidenceA moderator accepted a piece of community-submitted evidence: Halborn's post-mortem confirms the ~$5M Wasabi Protocol hack via the compromised wasabideployer.eth sole PerpManager admin account, with no multisig and timelock set to zero, draining funds across Ethereum, Base, Berachain and Blast, matching the submission. Trust score now 14.
hash: HixBH62WcgiZ…changes from v1 - v1Trust score: 172026-10-07 08:36:23Z
No reason was recorded for this version (saved before October 2026).
hash: E2hLPtA7FS2H…