Skip to main content
AVOID.NET

Audit log

Every state-changing event for DoinGud NFT Diamond Bidding Contract Exploit: 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. #1reviewby reviewerreviewer
    2026-10-27 10:58:33Z
    Score: 42 → 42 (no score change)
    Background claims (May 2021 announcement, Polygon, 5% to social causes, Alameda as a backer, January 2024 Cleo acquisition via Dealroom) hold. The funding total, most named investors and the Zug location are not in the cited press release, which is datelined Steinhausen. The headline exploit could not be verified because the sole source returned 402 and searches found nothing. The page presents it as an unverified allegation, which is accurate.
    anchoranchored
    chain
    ●mainnet-betaslot 462,045,268
    sig
    43hfqcsSTYyb…CQu7ewoXexplorer ↗
    hash
    EAaUhp5NHawX…ymPxUH68sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1327 B) ▸
    {"actor":"reviewer","artifact_identity":"4a31def647819ae75d03683285fbe3d4","blocked_count":1,"decided_at":"2026-10-27T10:58:33.656Z","decision":"review","disputed_pct":0.25,"findings_hash":"H3UtEct3VhmwhhZXNfhKSgVBbbJ6MS8gr1g8oNTBhtFb","investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":42,"page_content_hash":"81acb46bbeba05836518708534861e556aa12c2e33140d8fb6b6178d4ae0af2c","page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":42,"reason":"Background claims (May 2021 announcement, Polygon, 5% to social causes, Alameda as a backer, January 2024 Cleo acquisition via Dealroom) hold. The funding total, most named investors and the Zug location are not in the cited press release, which is datelined Steinhausen. The headline exploit could not be verified because the sole source returned 402 and searches found nothing. The page presents it as an unverified allegation, which is accurate.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":4,"sequence_num":1,"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 43e757ca-3448-4dfc-9f82-2548619b44bd
  2. #2review reviseby judgejudge
    2026-10-27 10:58:33Z
    Score: 42 → 34 (-8)
    Of 5 claims reviewed, 1 was blocked by the source (claim_findings[3], the exploit post returned HTTP 402) and is excluded from the percentage; of the remaining 4, 1 could not be verified (claim_findings[4], the dormancy claim has no cited source), giving 25%. The funding total, most named investors and the Zug location are not in the cited press release (claim_findings[1]), and the Cleo acquisition rests on aggregator data only (claim_findings[2]), though the page already hedges it. The exploit is presented as an unverified allegation, which matches the reviewer's findings, and no omissions or contradicting subject status were found. A high-priority gap remains: no on-chain transaction or primary source for the central exploit claim. Reviewer confidence is moderate (0.5), so the penalty is set in the lower part of the minor band.
    anchoranchored
    chain
    ●mainnet-betaslot 462,045,274
    sig
    4VvCMGiRx8PN…i4s3N25Qexplorer ↗
    hash
    64jbocvG26sJ…TQNg8XJnsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1554 B) ▸
    {"actor":"judge","artifact_identity":"4a31def647819ae75d03683285fbe3d4","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T10:58:33.656Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":42,"reason":"Of 5 claims reviewed, 1 was blocked by the source (claim_findings[3], the exploit post returned HTTP 402) and is excluded from the percentage; of the remaining 4, 1 could not be verified (claim_findings[4], the dormancy claim has no cited source), giving 25%. The funding total, most named investors and the Zug location are not in the cited press release (claim_findings[1]), and the Cleo acquisition rests on aggregator data only (claim_findings[2]), though the page already hedges it. The exploit is presented as an unverified allegation, which matches the reviewer's findings, and no omissions or contradicting subject status were found. A high-priority gap remains: no on-chain transaction or primary source for the central exploit claim. Reviewer confidence is moderate (0.5), so the penalty is set in the lower part of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":4,"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 a0e7ac6e-29e1-434d-87d9-ccbd7cf56328
  3. #3reviewby reviewerreviewer
    2026-11-03 05:54:57Z
    Score: 34 → 34 (no score change)
    The page is heavily hedged and its central exploit allegation is correctly flagged as unverified; my search found no corroboration either. The Newswire dateline and funding description check out. The founder attribution and the 5%-95% share range are not supported by the cited Newswire release. The Dealroom acquisition claim and the aggregator data could not be read. The page's central subject (the exploit) is unestablished, which is a structural weakness.
    anchoranchored
    chain
    ●mainnet-betaslot 464,788,580
    sig
    2AiD7Bdn8ASP…JWuoXc6cexplorer ↗
    hash
    DXVjAhDe3gtt…tJhXRLXmsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1339 B) ▸
    {"actor":"reviewer","artifact_identity":"96270391a5312c4094af8fb0b7adbc17","blocked_count":1,"decided_at":"2026-11-03T05:54:57.707Z","decision":"review","disputed_pct":0.25,"findings_hash":"ALhoGMCjD7DsC5uGJd6KPB3Rijn5RGL5rHtmKKegEV6F","investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"page_content_hash":"e3ff0625261c76e16e64bc1fc68666d333ed1b3eb0ed1fb622aee9450d84f2d7","page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":34,"reason":"The page is heavily hedged and its central exploit allegation is correctly flagged as unverified; my search found no corroboration either. The Newswire dateline and funding description check out. The founder attribution and the 5%-95% share range are not supported by the cited Newswire release. The Dealroom acquisition claim and the aggregator data could not be read. The page's central subject (the exploit) is unestablished, which is a structural weakness.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":4,"sequence_num":3,"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 9209d0fa-2242-41d5-819b-8382be2ba8b7
  4. #4review reviseby judgejudge
    2026-11-03 05:54:57Z
    Score: 34 → 32 (-2)
    Of five claims checked, one could not be read because the source blocked the reviewer and was left out of the count. Of the remaining four, none were disputed and one (claim_findings[1], the founder names and 5%-95% share range) could not be supported by the cited Newswire release, giving 25% unverified. The page's central exploit allegation is framed as unverified, which matches the reviewer's own search (claim_findings[2]), but the page is titled as an exploit with no primary source, a high-priority coverage gap. A modest penalty is applied, softened by the reviewer's moderate confidence.
    anchoranchored
    chain
    ●mainnet-betaslot 464,788,586
    sig
    3xWyWWVUedjt…HSgfzs5texplorer ↗
    hash
    FpT2W2qRnTLw…CZPsH65Ssha256 → base58
    verifying row…full verify ↗
    canonical bytes (1376 B) ▸
    {"actor":"judge","artifact_identity":"96270391a5312c4094af8fb0b7adbc17","band_override":null,"blocked_count":1,"decided_at":"2026-11-03T05:54:57.707Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":32,"page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":34,"reason":"Of five claims checked, one could not be read because the source blocked the reviewer and was left out of the count. Of the remaining four, none were disputed and one (claim_findings[1], the founder names and 5%-95% share range) could not be supported by the cited Newswire release, giving 25% unverified. The page's central exploit allegation is framed as unverified, which matches the reviewer's own search (claim_findings[2]), but the page is titled as an exploit with no primary source, a high-priority coverage gap. A modest penalty is applied, softened by the reviewer's moderate confidence.","replaces_fact_checks":{"score_before_fact_checks":42,"undone":1},"reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-2,"scored_claims":4,"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 b6f9f3ae-a0f2-4b75-a06e-e5146ec6269a
  5. #5reviewby reviewerreviewer
    2026-11-04 05:53:20Z
    Score: 32 → 32 (no score change)
    The core exploit claim matches the SlowMist entry in amount, mechanism and chain, and the page hedges it appropriately as alleged. The page misses that SlowMist gives an exact date of 2026-09-21 and an X reference. The seed round amount is confirmed, but the cited Crypto Daily article names only some of the listed backers, and the Switzerland claim has no located source. Founder attributions were not checked.
    anchoranchored
    chain
    ●mainnet-betaslot 465,191,391
    sig
    aJuU6Mfoy26h…FgJQehu9explorer ↗
    hash
    2jLDUYqpoGcv…bQEYWzW5sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1254 B) ▸
    {"actor":"reviewer","artifact_identity":"af7739fbc8eeec3512739f14ac27be2f","decided_at":"2026-11-04T05:53:20.777Z","decision":"review","disputed_pct":0.2,"findings_hash":"4oeWWCoHmfMGF2PHUDuTK5sLaBJfBfHHW8gfrFYWLQWh","investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":32,"page_content_hash":"f0c039377767f5734aee995e027a19ccf82e8bdfef0732047ce25311e90b1c30","page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":32,"reason":"The core exploit claim matches the SlowMist entry in amount, mechanism and chain, and the page hedges it appropriately as alleged. The page misses that SlowMist gives an exact date of 2026-09-21 and an X reference. The seed round amount is confirmed, but the cited Crypto Daily article names only some of the listed backers, and the Switzerland claim has no located source. Founder attributions were not checked.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"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 5b6ef450-cbd2-486a-a6b0-0451c96dce96
  6. #6review reviseby judgejudge
    2026-11-04 05:53:21Z
    Score: 32 → 34 (+2)
    The core exploit claim (claim_findings[0]) matches the SlowMist entry in amount, mechanism and chain, and the page labels it as alleged. One of six claims could not be verified (claim_findings[4], the Switzerland base has no located source), which gives a 17% unverified rate. The cited Crypto Daily article supports only some of the named seed backers (claim_findings[2] and [3]), and the page omits the exact date (2026-09-21) and X post reference that SlowMist gives (claim_findings[1]). A high-priority coverage gap on primary incident evidence, plus unchecked founder attributions, moves this to a minor revision rather than approval.
    anchoranchored
    chain
    ●mainnet-betaslot 465,191,397
    sig
    3Jgek3CDYM3F…3TViXzpeexplorer ↗
    hash
    E5JZGKHQDisK…rsrxrXzHsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1380 B) ▸
    {"actor":"judge","artifact_identity":"af7739fbc8eeec3512739f14ac27be2f","band_override":null,"decided_at":"2026-11-04T05:53:20.777Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":34,"page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":32,"reason":"The core exploit claim (claim_findings[0]) matches the SlowMist entry in amount, mechanism and chain, and the page labels it as alleged. One of six claims could not be verified (claim_findings[4], the Switzerland base has no located source), which gives a 17% unverified rate. The cited Crypto Daily article supports only some of the named seed backers (claim_findings[2] and [3]), and the page omits the exact date (2026-09-21) and X post reference that SlowMist gives (claim_findings[1]). A high-priority coverage gap on primary incident evidence, plus unchecked founder attributions, moves this to a minor revision rather than approval.","replaces_fact_checks":{"score_before_fact_checks":42,"undone":2},"reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":2,"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 26610662-0f22-4857-a93d-e956fcdc9665
  7. #7reviewby reviewerreviewer
    2026-11-17 21:06:36Z
    Score: 34 → 34 (no score change)
    Claims match the cited sources: the SlowMist entry, Newswire release and Crypto Daily seed round all check out, and the page hedges the single-source exploit appropriately. One claim (Crunchbase listing) was blocked and not scored; the founder's expanded full name was not verified from the cited profile. No contradictions or critical omissions found.
    anchoranchored
    chain
    ●mainnet-betaslot 470,678,295
    sig
    4rRBPfom9ENJ…FYeHoeHXexplorer ↗
    hash
    2u3BdQFXbGrv…hiToLfnDsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1230 B) ▸
    {"actor":"reviewer","artifact_identity":"ac00ecf7c7875b17d708465a8342ccf4","blocked_count":1,"decided_at":"2026-11-17T21:06:36.099Z","decision":"review","disputed_pct":0,"findings_hash":"FV2F1DV1MJJJjhFZXSqkvdXDC3B8h4BHZvrgB2D1LvXe","investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":34,"page_content_hash":"94e774be89e1edbde7aa1572958470db275f61ff005073b09e7e7a94fd63c76b","page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":34,"reason":"Claims match the cited sources: the SlowMist entry, Newswire release and Crypto Daily seed round all check out, and the page hedges the single-source exploit appropriately. One claim (Crunchbase listing) was blocked and not scored; the founder's expanded full name was not verified from the cited profile. No contradictions or critical omissions found.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"scored_claims":5,"sequence_num":7,"subject_status":"exploited","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 106283ed-4f57-4ee7-9bae-efe8ed2fc697
  8. #8review approveby judgejudge
    2026-11-17 21:06:36Z
    Score: 34 → 42 (+8)
    Of the six claims checked, five were confirmed or supported by their cited sources and one (claim_findings[3], the Crunchbase listing) could not be read because the source blocked the reviewer; that claim is left out of the percentage, which comes to 0% disputed. claim_findings[4] was only partly supported (the founder role is confirmed but the expanded full name was not seen on the cited profile), a minor point. The review found no omissions and no conflict between the page and the subject's status, and the page already labels the September 2026 exploit as alleged and single-sourced. The open high-priority gap (on-chain verification of the exploit) is a suggestion for expanding the page, not a defect in what it currently says.
    anchoranchored
    chain
    ●mainnet-betaslot 470,678,448
    sig
    51UB4ER7Jdus…FmmieaaQexplorer ↗
    hash
    sSBpEibWKcBV…Farrsurtsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1513 B) ▸
    {"actor":"judge","artifact_identity":"ac00ecf7c7875b17d708465a8342ccf4","band_override":null,"blocked_count":1,"decided_at":"2026-11-17T21:06:36.099Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":42,"page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":34,"reason":"Of the six claims checked, five were confirmed or supported by their cited sources and one (claim_findings[3], the Crunchbase listing) could not be read because the source blocked the reviewer; that claim is left out of the percentage, which comes to 0% disputed. claim_findings[4] was only partly supported (the founder role is confirmed but the expanded full name was not seen on the cited profile), a minor point. The review found no omissions and no conflict between the page and the subject's status, and the page already labels the September 2026 exploit as alleged and single-sourced. The open high-priority gap (on-chain verification of the exploit) is a suggestion for expanding the page, not a defect in what it currently says.","replaces_fact_checks":{"score_before_fact_checks":42,"undone":3},"reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":8,"scored_claims":5,"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 a49c5225-9d2c-45cd-b2f0-d51fe068dfc3
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>.