Skip to main content
AVOID.NET

Version history

Every immutable snapshot of Ekubo Protocol. A new version is saved each time the page changes, with the reason it changed. Pick two versions to see exactly what changed.

Compare→
  1. v11currentTrust score: 632026-11-17 21:06:02Z

    Fact-check reviewFact-check review (verdict: approve): the reviewer checked the page's claims against its sources; the trust score did not change.

    hash: c6d0b390e9d3…changes from v10
  2. v10Trust score: 632026-11-17 21:03:05Z

    Score recalculatedRe-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 61 → 63. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −3.2, problems around the subject, caused by others −0.9; legitimacy credit long-running +6; a recent unresolved incident −6.6; accepted community evidence −1.4.

    hash: c6d0b390e9d3…changes from v9
  3. v9Trust score: 612026-11-17 21:01:14Z

    EditedDraft repair sprint 2026-11-17: 6 fact-check findings addressed (sourced, corrected or removed); content that passed left unchanged.

    hash: 4a16d9f33755…changes from v8
  4. v8Trust score: 612026-11-17 21:01:13Z

    Before rewriteThe page as it stood just before it was rewritten; the next version says why.

    hash: 817513eb2a01…changes from v7
  5. v7Trust score: 612026-11-02 09:57:34Z

    Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the trust score did not change.

    hash: f864f10c6321…changes from v6
  6. v6Trust score: 612026-11-02 09:55:43Z

    Score recalculatedRe-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 71 → 61. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −4.4, problems around the subject, caused by others −0.6; legitimacy credit long-running +6; a recent unresolved incident −7.4; accepted community evidence −1.4.

    hash: f864f10c6321…changes from v5
  7. v5Trust score: 712026-11-02 08:36:11Z

    Re-researchedRe-researched in full by the investigator agent at a reader's request; the text was rewritten from new research.

    hash: becc348d07d3…changes from v4
  8. v4Trust score: 712026-11-02 08:36:11Z

    Before rewriteThe page as it stood just before it was rewritten; the next version says why.

    hash: 5d4ad94b1f1e…changes from v3
  9. v3Trust score: 712026-11-01 12:37:18Z

    Score recalculatedRescored under Scoring v2, the published formula (avoid.net/scoring): 51 → 71. Problems weighed by who is responsible: incidents the subject suffered −6, problems around the subject, caused by others −1.7, concerns that are not fraud −1.2; legitimacy credit long-running +6; 2 section(s) set aside until a failed fact-check is resolved; accepted community evidence −1.4; fact-check adjustments (−10) now shown as page reliability, not in the score.

    hash: c76913a3cf31…changes from v2
  10. v2Trust score: 512026-10-27 07:12:53Z

    Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the judge moved the trust score from 61 to 51.

    hash: 32cad35614b8…changes from v1
  11. v1Trust score: 612026-10-16 16:29:13Z

    Community evidenceA moderator accepted a piece of community-submitted evidence: The Block article confirms Ekubo lost ~$1.4M WBTC across ~85 transactions because v2 EVM extension router contracts accepted attacker-controlled payer/token/amount data without verifying authorization, per Blockaid. Trust score now 61.

    hash: AqmeJqq88DpE…