Skip to main content
AVOID.NET
← Cover Protocol5 decisions on this page

Audit log

Every state-changing event for Cover Protocol: 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-27 18:53:44Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 422,560,462
    sig
    4SHyYF8QpyVb…3FsCPANZexplorer ↗
    hash
    eWHXkUV8foBU…DsBRmC2Ksha256 → base58
    verifying row…full verify ↗
    canonical bytes (6310 B) ▸
    {"actor":"system:backfill","investigation_id":"2ba645fa-983a-424d-9e08-af9a7185f56f","kind":"publish","page_slug":"cover-protocol","published_at":"2026-05-27T18:53:44.008Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Cover Protocol","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://iq.wiki/wiki/cover-protocol","type":"other","url":""},{"credibility":3,"name":"https://www.tronweekly.com/cover-stealthy-rug/","type":"other","url":""},{"credibility":3,"name":"https://bitcoinexchangeguide.com/safe-token-pumping-hard-after-getting-revived-as-cover-protocol/","type":"other","url":""},{"credibility":3,"name":"https://coverprotocol.medium.com/cover-protocol-e202808aa4ef","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://mudit.blog/cover-protocol-hack-analysis-tokens-minted-exploit/","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/cover-protocol-suffers-infinite-minting-attack-price-tanks-97","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/markets/2020/12/28/cover-protocol-attack-perpetrated-by-white-hat-funds-returned-hacker-claims","type":"other","url":""},{"credibility":3,"name":"https://cryptobriefing.com/defi-developers-claim-cover-protocol-hack-return-funds/","type":"other","url":""},{"credibility":3,"name":"https://slowmist.medium.com/a-brief-analysis-of-the-cover-protocol-hacked-event-700d747b309c","type":"other","url":""},{"credibility":3,"name":"https://www.financemagnates.com/cryptocurrency/news/binance-halts-trading-of-hacked-defi-project-cover-protocol-token-crashes/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/markets/2021/03/05/defi-divorce-yearn-cancels-tie-up-with-cover-protocol","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/better-as-friends-defi-protocols-yearn-and-cover-announce-cessation-of-merger","type":"other","url":""},{"credibility":3,"name":"https://ambcrypto.com/yearn-finance-cover-protocol-announce-termination-of-merger-process/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/business/2021/09/05/defi-projects-cover-ruler-are-shutting-down-after-development-team-exits","type":"other","url":""},{"credibility":3,"name":"https://decrypt.co/80262/defi-insurance-protocol-cover-shuts-down-token-value-plummets","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/academy/article/why-is-binance-delisting-cover-the-end-of-cover-protocol","type":"other","url":""},{"credibility":3,"name":"https://cryptodaily.co.uk/2021/09/cover-protocol-delisting-saga","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://iq.wiki/wiki/cover-protocol","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://mudit.blog/cover-protocol-hack-analysis-tokens-minted-exploit/","type":"other","url":""},{"credibility":3,"name":"https://www.tronweekly.com/cover-stealthy-rug/","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/business/2021/09/05/defi-projects-cover-ruler-are-shutting-down-after-development-team-exits","type":"other","url":""},{"credibility":3,"name":"https://decrypt.co/80262/defi-insurance-protocol-cover-shuts-down-token-value-plummets","type":"other","url":""}]}],"sources_used":[],"summary":"Cover Protocol was a decentralized insurance marketplace on Ethereum, launched in November 2020 after a troubled rebrand from the failed SAFE token project. On December 28, 2020, a critical smart contract vulnerability in its Blacksmith farming contract allowed an attacker to mint approximately 40 quintillion COVER tokens and extract over $4 million in assets, crashing the token price by more than 97%. After a failed merger with Yearn Finance and the abrupt departure of core developers, the protocol permanently shut down on September 5, 2021, distributing remaining treasury funds to token holders.","timeline":[{"date":"2020-09-01","event":"SAFE token launches; immediate controversy erupts over founder Alan's handling of liquidity mining deployment, causing SAFE to crash over 90% from ~$4,000 to under $200.","source":""},{"date":"2020-09-26","event":"SAFE-to-SAFE2 token migration begins (1:1 conversion). Co-founder Azeem Ahmed departs the project.","source":""},{"date":"2020-10-18","event":"Podcast founder Jason Choi publicly labels the SAFE/COVER token structure a 'stealthy rug,' citing 5.8x dilution of early supporters and reallocation of 70% of new supply to a new yield farm.","source":""},{"date":"2020-11-20","event":"SAFE2-to-COVER migration begins. Cover Protocol officially launches on Ethereum mainnet.","source":""},{"date":"2020-11-28","event":"Cover Protocol announces merger with Yearn Finance; Cover to serve as coverage backstop for the Yearn product suite.","source":""},{"date":"2020-12-28","event":"Infinite mint exploit on Blacksmith.sol farming contract. Attacker mints approximately 40 quintillion COVER tokens and extracts ~$4.4 million (1,400 ETH, 1M DAI, 90 WBTC, 3K LINK). COVER token crashes 97%. Binance halts trading. Grap.Finance later claims white hat responsibility and returns extracted funds.","source":""},{"date":"2021-01-01","event":"Cover Protocol team distributes new COVER tokens to holders affected by the December 2020 exploit.","source":""},{"date":"2021-03-05","event":"Yearn Finance and Cover Protocol announce termination of merger. COVER drops ~28% immediately. DeFi Ted states he received approximately four hours' notice before the public announcement.","source":""},{"date":"2021-09-05","event":"Cover Protocol and Ruler Protocol permanently shut down after core development team abruptly abandons both projects without stated reason. DeFi Ted advises users to withdraw all funds immediately. Treasury distributed to token holders at block 13162680 snapshot.","source":""},{"date":"2021-09-05","event":"Binance announces delisting of COVER token following shutdown announcement.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 27fee234-4190-4f40-ac62-f5818698ca6f
  2. #2rescoreby systemsystem
    2026-10-10 18:40:03Z
    Score: 18 → 36 (+18)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 36. Problems weighed by who is responsible: the subject's own conduct −24, incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +2.
    anchoranchored
    chain
    ●mainnet-betaslot 455,358,248
    sig
    2eyF9MGKhuax…fN1oSkTEexplorer ↗
    hash
    9hmZMLSeNj9R…jJivqSTnsha256 → base58
    verifying row…full verify ↗
    canonical bytes (676 B) ▸
    {"actor":"system","decided_at":"2026-10-10T18:40:03.853Z","decision":"rescore","investigation_id":"2ba645fa-983a-424d-9e08-af9a7185f56f","new_score":36,"page_slug":"cover-protocol","prev_score":18,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 36. Problems weighed by who is responsible: the subject's own conduct −24, incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +2.","score_delta":18,"score_model":"v2","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 36a623bc-b5e7-4cf6-9534-58a1eb52a3d3
  3. #3reviewby reviewerreviewer
    2026-11-01 23:36:56Z
    Score: 36 → 36 (no score change)
    The core narrative holds: the December 2020 Blacksmith exploit, the 40 quintillion mint, the ~$4.4M cash-out, the Yearn split and the September 2021 shutdown with the block 13162680 snapshot are all supported. Weaker points are the 'returned the extracted funds' wording (CoinDesk reports a partial return), the unsourced 1inch detail, the SAFE price figures, the unverified Binance delisting date, and the uncited ZachXBT claim. The page correctly shows the entity as shut down.
    anchoranchored
    chain
    ●mainnet-betaslot 464,279,369
    sig
    2BgHQjKeDs5p…nQrfXD7Aexplorer ↗
    hash
    CLY6VsY4LjH4…nVMecvbWsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1366 B) ▸
    {"actor":"reviewer","artifact_identity":"341b5f5ec57634bc5c9dfea5d3f259d1","blocked_count":1,"decided_at":"2026-11-01T23:36:56.911Z","decision":"review","disputed_pct":0.4,"findings_hash":"wbmfSWwjqNbdfY2JdhYczegiuiax5GTRLKNR4bCxu9N","investigation_id":"2ba645fa-983a-424d-9e08-af9a7185f56f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":36,"omissions":{"material":0,"total":1},"page_content_hash":"9f7314d7a85a3d2eb22bc22ad76e5c16b172b634ab128006cbf0468ac5fd2f32","page_slug":"cover-protocol","prev_score":36,"reason":"The core narrative holds: the December 2020 Blacksmith exploit, the 40 quintillion mint, the ~$4.4M cash-out, the Yearn split and the September 2021 shutdown with the block 13162680 snapshot are all supported. Weaker points are the 'returned the extracted funds' wording (CoinDesk reports a partial return), the unsourced 1inch detail, the SAFE price figures, the unverified Binance delisting date, and the uncited ZachXBT claim. The page correctly shows the entity as shut down.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"subject_status":"shut_down","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 a54d48ef-69b4-45cd-ad13-334428d6111f
  4. #4review reviseby judgejudge
    2026-11-01 23:36:57Z
    Score: 36 → 36 (no score change)
    Of 11 claims checked, one was set aside because its source refused the reviewer, and 4 of the remaining 10 (40%) could not be verified: the 1inch cash-out detail (claim_findings[1]), the SAFE price figures (claim_findings[4]), the January 2021 token reissue (claim_findings[8]) and the uncited statement that ZachXBT flagged the entity (claim_findings[10]). None was contradicted, and the core account holds: the December 2020 exploit, the 40 quintillion mint, the Yearn split and the September 2021 shutdown are supported. Wording that overstates its sources also needs correcting: 'returned the extracted funds' (claim_findings[2]), where CoinDesk reports a partial return, and the unconfirmed Binance delisting date (claim_findings[7]). Because the unverified items are mostly unfetched sources rather than refuted claims, the penalty sits at the low end of the significant band.
    anchoranchored
    chain
    ●mainnet-betaslot 464,279,374
    sig
    5mLx4xBXAki5…JUoTLBguexplorer ↗
    hash
    BNGpifyDyic1…Lw47CBHfsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1564 B) ▸
    {"actor":"judge","artifact_identity":"341b5f5ec57634bc5c9dfea5d3f259d1","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T23:36:56.911Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"2ba645fa-983a-424d-9e08-af9a7185f56f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":36,"page_slug":"cover-protocol","prev_score":36,"reason":"Of 11 claims checked, one was set aside because its source refused the reviewer, and 4 of the remaining 10 (40%) could not be verified: the 1inch cash-out detail (claim_findings[1]), the SAFE price figures (claim_findings[4]), the January 2021 token reissue (claim_findings[8]) and the uncited statement that ZachXBT flagged the entity (claim_findings[10]). None was contradicted, and the core account holds: the December 2020 exploit, the 40 quintillion mint, the Yearn split and the September 2021 shutdown are supported. Wording that overstates its sources also needs correcting: 'returned the extracted funds' (claim_findings[2]), where CoinDesk reports a partial return, and the unconfirmed Binance delisting date (claim_findings[7]). Because the unverified items are mostly unfetched sources rather than refuted claims, the penalty sits at the low end of the significant band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"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 64bb3389-08c9-4297-8e4e-2ad85296c86d
  5. #5rescoreby systemsystem
    2026-11-01 23:36:58Z
    Score: 36 → 47 (+11)
    Recalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 36 → 47. Problems weighed by who is responsible: the subject's own conduct −16, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +2; 2 section(s) set aside until a failed fact-check is resolved.
    anchoranchored
    chain
    ●mainnet-betaslot 464,279,384
    sig
    3Z6Lg5VkWoEE…p2uJ3Zc1explorer ↗
    hash
    ATGK8Proe2fj…6eHLBWKwsha256 → base58
    verifying row…full verify ↗
    canonical bytes (753 B) ▸
    {"actor":"system","decided_at":"2026-11-01T23:36:56.911Z","decision":"rescore","investigation_id":"2ba645fa-983a-424d-9e08-af9a7185f56f","new_score":47,"page_slug":"cover-protocol","prev_score":36,"reason":"Recalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 36 → 47. Problems weighed by who is responsible: the subject's own conduct −16, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +2; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":11,"score_model":"v2","sequence_num":5,"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 83d0cb94-cd01-4944-99b4-0c702938dfe9
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>.