← Deguard8 decisions on this page
Audit log
Every state-changing event for Deguard: 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.
- #1reviewby reviewerreviewer2026-11-01 13:54:28ZScore: 60 → 60 (no score change)The factual claims about the ETH Zurich DeGuard tool and its CCS 2016 paper match the project page. DegenGuard is confirmed. Degns allegations are accurately hedged, though uncited. The Degis description is uncited and unchecked. The Twente thesis could not be read. No crypto entity, shutdown or sanction was found, so the page's negative findings look reasonable.anchoranchored
- chain
- ●mainnet-betaslot 464,116,322
- sig
5XhhRg4wJCGs…B8dYBZSeexplorer ↗- hash
9uhsd6onU1en…kM5UZSQRsha256 → base58
verifying row…full verify ↗canonical bytes (1209 B) ▸
{"actor":"reviewer","artifact_identity":"01dcb54c411e14473e4d8e357eb09d7b","blocked_count":1,"decided_at":"2026-11-01T13:54:28.843Z","decision":"review","disputed_pct":0.1667,"findings_hash":"5av35ZN1g76M8PA9YxGUb1V1bco3MS7G3pw2pyc8Au3z","investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_content_hash":"78df10ae87ccd0cc855187e0ea9c6beb9bcac45e829a8c09d52231cc75723e9f","page_slug":"deguard","prev_score":60,"reason":"The factual claims about the ETH Zurich DeGuard tool and its CCS 2016 paper match the project page. DegenGuard is confirmed. Degns allegations are accurately hedged, though uncited. The Degis description is uncited and unchecked. The Twente thesis could not be read. No crypto entity, shutdown or sanction was found, so the page's negative findings look reasonable.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"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 c65e60a2-993b-4184-8bde-d11ac18b7a5d - #2review reviseby judgejudge2026-11-01 13:54:29ZScore: 60 → 55 (-5)Of 7 claim findings, 1 was excluded because the source blocked the reviewer (claim_findings[5], the Twente thesis), leaving 6. None were disputed and 1 was unverifiable (claim_findings[4], the uncited Degis description), giving 16.7%, which falls in the minor band. The core claims about the ETH Zurich DeGuard tool, the CCS 2016 paper and DegenGuard were confirmed (claim_findings[0-2]) and the Degns allegation is accurately hedged. The penalty sits at the low end because the only gap is a low-stakes uncited aside and the review found no omissions and no contrary subject status.anchoranchored
- chain
- ●mainnet-betaslot 464,116,327
- sig
3X5RLQVBVzXT…PXkzRsQRexplorer ↗- hash
HBEdGwG8fKUh…Sq6uGNSZsha256 → base58
verifying row…full verify ↗canonical bytes (1261 B) ▸
{"actor":"judge","artifact_identity":"01dcb54c411e14473e4d8e357eb09d7b","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T13:54:28.843Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_slug":"deguard","prev_score":60,"reason":"Of 7 claim findings, 1 was excluded because the source blocked the reviewer (claim_findings[5], the Twente thesis), leaving 6. None were disputed and 1 was unverifiable (claim_findings[4], the uncited Degis description), giving 16.7%, which falls in the minor band. The core claims about the ETH Zurich DeGuard tool, the CCS 2016 paper and DegenGuard were confirmed (claim_findings[0-2]) and the Degns allegation is accurately hedged. The penalty sits at the low end because the only gap is a low-stakes uncited aside and the review found no omissions and no contrary subject status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":6,"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 3e21afb2-9254-4aae-a2b4-fcc702fc1883 - #3reviewby reviewerreviewer2026-11-01 21:35:34ZScore: 55 → 55 (no score change)The checked claims (IQ.wiki profile details, anonymous team, Unmarshal partnership date, DappBay Red Alarm wording, Degis/CertiK) match their sources, and the page is appropriately hedged about the Red Alarm flag. The Cyberscope figures and Venom Quests promotion could not be read because of 403/429 responses. No shutdown, exploit or sanction was found, but current operation remains unconfirmed.anchoranchored
- chain
- ●mainnet-betaslot 464,245,391
- sig
vUMopHNz7aoq…Xc1HfTpFexplorer ↗- hash
5Li5mHoLagVk…g99G6vhFsha256 → base58
verifying row…full verify ↗canonical bytes (1241 B) ▸
{"actor":"reviewer","artifact_identity":"bd6dc340ce75f40d0f1461f28fd7610b","blocked_count":2,"decided_at":"2026-11-01T21:35:34.075Z","decision":"review","disputed_pct":0.1429,"findings_hash":"J5w6g3ExV1Kaf4mh8iZYgxixwUMdDUiY8taHw4qFHRg","investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_content_hash":"673cb11f969254c9e93791f26b557e34487b83a64f98d53d782c730d0ef4fde4","page_slug":"deguard","prev_score":55,"reason":"The checked claims (IQ.wiki profile details, anonymous team, Unmarshal partnership date, DappBay Red Alarm wording, Degis/CertiK) match their sources, and the page is appropriately hedged about the Red Alarm flag. The Cyberscope figures and Venom Quests promotion could not be read because of 403/429 responses. No shutdown, exploit or sanction was found, but current operation remains unconfirmed.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"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 7d91e21a-1147-4a96-b622-b5a938af7b9b - #4review reviseby judgejudge2026-11-01 21:35:34ZScore: 55 → 51 (-4)None of the nine claims checked was disputed. Five were confirmed, one was partially supported (claim_findings[3], where the 'wallet-related privacy tooling' wording is looser than the source), and three could not be verified. Two of those three (claim_findings[4] and [6]) were blocked by the source (403 and 429), so they are left out of the percentage and reflect a coverage limit, not a defect. The remaining unverifiable claim (claim_findings[8], the 2016 academic paper) was not checked, which puts the adjusted rate at 1 of 7, or about 14%, in the minor band. The review found no shutdown or material omission, but it left two high-priority coverage gaps open: on-chain analysis of the DGN token and current operating status, which DappBay's 'Inaccessible Website' flag makes relevant. Given the reviewer's moderate confidence, the penalty is set at the low end of the band.anchoranchored
- chain
- ●mainnet-betaslot 464,245,396
- sig
63BAz1d8iyuP…HPyuWv6nexplorer ↗- hash
GjSgjiPQufSY…XFvuPaeFsha256 → base58
verifying row…full verify ↗canonical bytes (1666 B) ▸
{"actor":"judge","artifact_identity":"bd6dc340ce75f40d0f1461f28fd7610b","band_override":null,"blocked_count":2,"decided_at":"2026-11-01T21:35:34.075Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"deguard","prev_score":55,"reason":"None of the nine claims checked was disputed. Five were confirmed, one was partially supported (claim_findings[3], where the 'wallet-related privacy tooling' wording is looser than the source), and three could not be verified. Two of those three (claim_findings[4] and [6]) were blocked by the source (403 and 429), so they are left out of the percentage and reflect a coverage limit, not a defect. The remaining unverifiable claim (claim_findings[8], the 2016 academic paper) was not checked, which puts the adjusted rate at 1 of 7, or about 14%, in the minor band. The review found no shutdown or material omission, but it left two high-priority coverage gaps open: on-chain analysis of the DGN token and current operating status, which DappBay's 'Inaccessible Website' flag makes relevant. Given the reviewer's moderate confidence, the penalty is set at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-4,"score_limit":{"applied":-4,"limited":true,"proposed":-5,"rule":"limited_no_second_opinion","second":null},"scored_claims":7,"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 bbdc77bb-0004-41de-b358-fe28cec93af6 - #5reviewby reviewerreviewer2026-11-03 05:56:58ZScore: 51 → 51 (no score change)The page is heavily hedged and most checked claims hold: the anonymous team, unnamed audit and iOS inconsistency on iq.wiki, the DappBay Red Alarm label, and the 404 on deguard.io. One wording error: 'does not resolve' contradicts a 404, which means the server responded. The 'Inaccessible Website' flag was not seen on the DappBay detail page, which even offers a visit link. The Cyberscope, Venom and academic claims could not be read (source blocked) and are not scored. No shutdown, exploit or sanction found.anchoranchored
- chain
- ●mainnet-betaslot 464,789,208
- sig
iYsLdKRSbXmj…AhjpUK3eexplorer ↗- hash
4B8jmmiwLK4y…wG2ruc6jsha256 → base58
verifying row…full verify ↗canonical bytes (1357 B) ▸
{"actor":"reviewer","artifact_identity":"6dfd6efc577cd082e6c17a32741ce754","blocked_count":3,"decided_at":"2026-11-03T05:56:58.357Z","decision":"review","disputed_pct":0.1429,"findings_hash":"8digqhRxkA3u4SewWuJiXCNWQfS6gQ7wUgsFUGPRp9z2","investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_content_hash":"25603df5ca1711599fa9647c6097f228a3503845c42becad55065daa7c4f0dca","page_slug":"deguard","prev_score":51,"reason":"The page is heavily hedged and most checked claims hold: the anonymous team, unnamed audit and iOS inconsistency on iq.wiki, the DappBay Red Alarm label, and the 404 on deguard.io. One wording error: 'does not resolve' contradicts a 404, which means the server responded. The 'Inaccessible Website' flag was not seen on the DappBay detail page, which even offers a visit link. The Cyberscope, Venom and academic claims could not be read (source blocked) and are not scored. No shutdown, exploit or sanction found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"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 040b25ab-ffe0-412b-a7db-3387ad9ed5c1 - #6review reviseby judgejudge2026-11-03 05:56:58ZScore: 51 → 52 (+1)Of 10 claims checked, 3 could not be read because the sources blocked the reviewer and are excluded; 1 of the remaining 7 (about 14%) could not be verified. The 'Inaccessible Website' flag on DappBay (claim_findings[2]) was not found on the detail page, and the page wrongly says deguard.io 'does not resolve' when it returns an HTTP 404 (claim_findings[3]). The core findings hold: the anonymous team, the DappBay Red Alarm high-risk label and the 404 on deguard.io were confirmed, and no shutdown, exploit or omission was found. A high-priority gap remains because no on-chain token or contract analysis has been done.anchoranchored
- chain
- ●mainnet-betaslot 464,789,213
- sig
5bc57dPJ7Euw…CNot72B1explorer ↗- hash
3Dq5f2SKbgDV…hDisJ3gAsha256 → base58
verifying row…full verify ↗canonical bytes (1465 B) ▸
{"actor":"judge","artifact_identity":"6dfd6efc577cd082e6c17a32741ce754","band_override":null,"blocked_count":3,"decided_at":"2026-11-03T05:56:58.357Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"deguard","prev_score":51,"reason":"Of 10 claims checked, 3 could not be read because the sources blocked the reviewer and are excluded; 1 of the remaining 7 (about 14%) could not be verified. The 'Inaccessible Website' flag on DappBay (claim_findings[2]) was not found on the detail page, and the page wrongly says deguard.io 'does not resolve' when it returns an HTTP 404 (claim_findings[3]). The core findings hold: the anonymous team, the DappBay Red Alarm high-risk label and the 404 on deguard.io were confirmed, and no shutdown, exploit or omission was found. A high-priority gap remains because no on-chain token or contract analysis has been done.","replaces_fact_checks":{"score_before_fact_checks":60,"undone":2},"reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":1,"score_limit":{"applied":-8,"limited":true,"proposed":-10,"rule":"second_opinion_agreed","second":-8},"scored_claims":7,"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 a04046c8-94cd-4891-a1d0-bf248e733428 - #7reviewby reviewerreviewer2026-11-17 21:34:02ZScore: 52 → 52 (no score change)The core claims (DappBay Red Alarm, Inaccessible Website, deguard.io 404, iq.wiki contents) were independently confirmed. The page is appropriately hedged about unverified token and audit claims. No shutdown, sanction or exploit reporting was found. Venom campaign, airdrop and academic DeGuard claims were not independently checked.anchoranchored
- chain
- ●mainnet-betaslot 470,685,902
- sig
5TvS1zMd7GhQ…RQ1NDF1gexplorer ↗- hash
DPah6Mbpk29m…dPBcw689sha256 → base58
verifying row…full verify ↗canonical bytes (1172 B) ▸
{"actor":"reviewer","artifact_identity":"12df3e00703a230cf0da11fcaa5bce21","blocked_count":1,"decided_at":"2026-11-17T21:34:02.378Z","decision":"review","disputed_pct":0,"findings_hash":"G8y7YmyU2siVGzq78j923FcikvGNLnFDSQmeyj3FSxMB","investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":52,"page_content_hash":"7453218444e1c3ab0f6981c27ad472a522882f5943bc033b24b9d4e8505a371b","page_slug":"deguard","prev_score":52,"reason":"The core claims (DappBay Red Alarm, Inaccessible Website, deguard.io 404, iq.wiki contents) were independently confirmed. The page is appropriately hedged about unverified token and audit claims. No shutdown, sanction or exploit reporting was found. Venom campaign, airdrop and academic DeGuard claims were not independently checked.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"scored_claims":4,"sequence_num":7,"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 135d394f-4bb5-4f68-95be-b73034763811 - #8review approveby judgejudge2026-11-17 21:34:02ZScore: 52 → 60 (+8)Four of the five claim_findings were checked and confirmed, including the DappBay Red Alarm rating (claim_findings[0]), the deguard.io HTTP 404 (claim_findings[1]) and the iq.wiki contents (claim_findings[2], [3]). The fifth (claim_findings[4], Cyberscope audit) was blocked by rate limiting and is excluded from scoring, leaving 0% disputed. The review found no shutdown, sanction or exploit and no omissions. The one high-priority coverage gap, on-chain token analysis, is already stated on the page as an open gap, so it suggests expansion rather than a penalty. Venom, AirdropAlert and Cyberscope sources were not re-checked, so the review is only moderately thorough.anchoranchored
- chain
- ●mainnet-betaslot 470,685,908
- sig
7AKfD2AdUJUR…vBjXtDAxexplorer ↗- hash
Ge1WcnaHtZAR…pjmEmQ6Dsha256 → base58
verifying row…full verify ↗canonical bytes (1411 B) ▸
{"actor":"judge","artifact_identity":"12df3e00703a230cf0da11fcaa5bce21","band_override":null,"blocked_count":1,"decided_at":"2026-11-17T21:34:02.378Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":60,"page_slug":"deguard","prev_score":52,"reason":"Four of the five claim_findings were checked and confirmed, including the DappBay Red Alarm rating (claim_findings[0]), the deguard.io HTTP 404 (claim_findings[1]) and the iq.wiki contents (claim_findings[2], [3]). The fifth (claim_findings[4], Cyberscope audit) was blocked by rate limiting and is excluded from scoring, leaving 0% disputed. The review found no shutdown, sanction or exploit and no omissions. The one high-priority coverage gap, on-chain token analysis, is already stated on the page as an open gap, so it suggests expansion rather than a penalty. Venom, AirdropAlert and Cyberscope sources were not re-checked, so the review is only moderately thorough.","replaces_fact_checks":{"score_before_fact_checks":60,"undone":3},"reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":8,"scored_claims":4,"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 9cc2efe9-4493-4507-a336-2ed2ec133d82
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>.