← DYORSwap15 decisions on this page
Audit log
Every state-changing event for DYORSwap: 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.
- #1publishby system:backfill2026-10-02 17:08:57ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 452,673,245
- sig
VabJTXvUUA4u…ULrxDVkrexplorer ↗- hash
67xWbz42BqeE…VPupsLuHsha256 → base58
verifying row…full verify ↗canonical bytes (10651 B) ▸
{"actor":"system:backfill","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","kind":"publish","page_slug":"dyorswap","published_at":"2026-10-02T17:08:57.410Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"DYORSWAP","sections":[{"content":"DYORSWAP is a decentralized exchange (DEX) offering token swaps, liquidity provision, and staking across a large number of blockchain networks, reportedly including X Layer, Blast, Ink, Stable, Plasma, and Degen Chain, among others, with X Layer representing the largest share of activity. The platform has a native DYOR token used for governance and protocol revenue sharing. As of recent data cited by DeFiLlama, the protocol's Total Value Locked (TVL) was reported at roughly $2.7 million, indicating a relatively small-to-mid-size DEX rather than a top-tier exchange. No named founders or core team members for DYORSWAP specifically have been identified in publicly available sources; a separate, differently-named project (\"Dyor Exchange\") with listed executives appears to be an unrelated entity and should not be confused with DYORSWAP.","heading":"Platform Overview","severity":"low","sources":[{"credibility":2,"name":"DYORSwap (Blast) Statistics - CoinGecko","type":"research","url":"https://www.coingecko.com/en/exchanges/dyorswap-blast"},{"credibility":2,"name":"DyorSwap TVL, Fees, Revenue & Volume - DefiLlama","type":"on_chain","url":"https://defillama.com/protocol/dyorswap"}]},{"content":"In late September 2026, scammers deployed a fraudulent blockchain that impersonated GIWA, an Ethereum Layer-2 network under development by South Korean exchange operator Dunamu (operator of Upbit). The fake chain reused GIWA's legitimate chain ID (9134), which misled DYORSWAP's verification process into integrating it as though it were the authentic GIWA mainnet. According to multiple reports, the fraudulent bridge went live shortly after 6 PM UTC on a Saturday and was fully drained roughly 12 hours later, with stolen funds routed through the Tornado Cash mixer. Approximately 1,335 addresses bridged a combined 767.65 ETH into the fake contract, of which about 766.25 ETH (roughly $2 million) was stolen. GIWA's actual operators publicly denied having an active mainnet, but the warning came only minutes before the fraudulent contract was emptied, too late to prevent most losses. DYORSWAP subsequently stated that its own DYOR smart contracts were not compromised or attacked; the incident instead involved a wholly separate, fraudulent chain that DYORSWAP had mistakenly listed and integrated.","heading":"Fake GIWA Mainnet Bridge Scam (September 2026)","severity":"critical","sources":[{"credibility":1,"name":"Scammers Steal $2M in ETH as Fake GIWA Network Fools DYORSWAP - Cointelegraph","type":"news_article","url":"https://cointelegraph.com/news/fake-giwa-blockchain-scam-drains-2m-eth"},{"credibility":2,"name":"DYORSWAP users tricked into sending 767 ETH to fake bridge contract - Protos","type":"news_article","url":"https://protos.com/dyorswap-users-tricked-into-sending-767-eth-to-fake-bridge-contract/"},{"credibility":2,"name":"DYORSWAP Fake Bridge Scam Drains $2M in ETH - Cryptonomist","type":"news_article","url":"https://en.cryptonomist.ch/2026/09/28/dyorswap-fake-bridge-scam/"},{"credibility":2,"name":"DyorSwap Identifies Fake GIWA Mainnet as a Scam and Plans Treasury Compensation for Affected Users - KuCoin News","type":"news_article","url":"https://www.kucoin.com/news/flash/dyorswap-identifies-fake-giwa-mainnet-as-scam-plans-treasury-compensation-for-affected-users"},{"credibility":2,"name":"DYORSWAP: DYOR contract was not attacked; over 200 ETH in compensation distributed - PANews","type":"news_article","url":"https://panews.io/articles/01a0e5af-140a-751d-923d-a3d804b3f1a1"}]},{"content":"Following the fake GIWA bridge incident, DYORSWAP announced it would use treasury reserves to reimburse affected users. Under the published compensation structure, users who bridged less than 5 ETH into the fraudulent contract were offered a 40% reimbursement ratio, while addresses that bridged larger amounts were subject to separate case-by-case review due to suspicion of phishing involvement or participation in the fraud itself. DYORSWAP stated it had distributed over 200 ETH in compensation to affected users from its own funds, and published an official compensation wallet address while warning users that the team would never ask victims to send funds or pay fees as part of the compensation process -- a caution against follow-up scams targeting the same victims. The team also stated it was investigating the bridge deployer and downstream fund recipients, including flagging suspicious accounts allegedly linked to funding via Binance and Gate.io.","heading":"Compensation Response","severity":"medium","sources":[{"credibility":2,"name":"DYORSWAP GIWA Scam Compensation: 40% Payout for Eligible Victims - Phemex","type":"news_article","url":"https://phemex.com/news/article/dyorswap-releases-compensation-plan-for-giwa-fake-chain-scam-victims-97998"},{"credibility":2,"name":"DYORSWAP: DYOR contract was not attacked; over 200 ETH in compensation distributed - PANews","type":"news_article","url":"https://panews.io/articles/01a0e5af-140a-751d-923d-a3d804b3f1a1"}]},{"content":"No publicly disclosed third-party smart contract audit from a widely recognized security firm (such as CertiK, Hacken, or PeckShield) has been identified for DYORSWAP. The absence of a verified audit, combined with the platform's failure to properly validate a counterfeit blockchain before integrating it -- which directly enabled the September 2026 GIWA impersonation losses -- represents a material due-diligence gap. This is distinct from, but related to, the GIWA incident: the core vulnerability exploited was not a smart-contract bug but inadequate chain-verification procedures prior to listing a new network. This finding is based on an absence of evidence of an audit in available sources rather than a confirmed statement that no audit exists, and should be treated with that caveat.","heading":"Transparency and Audit Concerns","severity":"medium","sources":[{"credibility":2,"name":"DYORSwap on Solana: Project Review, Programs, Token, Metrics - Solana Compass","type":"research","url":"https://solanacompass.com/projects/dyorswap"}]}],"sources_used":[{"credibility":1,"name":"Scammers Steal $2M in ETH as Fake GIWA Network Fools DYORSWAP - Cointelegraph","type":"news_article","url":"https://cointelegraph.com/news/fake-giwa-blockchain-scam-drains-2m-eth"},{"credibility":2,"name":"DYORSWAP users tricked into sending 767 ETH to fake bridge contract - Protos","type":"news_article","url":"https://protos.com/dyorswap-users-tricked-into-sending-767-eth-to-fake-bridge-contract/"},{"credibility":2,"name":"DYORSWAP Fake Bridge Scam Drains $2M in ETH - Cryptonomist","type":"news_article","url":"https://en.cryptonomist.ch/2026/09/28/dyorswap-fake-bridge-scam/"},{"credibility":2,"name":"DyorSwap Identifies Fake GIWA Mainnet as a Scam and Plans Treasury Compensation for Affected Users - KuCoin News","type":"news_article","url":"https://www.kucoin.com/news/flash/dyorswap-identifies-fake-giwa-mainnet-as-scam-plans-treasury-compensation-for-affected-users"},{"credibility":2,"name":"DYORSWAP: DYOR contract was not attacked; over 200 ETH in compensation distributed - PANews","type":"news_article","url":"https://panews.io/articles/01a0e5af-140a-751d-923d-a3d804b3f1a1"},{"credibility":2,"name":"DYORSWAP GIWA Scam Compensation: 40% Payout for Eligible Victims - Phemex","type":"news_article","url":"https://phemex.com/news/article/dyorswap-releases-compensation-plan-for-giwa-fake-chain-scam-victims-97998"},{"credibility":2,"name":"DYORSwap (Blast) Statistics - CoinGecko","type":"research","url":"https://www.coingecko.com/en/exchanges/dyorswap-blast"},{"credibility":2,"name":"DyorSwap TVL, Fees, Revenue & Volume - DefiLlama","type":"on_chain","url":"https://defillama.com/protocol/dyorswap"},{"credibility":2,"name":"DYORSwap on Solana: Project Review, Programs, Token, Metrics - Solana Compass","type":"research","url":"https://solanacompass.com/projects/dyorswap"}],"summary":"DYORSWAP (also styled DyorSwap) is a multi-chain decentralized exchange operating across more than a dozen networks including X Layer, Blast, Ink, and Plasma, with a native DYOR governance token. In September 2026 the platform integrated a fraudulent blockchain impersonating the legitimate GIWA Layer-2 network, after which scammers drained roughly 766 ETH (about $2 million) from users who bridged funds believing it was the real GIWA mainnet. DYORSWAP has stated its own smart contracts were not hacked, has offered partial treasury-funded compensation to affected users, and no court filings or regulatory enforcement actions against the platform have been identified.","timeline":[{"date":"2026-09","event":"A fraudulent blockchain impersonating GIWA, an Ethereum Layer-2 network under development by Upbit operator Dunamu, is deployed, reusing GIWA's legitimate chain ID (9134); DYORSWAP integrates it believing it to be the authentic GIWA mainnet. The fake bridge goes live and is drained within roughly 12 hours, with proceeds routed through Tornado Cash.","source":"Protos","source_url":"https://protos.com/dyorswap-users-tricked-into-sending-767-eth-to-fake-bridge-contract/"},{"date":"2026-09","date_evidence":"DyorSwap issued a crypto scam alert on September 27 (UTC+8), confirming that the so-called \"GIWA mainnet\" is a fraudulent network.","date_original":"2026-09-27","event":"DYORSWAP publicly confirms the GIWA mainnet it had integrated was fraudulent and warns users to avoid unofficial GIWA RPCs, bridges, and contracts.","source":"KuCoin News","source_url":"https://www.kucoin.com/news/flash/dyorswap-identifies-fake-giwa-mainnet-as-scam-plans-treasury-compensation-for-affected-users"},{"date":"2026-09","date_original":"2026-09-28","event":"DYORSWAP states its own DYOR smart contracts were not attacked, discloses it has distributed over 200 ETH in compensation to affected users from treasury funds, and details that 1,335 addresses bridged funds with 766.25 ETH ultimately stolen.","source":"PANews","source_url":"https://panews.io/articles/01a0e5af-140a-751d-923d-a3d804b3f1a1"},{"date":"2026-09","event":"DYORSWAP publishes a tiered compensation plan: a 40% reimbursement ratio for users who bridged less than 5 ETH, with larger amounts subject to individual review.","source":"Phemex","source_url":"https://phemex.com/news/article/dyorswap-releases-compensation-plan-for-giwa-fake-chain-scam-victims-97998"}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision db68d37a-fcdd-4d62-b6fe-10605949902e - #2reviewby reviewerreviewer2026-10-27 10:50:40ZScore: 38 → 38 (no score change)The core incident facts (fake GIWA chain, chain ID 9134, 767.65 ETH, 1,335 addresses, 766.25 ETH drained, dates) match the sources I could read. Weaknesses: the 'inadvertent victim' wording is attributed to Crypto Briefing but is DYORSwap's own framing; one timeline entry cites the wrong source for the 40% ratio and compensation address; the 'no perpetrators named' line leaves out the project's suspect addresses and the Tornado Cash laundering. The anonymous-team, no-audit and market-metric claims could not be checked because their sources were blocked.anchoranchored
- chain
- ●mainnet-betaslot 462,042,980
- sig
4mZMRAyyaH5D…K1muSxxrexplorer ↗- hash
2uY8gzRogP1S…GFbo2N93sha256 → base58
verifying row…full verify ↗canonical bytes (1438 B) ▸
{"actor":"reviewer","artifact_identity":"91cf880561a2ca813b14a76f2ad2e959","blocked_count":2,"decided_at":"2026-10-27T10:50:40.026Z","decision":"review","disputed_pct":0,"findings_hash":"AvtV7zrynDZpjNPrDnditP6QcZKz8LyErFbknZg6hnFa","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"omissions":{"material":0,"total":2},"page_content_hash":"67543ae87b6d0c1ca2d1c6ad1af6c5d29a5e847e5b054c68d62058f141175311","page_slug":"dyorswap","prev_score":38,"reason":"The core incident facts (fake GIWA chain, chain ID 9134, 767.65 ETH, 1,335 addresses, 766.25 ETH drained, dates) match the sources I could read. Weaknesses: the 'inadvertent victim' wording is attributed to Crypto Briefing but is DYORSwap's own framing; one timeline entry cites the wrong source for the 40% ratio and compensation address; the 'no perpetrators named' line leaves out the project's suspect addresses and the Tornado Cash laundering. The anonymous-team, no-audit and market-metric claims could not be checked because their sources were blocked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":4,"sequence_num":2,"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 f7aa0204-cf50-477a-8264-f4d2b18eeee9 - #3review reviseby judgejudge2026-10-27 10:50:40ZScore: 38 → 33 (-5)The core incident facts (fake GIWA chain, chain ID 9134, 767.65 ETH received, 766.25 ETH drained) were confirmed (claim_findings[0]), and no claim was disputed, so the computed disputed share is 0% (4 countable findings; 2 of 6 were excluded because the sources blocked the reviewer). The page is revised rather than approved because the audit and team claims rest on a single source that could not be read, which the reviewer rated a high-priority coverage gap, and because three claims need correction: the 'inadvertent victim' wording is attributed to Crypto Briefing but is DYORSwap's own framing (claim_findings[1]), the 40% compensation ratio and address are cited to the wrong article (claim_findings[2]), and 'no perpetrators named' leaves out the project's suspect addresses and the Tornado Cash laundering (claim_findings[3], omission_findings[0]). No shutdown, sanction or exploit contradicts the page, and the omissions are minor. The blocked share is a limit on what could be checked, not a defect of the page.anchoranchored
- chain
- ●mainnet-betaslot 462,042,985
- sig
3CCtXaNnEHws…B1XmBKeFexplorer ↗- hash
9QqHpNuajhUX…j9zpJLz3sha256 → base58
verifying row…full verify ↗canonical bytes (2865 B) ▸
{"actor":"judge","artifact_identity":"91cf880561a2ca813b14a76f2ad2e959","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"The core incident facts (fake GIWA chain, chain ID 9134, 767.65 ETH received, 766.25 ETH drained) were confirmed (claim_findings[0]), and no claim was disputed, so the computed disputed share is 0% (4 countable findings; 2 of 6 were excluded because the sources blocked the reviewer). The page is revised rather than approved because the audit and team claims rest on a single source that could not be read, which the reviewer rated a high-priority coverage gap, and because three claims need correction: the 'inadvertent victim' wording is attributed to Crypto Briefing but is DYORSwap's own framing (claim_findings[1]), the 40% compensation ratio and address are cited to the wrong article (claim_findings[2]), and 'no perpetrators named' leaves out the project's suspect addresses and the Tornado Cash laundering (claim_findings[3], omission_findings[0]). No shutdown, sanction or exploit contradicts the page, and the omissions are minor. The blocked share is a limit on what could be checked, not a defect of the page."},"blocked_count":2,"decided_at":"2026-10-27T10:50:40.026Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":33,"page_slug":"dyorswap","prev_score":38,"reason":"The core incident facts (fake GIWA chain, chain ID 9134, 767.65 ETH received, 766.25 ETH drained) were confirmed (claim_findings[0]), and no claim was disputed, so the computed disputed share is 0% (4 countable findings; 2 of 6 were excluded because the sources blocked the reviewer). The page is revised rather than approved because the audit and team claims rest on a single source that could not be read, which the reviewer rated a high-priority coverage gap, and because three claims need correction: the 'inadvertent victim' wording is attributed to Crypto Briefing but is DYORSwap's own framing (claim_findings[1]), the 40% compensation ratio and address are cited to the wrong article (claim_findings[2]), and 'no perpetrators named' leaves out the project's suspect addresses and the Tornado Cash laundering (claim_findings[3], omission_findings[0]). No shutdown, sanction or exploit contradicts the page, and the omissions are minor. The blocked share is a limit on what could be checked, not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":4,"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 bda10d0a-1c3c-4666-8c24-9e7b6c54b92a - #4rescoreby systemsystem2026-11-01 17:06:08ZScore: 33 → 79 (+46)Rescored under Scoring v2, the published formula (avoid.net/scoring): 33 → 79. Problems weighed by who is responsible: concerns that are not fraud −6.4, problems around the subject, caused by others −1.8; legitimacy credit long-running +4, audits +8; 2 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−5) now shown as page reliability, not in the score.anchoranchored
- chain
- ●mainnet-betaslot 464,169,937
- sig
2Xj585Sjhw2V…4bDgwWCFexplorer ↗- hash
9VF1zFYBRX4t…CKhjR3cFsha256 → base58
verifying row…full verify ↗canonical bytes (752 B) ▸
{"actor":"system","decided_at":"2026-11-01T17:06:08.089Z","decision":"rescore","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","new_score":79,"page_slug":"dyorswap","prev_score":33,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 33 → 79. Problems weighed by who is responsible: concerns that are not fraud −6.4, problems around the subject, caused by others −1.8; legitimacy credit long-running +4, audits +8; 2 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−5) now shown as page reliability, not in the score.","score_delta":46,"score_model":"v2","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 942200a4-dddc-41ef-93c1-26aed2e4051e - #5rescoreby systemsystem2026-11-03 09:54:27ZScore: 79 → 45 (-34)Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 79 → 45. Problems weighed by who is responsible: incidents the subject suffered −16, concerns that are not fraud −3.2, problems around the subject, caused by others −1.1; a recent unresolved incident −9.8.anchoranchored
- chain
- ●mainnet-betaslot 464,855,856
- sig
2Jjh6ok6Fn2Z…7H3LWNK2explorer ↗- hash
13PfysQUpBYR…HA9U9uGfsha256 → base58
verifying row…full verify ↗canonical bytes (707 B) ▸
{"actor":"system","decided_at":"2026-11-03T09:54:26.490Z","decision":"rescore","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","new_score":45,"page_slug":"dyorswap","prev_score":79,"reason":"Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 79 → 45. Problems weighed by who is responsible: incidents the subject suffered −16, concerns that are not fraud −3.2, problems around the subject, caused by others −1.1; a recent unresolved incident −9.8.","score_delta":-34,"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 c43e5c02-9c97-46c7-b182-32d44aa0ef6b - #6reviewby reviewerreviewer2026-11-03 09:55:56ZScore: 45 → 45 (no score change)The core incident facts (amounts, address count, dates, chain ID 9134, compensation over 200 ETH, Tornado Cash figures) match the cited sources. Defects are attribution: the 40% policy is credited to KuCoin, which does not report it, and the 12-13 hour duration is credited to Cointelegraph, which does not state it. The GIWA denial timing was not verified. The Grid and DefiLlama claims were not checked. No shutdown or sanction was found.anchoranchored
- chain
- ●mainnet-betaslot 464,856,175
- sig
M8jmgyqFHehW…7Lfsq5sCexplorer ↗- hash
9fJZKmGjXsr6…ADHp9PKpsha256 → base58
verifying row…full verify ↗canonical bytes (1251 B) ▸
{"actor":"reviewer","artifact_identity":"f9eb68d7f410e8ff06d4cade21c96cb0","decided_at":"2026-11-03T09:55:56.722Z","decision":"review","disputed_pct":0.2222,"findings_hash":"CmVoMPJzjjWNaoZ8DFTgJASGVaTLkH2uSQXgQSYYPiDC","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"page_content_hash":"6b8374dc2f78cfbf1d52660a2c5d6c90501a99c2c83c9cf8df5f22a79fd9dec9","page_slug":"dyorswap","prev_score":45,"reason":"The core incident facts (amounts, address count, dates, chain ID 9134, compensation over 200 ETH, Tornado Cash figures) match the cited sources. Defects are attribution: the 40% policy is credited to KuCoin, which does not report it, and the 12-13 hour duration is credited to Cointelegraph, which does not state it. The GIWA denial timing was not verified. The Grid and DefiLlama claims were not checked. No shutdown or sanction was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":6,"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 b87b29b4-c6de-4cd5-b121-04044d31af3b - #7review reviseby judgejudge2026-11-03 09:55:57ZScore: 45 → 45 (no score change)The core incident facts on this page (amounts, address count, deployment date, compensation of more than 200 ETH, Tornado Cash figures) match the cited sources, and no shutdown, sanction or omission was found. Two of eight claims could not be verified (claim_findings[7] on the timing of GIWA's denial, claim_findings[8] on the audit, team and TVL caveats), giving a disputed share of 25%. Two further claims are attributed to the wrong source: the 40% reimbursement policy is credited to KuCoin though Protos reports it (claim_findings[2]), and the 12-13 hour duration is credited to Cointelegraph though it does not state it (claim_findings[3]). These are citation fixes rather than disputed allegations, so the penalty is at the lower end of the minor band.anchoranchored
- chain
- ●mainnet-betaslot 464,856,323
- sig
2ZoWpFPVqE33…8yDrwxkGexplorer ↗- hash
BbrwraW7naTZ…shRQ27A9sha256 → base58
verifying row…full verify ↗canonical bytes (1402 B) ▸
{"actor":"judge","artifact_identity":"f9eb68d7f410e8ff06d4cade21c96cb0","band_override":null,"decided_at":"2026-11-03T09:55:56.722Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"page_slug":"dyorswap","prev_score":45,"reason":"The core incident facts on this page (amounts, address count, deployment date, compensation of more than 200 ETH, Tornado Cash figures) match the cited sources, and no shutdown, sanction or omission was found. Two of eight claims could not be verified (claim_findings[7] on the timing of GIWA's denial, claim_findings[8] on the audit, team and TVL caveats), giving a disputed share of 25%. Two further claims are attributed to the wrong source: the 40% reimbursement policy is credited to KuCoin though Protos reports it (claim_findings[2]), and the 12-13 hour duration is credited to Cointelegraph though it does not state it (claim_findings[3]). These are citation fixes rather than disputed allegations, so the penalty is at the lower end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"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 743eb064-0a49-4572-880f-5501a503d9d3 - #8rescoreby systemsystem2026-11-03 09:55:57ZScore: 45 → 48 (+3)Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 45 → 48. Problems weighed by who is responsible: incidents the subject suffered −16, problems around the subject, caused by others −1.1; a recent unresolved incident −9.8; 1 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 464,856,329
- sig
5tHH9hQzgUNW…awvVdhNaexplorer ↗- hash
ERUtHQaBzAt8…8SLfowZusha256 → base58
verifying row…full verify ↗canonical bytes (714 B) ▸
{"actor":"system","decided_at":"2026-11-03T09:55:56.722Z","decision":"rescore","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","new_score":48,"page_slug":"dyorswap","prev_score":45,"reason":"Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 45 → 48. Problems weighed by who is responsible: incidents the subject suffered −16, problems around the subject, caused by others −1.1; a recent unresolved incident −9.8; 1 section(s) set aside until a failed fact-check is resolved.","score_delta":3,"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 f87e541d-3603-4690-8912-51be810d5e96 - #9rescoreby systemsystem2026-11-04 10:06:26ZScore: 48 → 73 (+25)Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 48 → 73. Problems weighed by who is responsible: problems around the subject, caused by others −4.8, concerns that are not fraud −3.2; legitimacy credit audits +8.anchoranchored
- chain
- ●mainnet-betaslot 465,262,290
- sig
4erc4FiMXqgc…QsPYcWN6explorer ↗- hash
5FwikG4x989R…c1C7NYYQsha256 → base58
verifying row…full verify ↗canonical bytes (664 B) ▸
{"actor":"system","decided_at":"2026-11-04T10:06:26.032Z","decision":"rescore","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","new_score":73,"page_slug":"dyorswap","prev_score":48,"reason":"Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 48 → 73. Problems weighed by who is responsible: problems around the subject, caused by others −4.8, concerns that are not fraud −3.2; legitimacy credit audits +8.","score_delta":25,"score_model":"v2","sequence_num":9,"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 e040d241-a736-4cef-b438-25b2d348800f - #10reviewby reviewerreviewer2026-11-04 10:07:51ZScore: 73 → 73 (no score change)Core incident figures (767.65 ETH, 1,335 addresses, 766.25 ETH drained, ~$2M, 40% policy, 200+ ETH paid) match Protos and Cointelegraph. Minor issues: 'promoted' is unsupported, the Dunamu link is not in cited sources, and the Sept 27 quote is not in the cited Cointelegraph piece. Audit and team claims are unchecked negative statements, hedged by the page. No contradicting subject status found.anchoranchored
- chain
- ●mainnet-betaslot 465,262,715
- sig
3bQFUtJi6bLT…c61ig4hWexplorer ↗- hash
BsCrR8qt4feB…79qaVmFqsha256 → base58
verifying row…full verify ↗canonical bytes (1209 B) ▸
{"actor":"reviewer","artifact_identity":"cc8f9c48d27d92ae0d6a18e8226a40cc","decided_at":"2026-11-04T10:07:51.334Z","decision":"review","disputed_pct":0.2222,"findings_hash":"5jgKSq5uTia4ZoNaX2kr5PWFKYGJusEMyCszUA4UDTMr","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":73,"page_content_hash":"3b87108a7c8861a36b674d6eafd4d87fd90fe1bc3e87d6573b8cfdf2cadfa8af","page_slug":"dyorswap","prev_score":73,"reason":"Core incident figures (767.65 ETH, 1,335 addresses, 766.25 ETH drained, ~$2M, 40% policy, 200+ ETH paid) match Protos and Cointelegraph. Minor issues: 'promoted' is unsupported, the Dunamu link is not in cited sources, and the Sept 27 quote is not in the cited Cointelegraph piece. Audit and team claims are unchecked negative statements, hedged by the page. No contradicting subject status found.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":10,"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 9bc6e8fe-d0dc-4570-82fe-d10575ddf436 - #11review reviseby judgejudge2026-11-04 10:07:51ZScore: 73 → 73 (no score change)The core incident figures (767.65 ETH, 1,335 addresses, 766.25 ETH drained, about $2 million, the 40% reimbursement policy and over 200 ETH paid) were confirmed against Protos and Cointelegraph (claim_findings[0], [2], [5]). Two of nine claims (22%) could not be verified from the cited sources: the Dunamu association (claim_findings[4]) and the no-audit statement (claim_findings[8]). Two further claims were only partly supported: the summary's 'promoted' wording (claim_findings[1]) and the quoted 27 September statement missing from the cited Cointelegraph article (claim_findings[6]). No omission or contradicting subject status was found, so the minor band applies and a small penalty is set until the wording and citations are corrected.anchoranchored
- chain
- ●mainnet-betaslot 465,262,720
- sig
2DH67mjRmg5b…RdmfdV84explorer ↗- hash
3Sv3GhawivxK…oWbSenjWsha256 → base58
verifying row…full verify ↗canonical bytes (1388 B) ▸
{"actor":"judge","artifact_identity":"cc8f9c48d27d92ae0d6a18e8226a40cc","band_override":null,"decided_at":"2026-11-04T10:07:51.334Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":73,"page_slug":"dyorswap","prev_score":73,"reason":"The core incident figures (767.65 ETH, 1,335 addresses, 766.25 ETH drained, about $2 million, the 40% reimbursement policy and over 200 ETH paid) were confirmed against Protos and Cointelegraph (claim_findings[0], [2], [5]). Two of nine claims (22%) could not be verified from the cited sources: the Dunamu association (claim_findings[4]) and the no-audit statement (claim_findings[8]). Two further claims were only partly supported: the summary's 'promoted' wording (claim_findings[1]) and the quoted 27 September statement missing from the cited Cointelegraph article (claim_findings[6]). No omission or contradicting subject status was found, so the minor band applies and a small penalty is set until the wording and citations are corrected.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"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 44e6dae4-30c9-4898-9076-1ce94d9162b9 - #12rescoreby systemsystem2026-11-04 10:07:52ZScore: 73 → 76 (+3)Recalculated after the fact-check of 2026-11-04. Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 76. Problems weighed by who is responsible: problems around the subject, caused by others −4.8; legitimacy credit audits +8; 1 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 465,262,725
- sig
2Crih3JqmFPn…WknH1hv7explorer ↗- hash
Hxv2JfpHesE6…ZRy4Efdcsha256 → base58
verifying row…full verify ↗canonical bytes (673 B) ▸
{"actor":"system","decided_at":"2026-11-04T10:07:51.334Z","decision":"rescore","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","new_score":76,"page_slug":"dyorswap","prev_score":73,"reason":"Recalculated after the fact-check of 2026-11-04. Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 76. Problems weighed by who is responsible: problems around the subject, caused by others −4.8; legitimacy credit audits +8; 1 section(s) set aside until a failed fact-check is resolved.","score_delta":3,"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 3e9f86dd-770f-468f-a86e-6fa56196fafc - #13rescoreby systemsystem2026-11-17 21:10:33ZScore: 76 → 67 (-9)Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 76 → 67. Problems weighed by who is responsible: problems around the subject, caused by others −4.8, concerns that are not fraud −3.2.anchoranchored
- chain
- ●mainnet-betaslot 470,679,630
- sig
5KPFV9BipN9g…fehkhThXexplorer ↗- hash
4T8oxLBZv46e…Koi4gDsKsha256 → base58
verifying row…full verify ↗canonical bytes (636 B) ▸
{"actor":"system","decided_at":"2026-11-17T21:10:32.415Z","decision":"rescore","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","new_score":67,"page_slug":"dyorswap","prev_score":76,"reason":"Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 76 → 67. Problems weighed by who is responsible: problems around the subject, caused by others −4.8, concerns that are not fraud −3.2.","score_delta":-9,"score_model":"v2","sequence_num":13,"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 20c67756-61e0-45d2-9107-46c2feebf4fc - #14reviewby reviewerreviewer2026-11-17 21:11:25ZScore: 67 → 67 (no score change)Core incident facts (767.65 ETH, 1,335 addresses, chain ID 9134, Tornado Cash, 40% policy, over 200 ETH paid, no audits on DefiLlama) match Protos, Cointelegraph and the DefiLlama API. The page properly hedges single-source claims. No disputed claims found. Coverage of on-chain evidence and team background is thin. The TVL range and the 'perpetuals' product claim were not checked.anchoranchored
- chain
- ●mainnet-betaslot 470,679,643
- sig
2oiasadGoZhp…ayDmBhPYexplorer ↗- hash
Gr3Xg2D11ZeY…VKpwZY33sha256 → base58
verifying row…full verify ↗canonical bytes (1190 B) ▸
{"actor":"reviewer","artifact_identity":"f7cb786314f5f075c71a6e9b2f3b686a","decided_at":"2026-11-17T21:11:25.843Z","decision":"review","disputed_pct":0,"findings_hash":"4ea2sbjnBL9RJNkNmD2CrMceb87HvSsH7yxvNWaPNaX4","investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":67,"page_content_hash":"a31d566b787d0098ccee022e89aa9ba7e18a7f59b476738daa090e2d891164b9","page_slug":"dyorswap","prev_score":67,"reason":"Core incident facts (767.65 ETH, 1,335 addresses, chain ID 9134, Tornado Cash, 40% policy, over 200 ETH paid, no audits on DefiLlama) match Protos, Cointelegraph and the DefiLlama API. The page properly hedges single-source claims. No disputed claims found. Coverage of on-chain evidence and team background is thin. The TVL range and the 'perpetuals' product claim were not checked.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"sequence_num":14,"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 beeb9ea5-b38f-4cbb-bf49-746ab1f2e91b - #15review approveby judgejudge2026-11-17 21:11:26ZScore: 67 → 67 (no score change)All 7 claim_findings were confirmed against Protos, Cointelegraph, the KuCoin/Protos reporting and the DefiLlama API, so 0 of 7 are disputed or unverifiable (0%). The review found no omissions and its subject_status shows DYORSwap operating with nothing contradicting the page. The page also correctly flags single-source claims (claim_findings[4], claim_findings[3]). Open coverage gaps (on-chain addresses, team background, independent confirmation of compensation) are medium or low priority and suggest expansion rather than a penalty. The TVL range and the 'perpetuals' product claim were not checked by the reviewer.anchoranchored
- chain
- ●mainnet-betaslot 470,679,650
- sig
43TP4YcQdfm5…ueRjoM1fexplorer ↗- hash
6YGRKLWv5NDb…uJumW2Hpsha256 → base58
verifying row…full verify ↗canonical bytes (1261 B) ▸
{"actor":"judge","artifact_identity":"f7cb786314f5f075c71a6e9b2f3b686a","band_override":null,"decided_at":"2026-11-17T21:11:25.843Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":67,"page_slug":"dyorswap","prev_score":67,"reason":"All 7 claim_findings were confirmed against Protos, Cointelegraph, the KuCoin/Protos reporting and the DefiLlama API, so 0 of 7 are disputed or unverifiable (0%). The review found no omissions and its subject_status shows DYORSwap operating with nothing contradicting the page. The page also correctly flags single-source claims (claim_findings[4], claim_findings[3]). Open coverage gaps (on-chain addresses, team background, independent confirmation of compensation) are medium or low priority and suggest expansion rather than a penalty. The TVL range and the 'perpetuals' product claim were not checked by the reviewer.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"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 41545bd5-6bc6-4421-9f34-0e6c64ea6d34
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>.