Skip to main content
AVOID.NET
← DODO AMM15 decisions on this page

Audit log

Every state-changing event for DODO AMM: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-05-28 18:37:20Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 422,776,111
    sig
    34NH2Z5KQhDK…DB7VJAPYexplorer ↗
    hash
    3c4cnzrCQfRz…uwbJCBDasha256 → base58
    verifying row…full verify ↗
    canonical bytes (10536 B) ▸
    {"actor":"system:backfill","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","kind":"publish","page_slug":"dodo-amm","published_at":"2026-05-28T18:37:20.809Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"DODO AMM","sections":[{"content":"","heading":"","severity":"none","sources":[{"credibility":2,"name":"What Is DODO? PMM Algorithm Explained — Gate Learn","type":"other","url":"https://www.gate.com/learn/articles/what-is-dodo/626"},{"credibility":2,"name":"DODO: Capital Efficient DEX — Messari","type":"research","url":"https://messari.io/report/dodo-capital-efficient-dex"},{"credibility":2,"name":"What Is DODO? — Binance Academy","type":"other","url":"https://academy.binance.com/en/articles/what-is-dodo"}]},{"content":"","heading":"","severity":"high","sources":[{"credibility":2,"name":"Explained: The DODO DEX Hack (March 2021) — Halborn","type":"research","url":"https://www.halborn.com/blog/post/explained-the-dodo-dex-hack-march-2021"},{"credibility":1,"name":"DODO DEX Drained of $3.8M in DeFi Exploit — CoinDesk","type":"news_article","url":"https://www.coindesk.com/tech/2021/03/09/dodo-dex-drained-of-38m-in-defi-exploit"},{"credibility":2,"name":"DODO Details $3.8 Million DeFi Attack in Post Mortem — BeInCrypto","type":"news_article","url":"https://beincrypto.com/dodo-details-defi-attack-post-mortem/"},{"credibility":1,"name":"Decentralized exchange DODO recovers some funds after attackers exploit bug for $3.8M — The Block","type":"news_article","url":"https://www.theblock.co/linked/97734/dodo-dex-exploit-bug-attack"},{"credibility":2,"name":"SlowMist: An Analysis of the Attack on DODO — SlowMist / Medium","type":"research","url":"https://slowmist.medium.com/an-analysis-of-the-attack-on-dodo-628128ee6f5f"},{"credibility":2,"name":"DeFi Hacks Continue: DODO Exploited for up to $3.8M — CryptoPotato","type":"news_article","url":"https://cryptopotato.com/defi-hacks-continue-decentralized-exchange-dodo-exploited-for-up-to-3-8m/"},{"credibility":2,"name":"DODO Finance Initialization Vulnerability — Quadriga Initiative","type":"community_report","url":"https://www.quadrigainitiative.com/casestudy/dodofinancehack.php"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":1,"name":"DODO Security Audits — DODO Official Documentation","type":"official","url":"https://docs.dodoex.io/en/home/security"},{"credibility":2,"name":"Explained: The DODO DEX Hack (March 2021) — Halborn","type":"research","url":"https://www.halborn.com/blog/post/explained-the-dodo-dex-hack-march-2021"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":2,"name":"DODO (DODO) Tokenomics — Tokenomist","type":"research","url":"https://tokenomist.ai/dodo"},{"credibility":2,"name":"DODO Token(DODO) Tokenomics and ICO/IDO Info — CoinCarp","type":"other","url":"https://www.coincarp.com/currencies/dodo/project-info/"},{"credibility":2,"name":"DODO (DODO) IDO Funding Rounds & Tokenomics Analysis — CryptoRank","type":"research","url":"https://cryptorank.io/ico/dodo"}]},{"content":"","heading":"","severity":"low","sources":[]},{"content":"","heading":"","severity":"low","sources":[{"credibility":2,"name":"DODO TVL, Fees, Revenue, Volume — DeFiLlama","type":"on_chain","url":"https://defillama.com/protocol/dodo"},{"credibility":2,"name":"Dodo DEX Review 2025 — Coin Bureau","type":"research","url":"https://coinbureau.com/review/dodo-dex-review"},{"credibility":2,"name":"DODO: Everything You Need To Know — Komodo Platform","type":"other","url":"https://komodoplatform.com/en/academy/what-is-dodo-dodo/"}]}],"sources_used":[{"credibility":2,"name":"Explained: The DODO DEX Hack (March 2021) — Halborn","type":"research","url":"https://www.halborn.com/blog/post/explained-the-dodo-dex-hack-march-2021"},{"credibility":1,"name":"DODO DEX Drained of $3.8M in DeFi Exploit — CoinDesk","type":"news_article","url":"https://www.coindesk.com/tech/2021/03/09/dodo-dex-drained-of-38m-in-defi-exploit"},{"credibility":2,"name":"DODO Details $3.8 Million DeFi Attack in Post Mortem — BeInCrypto","type":"news_article","url":"https://beincrypto.com/dodo-details-defi-attack-post-mortem/"},{"credibility":1,"name":"Decentralized exchange DODO recovers some funds after attackers exploit bug for $3.8M — The Block","type":"news_article","url":"https://www.theblock.co/linked/97734/dodo-dex-exploit-bug-attack"},{"credibility":2,"name":"SlowMist: An Analysis of the Attack on DODO — SlowMist / Medium","type":"research","url":"https://slowmist.medium.com/an-analysis-of-the-attack-on-dodo-628128ee6f5f"},{"credibility":2,"name":"DeFi Hacks Continue: DODO Exploited for up to $3.8M — CryptoPotato","type":"news_article","url":"https://cryptopotato.com/defi-hacks-continue-decentralized-exchange-dodo-exploited-for-up-to-3-8m/"},{"credibility":2,"name":"DODO Finance Initialization Vulnerability — Quadriga Initiative","type":"community_report","url":"https://www.quadrigainitiative.com/casestudy/dodofinancehack.php"},{"credibility":1,"name":"DODO Security Audits — DODO Official Documentation","type":"official","url":"https://docs.dodoex.io/en/home/security"},{"credibility":2,"name":"DODO TVL, Fees, Revenue, Volume — DeFiLlama","type":"on_chain","url":"https://defillama.com/protocol/dodo"},{"credibility":2,"name":"DODO (DODO) Tokenomics — Tokenomist","type":"research","url":"https://tokenomist.ai/dodo"},{"credibility":2,"name":"DODO Token(DODO) Tokenomics and ICO/IDO Info — CoinCarp","type":"other","url":"https://www.coincarp.com/currencies/dodo/project-info/"},{"credibility":2,"name":"DODO (DODO) IDO Funding Rounds & Tokenomics Analysis — CryptoRank","type":"research","url":"https://cryptorank.io/ico/dodo"},{"credibility":2,"name":"Dodo DEX Review 2025 — Coin Bureau","type":"research","url":"https://coinbureau.com/review/dodo-dex-review"},{"credibility":2,"name":"What Is DODO? PMM Algorithm Explained — Gate Learn","type":"other","url":"https://www.gate.com/learn/articles/what-is-dodo/626"},{"credibility":2,"name":"DODO: Capital Efficient DEX — Messari","type":"research","url":"https://messari.io/report/dodo-capital-efficient-dex"},{"credibility":1,"name":"DODO DEX Drained of $3.8M — Nasdaq (CoinDesk reprint)","type":"news_article","url":"https://www.nasdaq.com/articles/dodo-dex-drained-of-$3.8m-in-defi-exploit-2021-03-09"},{"credibility":2,"name":"Decentralized Exchange DODO Hacked For $3.8 Million — Yahoo Finance","type":"news_article","url":"https://finance.yahoo.com/news/decentralized-exchange-dodo-hacked-3-004826782.html"}],"summary":"DODO is a decentralized exchange (DEX) protocol launched in 2020, operating across 14 EVM-compatible chains, and known for its proprietary Proactive Market Maker (PMM) algorithm that concentrates liquidity near market price. On March 8, 2021, an attacker exploited a critical initialization vulnerability in DODO's V2 Crowdpooling smart contracts, draining approximately $3.8 million across four pools; roughly $3.1 million was subsequently recovered through voluntary restitution and frontrunning bot operator cooperation. The protocol continues to operate and has undergone multiple third-party security audits post-exploit, though it has lost significant market share and TVL since its 2021 peak.","timeline":[{"date":"2020-07-10","event":"DODO V1 smart contracts audited by PeckShield.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2020-09-18","event":"DODO V1 smart contracts audited by Trail of Bits.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2020-12-17","event":"DODO V2 contracts audited by PeckShield prior to V2 launch.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2021-02-18","event":"vDODO contracts audited by CertiK.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2021-03-08","event":"Attackers exploit a critical re-initialization vulnerability in DODO V2 Crowdpooling smart contracts, draining approximately $3.8 million from four pools (WSZO, WCRES, ETHA, FUSI) using flash loans. Two frontrunning MEV bots also execute the exploit ahead of the primary attacker.","source":"CoinDesk","source_url":"https://www.coindesk.com/tech/2021/03/09/dodo-dex-drained-of-38m-in-defi-exploit"},{"date":"2021-03-09","event":"DODO publicly discloses the attack; initial reports estimate $2.1 million in losses. Token price falls approximately 6% to $3.84. TVL declines 29% to $39 million.","source":"BeInCrypto","source_url":"https://beincrypto.com/dodo-dex-exploited-for-2-million-in-latest-defi-incursion/"},{"date":"2021-03-10","event":"DODO releases post-mortem with updated figures confirming $3.8 million total drained. Team reports recovery of $1.89 million (approximately 1,139,456 USDT and 411 ETH), with $200,000 frozen on an exchange. Net unrecovered loss estimated at approximately $700,000.","source":"BeInCrypto post-mortem","source_url":"https://beincrypto.com/dodo-details-defi-attack-post-mortem/"},{"date":"2021-03-16","event":"V2 CrowdPooling and Vending Machine contracts audited by Beosin — after the exploit had already occurred.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2021-04-13","event":"DODO V2 contracts audited by SlowMist as part of post-exploit remediation.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2021-12-15","event":"DODO LimitOrder, RFQ, and CrowdPooling V2 contracts audited by CertiK.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2022-12-12","event":"DODOFeeRouteProxy contract audited by Sherlock.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2023-07-01","event":"DODO V3 contracts audited by Sherlock.","source":"DODO Official Documentation","source_url":"https://docs.dodoex.io/en/home/security"},{"date":"2024-04-01","event":"DODO announces DODOchain, an omni-chain trading DEX initiative, as part of strategic pivot.","source":"Coin Bureau DODO DEX Review","source_url":"https://coinbureau.com/review/dodo-dex-review"},{"date":"2025-01-01","event":"DODO token vesting schedules fully complete; entire 1,000,000,000 token supply now circulating.","source":"Tokenomist DODO Unlock Events","source_url":"https://www.tokenomist.ai/dodo/unlock-events"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 97f902df-9834-496a-95a2-25409ef20038
  2. #2reviewby reviewerreviewer
    2026-08-18 16:55:18Z
    Score: 42 → 42 (no score change)
    The page's core narrative is well supported: a March 8, 2021 smart-contract exploit drained ~$3.8M from DODO's V2 Crowdpooling pools, and DODO's own account (corroborated by Quadriga Initiative) confirms ~$3.1M was recovered within 24 hours via attacker restitution and frontrunning-bot cooperation, consistent with the page's summary. All nine audit dates in the timeline match DODO's official security page exactly. Two defects were found: a wrong token-price figure (page says 6% drop to $3.84; contemporaneous reporting says ~2.55% to $3.94) and an internally inconsistent net-unrecovered-loss figure that conflates an early $1.89M recovery report with a later $3.1M final tally. The editorial language throughout is appropriately hedged (attack attributed to an external attacker, not to DODO), and no unhedged-allegation issues were found. No incidents beyond the single 2021 exploit were identified in five-plus years of subsequent operation, which is a point in the entity's favor that the page does not explicitly foreground.
    anchoranchored
    chain
    ●mainnet-betaslot 443,508,335
    sig
    3cquukDqjETD…yP382vZ1explorer ↗
    hash
    BsG8fGAh5mxm…jPWC9AuLsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1378 B) ▸
    {"actor":"reviewer","decided_at":"2026-08-18T16:55:18.552Z","decision":"review","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","new_score":42,"page_slug":"dodo-amm","prev_score":42,"reason":"The page's core narrative is well supported: a March 8, 2021 smart-contract exploit drained ~$3.8M from DODO's V2 Crowdpooling pools, and DODO's own account (corroborated by Quadriga Initiative) confirms ~$3.1M was recovered within 24 hours via attacker restitution and frontrunning-bot cooperation, consistent with the page's summary. All nine audit dates in the timeline match DODO's official security page exactly. Two defects were found: a wrong token-price figure (page says 6% drop to $3.84; contemporaneous reporting says ~2.55% to $3.94) and an internally inconsistent net-unrecovered-loss figure that conflates an early $1.89M recovery report with a later $3.1M final tally. The editorial language throughout is appropriately hedged (attack attributed to an external attacker, not to DODO), and no unhedged-allegation issues were found. No incidents beyond the single 2021 exploit were identified in five-plus years of subsequent operation, which is a point in the entity's favor that the page does not explicitly foreground.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 63cacef2-7a59-4c88-b246-50bf819beb68
  3. #3review reviseby judgejudge
    2026-08-18 16:55:18Z
    Score: 42 → 60 (+18)
    The reviewer classifies the sole material incident on the page — the March 8, 2021 V2 Crowdpooling exploit — as attribution 'b' (suffered), noting DODO was the victim of an external smart-contract attack, published a transparent post-mortem, recovered roughly 82% of the drained funds within 24 hours (claim_findings[3]-[4], both confirmed), and has had no further exploits, fraud allegations, or regulatory actions in over five years of subsequent operation (calibration_assessment.incident_attributions[0]). Per the scoring rubric's own worked example, a suffered hack with this recovery profile caps exposure at CAUTIONARY (50-69), not WARNING (20-49); the current 42/WARNING score appears to be treating the incident as entity-attributable risk rather than victimhood. The reviewer's recommended 60 appropriately sits mid-band rather than at the top, reflecting two legitimate residual drags that are unrelated to fraud: the exploited Crowdpooling contracts shipped without a pre-launch audit (a process gap, not misconduct), and the protocol's TVL/market relevance has declined sharply since 2021. This is a correction in the entity's favor — the page's own hedged language ('an attacker exploited,' 'voluntary restitution') already reflects the suffered-hack read; the score band did not.
    anchoranchored
    chain
    ●mainnet-betaslot 443,508,339
    sig
    3KBsJkaeaZAZ…PLLKRAwGexplorer ↗
    hash
    5KwmDakGe8PG…kMnqxjkYsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1643 B) ▸
    {"actor":"judge","decided_at":"2026-08-18T16:55:18.552Z","decision":"review_revise","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","new_score":60,"page_slug":"dodo-amm","prev_score":42,"reason":"The reviewer classifies the sole material incident on the page — the March 8, 2021 V2 Crowdpooling exploit — as attribution 'b' (suffered), noting DODO was the victim of an external smart-contract attack, published a transparent post-mortem, recovered roughly 82% of the drained funds within 24 hours (claim_findings[3]-[4], both confirmed), and has had no further exploits, fraud allegations, or regulatory actions in over five years of subsequent operation (calibration_assessment.incident_attributions[0]). Per the scoring rubric's own worked example, a suffered hack with this recovery profile caps exposure at CAUTIONARY (50-69), not WARNING (20-49); the current 42/WARNING score appears to be treating the incident as entity-attributable risk rather than victimhood. The reviewer's recommended 60 appropriately sits mid-band rather than at the top, reflecting two legitimate residual drags that are unrelated to fraud: the exploited Crowdpooling contracts shipped without a pre-launch audit (a process gap, not misconduct), and the protocol's TVL/market relevance has declined sharply since 2021. This is a correction in the entity's favor — the page's own hedged language ('an attacker exploited,' 'voluntary restitution') already reflects the suffered-hack read; the score band did not.","score_delta":18,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision f498d385-b7b0-4fd9-982e-9b73a7e2ac2f
  4. #4reviewby reviewerreviewer
    2026-10-16 16:50:38Z
    Score: 62 → 62 (no score change)
    The page's core narrative — DODO's August 2020 launch, the March 8, 2021 Crowdpool exploit draining ~$3.8M with ~$3.1M later returned by front-running bots, the funding history, and the absence of any US regulatory action — holds up well against independent sources. However, the Security and Audits section contains a verifiable, internally relevant error: it and the corresponding timeline entries mislabel which audit (PeckShield Dec 2020 V2, vs. CertiK Feb 2021 vDODO) preceded the vulnerable code changes, which actually contradicts the page's own exploit section narrative blaming the PeckShield audit. The DODO token's all-time-high price ($8.49) is also inconsistent with the page's own cited source (CoinGecko), which shows $8.38, matched by every other tracker checked. A handful of claims (90% V3 gas savings, the three-DAO governance structure, and some founder biographical detail) could not be independently verified with the sources available. The seed-round co-lead attribution to DeFiance Capital is only weakly corroborated by a secondary source not cited on the page.
    anchoranchored
    chain
    ●mainnet-betaslot 457,710,457
    sig
    5jpy4iwmnutg…8opYTdW5explorer ↗
    hash
    76Pj9BrRSwsE…Ynnne1Wisha256 → base58
    verifying row…full verify ↗
    canonical bytes (1680 B) ▸
    {"actor":"reviewer","artifact_identity":"72bdf83f61dec785beb574c3c6f572c9","decided_at":"2026-10-16T16:50:38.680Z","decision":"review","disputed_pct":0.3913,"findings_hash":"EmcjDYBfak6ML2RfFScoGVszeBnmFdZFKRfx27r9bHSr","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","mode":"findings_only","new_score":62,"page_content_hash":"1bcdcbefc7f0ced44c33b5690bed89defacbd6f0883c73d09842c31315bdc7c6","page_slug":"dodo-amm","prev_score":62,"reason":"The page's core narrative — DODO's August 2020 launch, the March 8, 2021 Crowdpool exploit draining ~$3.8M with ~$3.1M later returned by front-running bots, the funding history, and the absence of any US regulatory action — holds up well against independent sources. However, the Security and Audits section contains a verifiable, internally relevant error: it and the corresponding timeline entries mislabel which audit (PeckShield Dec 2020 V2, vs. CertiK Feb 2021 vDODO) preceded the vulnerable code changes, which actually contradicts the page's own exploit section narrative blaming the PeckShield audit. The DODO token's all-time-high price ($8.49) is also inconsistent with the page's own cited source (CoinGecko), which shows $8.38, matched by every other tracker checked. A handful of claims (90% V3 gas savings, the three-DAO governance structure, and some founder biographical detail) could not be independently verified with the sources available. The seed-round co-lead attribution to DeFiance Capital is only weakly corroborated by a secondary source not cited on the page.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision ebc6103b-b9c4-48ec-b7dd-c53f3b8d32b4
  5. #5reviewby reviewerreviewer
    2026-10-27 11:11:59Z
    Score: 62 → 62 (no score change)
    The core exploit facts (March 2021, $3.8M, four named Crowdpools) check out against CoinDesk. The recovery figure of $3.1M conflicts with CoinDesk's day-one $1.88M and could not be settled because the postmortem was blocked. One timeline citation (Alameda collapse sourced to a 2021 hack article) is mismatched. Most other claims were not checkable because primary sources returned 403; no later exploit or shutdown was found.
    anchoranchored
    chain
    ●mainnet-betaslot 462,049,095
    sig
    2B4vD3sTYV2g…iJsoYZfmexplorer ↗
    hash
    2gy2LsU19uef…oHNwnr6nsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1268 B) ▸
    {"actor":"reviewer","artifact_identity":"e76be5b8a0bde263008fb56f37ffd33b","blocked_count":2,"decided_at":"2026-10-27T11:11:59.561Z","decision":"review","disputed_pct":0.5,"findings_hash":"3zSLQRKjW1vaV7idsoicd3YLAyAz4ZGjJh54pgPiQ1uP","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":62,"page_content_hash":"1bcdcbefc7f0ced44c33b5690bed89defacbd6f0883c73d09842c31315bdc7c6","page_slug":"dodo-amm","prev_score":62,"reason":"The core exploit facts (March 2021, $3.8M, four named Crowdpools) check out against CoinDesk. The recovery figure of $3.1M conflicts with CoinDesk's day-one $1.88M and could not be settled because the postmortem was blocked. One timeline citation (Alameda collapse sourced to a 2021 hack article) is mismatched. Most other claims were not checkable because primary sources returned 403; no later exploit or shutdown was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":4,"sequence_num":5,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 783cf5d3-34ec-46eb-bb6c-848d0abcfb25
  6. #6review reviseby judgejudge
    2026-10-27 11:12:00Z
    Score: 62 → 51 (-11)
    Of six claims checked, two were blocked by the source and are left out of the count. Of the remaining four, one citation was disputed (claim_findings[4]: the November 2022 Alameda/FTX collapse is sourced to a 2021 article about the DODO hack) and one was unverifiable (claim_findings[5]: the 'no regulatory action' claim rests on a generic compliance blog). That gives a 50% disputed share, in the significant-issues band. The core exploit facts were confirmed by CoinDesk (claim_findings[0]), and the $3.1M recovery figure conflicts with CoinDesk's day-one figure but is unsettled (claim_findings[1]). The review found no omissions and no contradicting subject status. Because the reviewer's confidence is low (0.35) and the count rests on only four claims, the penalty is set at the mild end of the band.
    anchoranchored
    chain
    ●mainnet-betaslot 462,049,100
    sig
    3ahpUf5Joiik…UvSxjRFYexplorer ↗
    hash
    DoaPejwdqFP4…bBcHaTYcsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1592 B) ▸
    {"actor":"judge","artifact_identity":"e76be5b8a0bde263008fb56f37ffd33b","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T11:11:59.561Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"dodo-amm","prev_score":62,"reason":"Of six claims checked, two were blocked by the source and are left out of the count. Of the remaining four, one citation was disputed (claim_findings[4]: the November 2022 Alameda/FTX collapse is sourced to a 2021 article about the DODO hack) and one was unverifiable (claim_findings[5]: the 'no regulatory action' claim rests on a generic compliance blog). That gives a 50% disputed share, in the significant-issues band. The core exploit facts were confirmed by CoinDesk (claim_findings[0]), and the $3.1M recovery figure conflicts with CoinDesk's day-one figure but is unsettled (claim_findings[1]). The review found no omissions and no contradicting subject status. Because the reviewer's confidence is low (0.35) and the count rests on only four claims, the penalty is set at the mild end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-11,"score_limit":{"applied":-11,"limited":true,"proposed":-15,"rule":"limited_no_second_opinion","second":null},"scored_claims":4,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 91ae33cf-9666-4b5f-90cc-48594baf3630
  7. #7rescoreby systemsystem
    2026-11-01 12:37:08Z
    Score: 51 → 74 (+23)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 51 → 74. 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 −1.5; legitimacy credit long-running +10; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (+7) now shown as page reliability, not in the score.
    anchoranchored
    chain
    ●mainnet-betaslot 464,094,831
    sig
    3qqTaYB2fqM8…omgPNUUVexplorer ↗
    hash
    H8E5HxqoYdW9…xRbXW6rFsha256 → base58
    verifying row…full verify ↗
    canonical bytes (777 B) ▸
    {"actor":"system","decided_at":"2026-11-01T12:37:07.986Z","decision":"rescore","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","new_score":74,"page_slug":"dodo-amm","prev_score":51,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 51 → 74. 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 −1.5; legitimacy credit long-running +10; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (+7) now shown as page reliability, not in the score.","score_delta":23,"score_model":"v2","sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision b388daa7-0716-4b17-b2af-d39d2fe563ec
  8. #8rescoreby systemsystem
    2026-11-02 08:33:26Z
    Score: 74 → 73 (-1)
    Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 74 → 73. 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 −2.5; legitimacy credit long-running +10.
    anchoranchored
    chain
    ●mainnet-betaslot 464,429,648
    sig
    5s6ST3uybJ83…ZXZtpU21explorer ↗
    hash
    GT9qb8JZ3cZR…AFdDfWLGsha256 → base58
    verifying row…full verify ↗
    canonical bytes (706 B) ▸
    {"actor":"system","decided_at":"2026-11-02T08:33:25.211Z","decision":"rescore","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","new_score":73,"page_slug":"dodo-amm","prev_score":74,"reason":"Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 74 → 73. 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 −2.5; legitimacy credit long-running +10.","score_delta":-1,"score_model":"v2","sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 58c015e4-f04b-4c35-a1ce-f6f3287c4d9f
  9. #9reviewby reviewerreviewer
    2026-11-02 08:36:30Z
    Score: 73 → 73 (no score change)
    The core exploit narrative (date, amount, pools, mechanism, recovery figures and their conflict) matches CoinDesk, The Block and Halborn. The summary's 'roughly half recovered' is stated more firmly than the body, which correctly says sources conflict (about $1.88M vs about $3.1M). The partner-firm list is not found in fetched sources, and TVL and market figures could not be verified (DeFiLlama returned 403). No evidence of shutdown, sanction or newer exploit was found.
    anchoranchored
    chain
    ●mainnet-betaslot 464,430,525
    sig
    45jwCy9FYWuA…JcS2BiD6explorer ↗
    hash
    AMTfbtoRhGuM…nYwYMetBsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1319 B) ▸
    {"actor":"reviewer","artifact_identity":"9499a424087650f75a00ca9216fb7cf1","blocked_count":1,"decided_at":"2026-11-02T08:36:30.577Z","decision":"review","disputed_pct":0.25,"findings_hash":"HGP7nTmMDiay6Jd7Sx2y8P4TMeq8GnngBnzTMkHjj9iU","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":73,"page_content_hash":"2527fb2f8b42bba2c3b14b4572b805e0cfeb344b8ff8cc6e0ff5da4343bd182f","page_slug":"dodo-amm","prev_score":73,"reason":"The core exploit narrative (date, amount, pools, mechanism, recovery figures and their conflict) matches CoinDesk, The Block and Halborn. The summary's 'roughly half recovered' is stated more firmly than the body, which correctly says sources conflict (about $1.88M vs about $3.1M). The partner-firm list is not found in fetched sources, and TVL and market figures could not be verified (DeFiLlama returned 403). No evidence of shutdown, sanction or newer exploit was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":9,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 51e35c4b-e031-4969-887a-02a88a23aa19
  10. #10review reviseby judgejudge
    2026-11-02 08:36:30Z
    Score: 73 → 73 (no score change)
    The core exploit account (date, $3.8M amount, four pools, mechanism, and the conflicting recovery figures) was confirmed against CoinDesk, The Block and Halborn, and no shutdown, sanction or newer incident was found. Two of eight scored claims could not be verified: the list of partner firms DODO named (claim_findings[5]) and the Coinpaprika market figures (claim_findings[7]), which is about 25%. The summary also states that 'roughly half' of the funds were recovered more firmly than the body does, and the body itself says the figure is unsettled (claim_findings[0]). The DeFiLlama figures could not be checked because the site blocked the reviewer (1 of 9 claims, not scored), so the TVL numbers remain a coverage limit rather than a defect.
    anchoranchored
    chain
    ●mainnet-betaslot 464,430,530
    sig
    5TwA8EiCwZRM…9A5KkYEfexplorer ↗
    hash
    7Cnp27Uv3NCx…MV8A8ibhsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1425 B) ▸
    {"actor":"judge","artifact_identity":"9499a424087650f75a00ca9216fb7cf1","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T08:36:30.577Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":73,"page_slug":"dodo-amm","prev_score":73,"reason":"The core exploit account (date, $3.8M amount, four pools, mechanism, and the conflicting recovery figures) was confirmed against CoinDesk, The Block and Halborn, and no shutdown, sanction or newer incident was found. Two of eight scored claims could not be verified: the list of partner firms DODO named (claim_findings[5]) and the Coinpaprika market figures (claim_findings[7]), which is about 25%. The summary also states that 'roughly half' of the funds were recovered more firmly than the body does, and the body itself says the figure is unsettled (claim_findings[0]). The DeFiLlama figures could not be checked because the site blocked the reviewer (1 of 9 claims, not scored), so the TVL numbers remain a coverage limit rather than a defect.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 2d3bc345-8b8a-4fe7-a806-5e0e1bf9831a
  11. #11rescoreby systemsystem
    2026-11-02 08:36:31Z
    Score: 73 → 74 (+1)
    Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 74. 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 −1.7; legitimacy credit long-running +10; 1 section(s) set aside until a failed fact-check is resolved.
    anchoranchored
    chain
    ●mainnet-betaslot 464,430,535
    sig
    AM1Jioe6CyLx…zPz3MaRKexplorer ↗
    hash
    H8BEvDBA2SL9…J4rpkFrrsha256 → base58
    verifying row…full verify ↗
    canonical bytes (749 B) ▸
    {"actor":"system","decided_at":"2026-11-02T08:36:30.577Z","decision":"rescore","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","new_score":74,"page_slug":"dodo-amm","prev_score":73,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 74. 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 −1.7; legitimacy credit long-running +10; 1 section(s) set aside until a failed fact-check is resolved.","score_delta":1,"score_model":"v2","sequence_num":11,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 37e94322-605b-4fda-9e94-fd97f34438cf
  12. #12rescoreby systemsystem
    2026-11-17 21:27:29Z
    Score: 74 → 73 (-1)
    Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 74 → 73. 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 −2.5; legitimacy credit long-running +10.
    anchoranchored
    chain
    ●mainnet-betaslot 470,684,210
    sig
    28aV3mzZ2rfo…uncNyCBGexplorer ↗
    hash
    FYgFMzdd33Ag…rCHJPNDDsha256 → base58
    verifying row…full verify ↗
    canonical bytes (707 B) ▸
    {"actor":"system","decided_at":"2026-11-17T21:27:28.609Z","decision":"rescore","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","new_score":73,"page_slug":"dodo-amm","prev_score":74,"reason":"Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 74 → 73. 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 −2.5; legitimacy credit long-running +10.","score_delta":-1,"score_model":"v2","sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 7c2f676e-7e93-4aba-99f5-922e4b525efc
  13. #13reviewby reviewerreviewer
    2026-11-17 21:29:43Z
    Score: 73 → 73 (no score change)
    Core exploit facts (amount, pools, mechanism, dates) and both recovery figures match The Block and Halborn, and the page transparently flags the discrepancy between them. DeFiLlama and Coinpaprika market figures could not be read and are not scored. No current-status contradictions were found. The audit and regulatory sections are explicitly hedged absence-of-evidence statements.
    anchoranchored
    chain
    ●mainnet-betaslot 470,684,813
    sig
    4YBBqfndsJGT…2mqvjdWDexplorer ↗
    hash
    3xPMrUzGzrvH…fhj1vetSsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1225 B) ▸
    {"actor":"reviewer","artifact_identity":"37e117573c6702c9b3dc1ea0a9cb28fe","blocked_count":1,"decided_at":"2026-11-17T21:29:42.922Z","decision":"review","disputed_pct":0,"findings_hash":"2kJFjJJzkPvE4vqnHdLLYFbPfrvrQmXUDPb5DkFkiEdM","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":73,"page_content_hash":"f9c127164e21429e785964c155cdb92121d514137e6d4f469848b86ac8cbf7a4","page_slug":"dodo-amm","prev_score":73,"reason":"Core exploit facts (amount, pools, mechanism, dates) and both recovery figures match The Block and Halborn, and the page transparently flags the discrepancy between them. DeFiLlama and Coinpaprika market figures could not be read and are not scored. No current-status contradictions were found. The audit and regulatory sections are explicitly hedged absence-of-evidence statements.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"scored_claims":6,"sequence_num":13,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision b2ec7594-c7fa-4521-a07f-87673320ffd2
  14. #14review approveby judgejudge
    2026-11-17 21:29:43Z
    Score: 73 → 73 (no score change)
    Of 7 claim findings, 6 were confirmed against The Block and Halborn (exploit amount, affected pools, mechanism, dates, and both recovery figures) and none were disputed. One finding, claim_findings[5] on DeFiLlama TVL figures, could not be read because the source was blocked or too large, so it was excluded from the calculation; that is a coverage limit, not a defect of the page. The calculated disputed share is 0%. The review found no omissions and no contradiction of the page's status, and the open coverage gaps are low or medium priority.
    anchoranchored
    chain
    ●mainnet-betaslot 470,684,820
    sig
    YcGUBNaTqHtL…n5cef7Gmexplorer ↗
    hash
    7q58mBag1yyz…8fjfXAZksha256 → base58
    verifying row…full verify ↗
    canonical bytes (1222 B) ▸
    {"actor":"judge","artifact_identity":"37e117573c6702c9b3dc1ea0a9cb28fe","band_override":null,"blocked_count":1,"decided_at":"2026-11-17T21:29:42.922Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":73,"page_slug":"dodo-amm","prev_score":73,"reason":"Of 7 claim findings, 6 were confirmed against The Block and Halborn (exploit amount, affected pools, mechanism, dates, and both recovery figures) and none were disputed. One finding, claim_findings[5] on DeFiLlama TVL figures, could not be read because the source was blocked or too large, so it was excluded from the calculation; that is a coverage limit, not a defect of the page. The calculated disputed share is 0%. The review found no omissions and no contradiction of the page's status, and the open coverage gaps are low or medium priority.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"scored_claims":6,"sequence_num":14,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 37492be6-7567-472d-aa5c-95460900dce3
  15. #15rescoreby systemsystem
    2026-11-17 21:29:44Z
    Score: 73 → 74 (+1)
    Recalculated after the fact-check of 2026-11-17. Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 74. 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 −1.7; legitimacy credit long-running +10; 1 section(s) set aside until a failed fact-check is resolved.
    anchoranchored
    chain
    ●mainnet-betaslot 470,684,826
    sig
    2psbASPYaYEq…igCJp1GMexplorer ↗
    hash
    dkFt6BLhwQNE…rGs31qTDsha256 → base58
    verifying row…full verify ↗
    canonical bytes (749 B) ▸
    {"actor":"system","decided_at":"2026-11-17T21:29:42.922Z","decision":"rescore","investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","new_score":74,"page_slug":"dodo-amm","prev_score":73,"reason":"Recalculated after the fact-check of 2026-11-17. Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 74. 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 −1.7; legitimacy credit long-running +10; 1 section(s) set aside until a failed fact-check is resolved.","score_delta":1,"score_model":"v2","sequence_num":15,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 7242ac09-72ba-4f15-ba9f-297d5c45fd6f
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.