Audit log

Every state-changing event for Poly Network: 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-21 18:45:42Z
   Score: ? → ? (no score change)
   anchoranchored

   chain

   ●mainnet-betaslot 421,258,817

   sig

   4FQDTj4p5Arv…oW9BTu8xcopyexplorer ↗

   hash

   85DQh6TTm46q…SLYkGUu5copysha256 → base58

   verifying row…full verify ↗

   canonical bytes (7092 B) ▸

   {"actor":"system:backfill","investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","kind":"publish","page_slug":"poly-network","published_at":"2026-05-21T18:45:41.971Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Poly Network","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://neo.org/blog/details/4207","type":"other","url":""},{"credibility":3,"name":"https://phemex.com/academy/what-is-poly-network","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/magazine/shanghai-man-poly-network-hacking-shows-how-divided-the-eastern-and-western-crypto-communities-still-are/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/markets/2021/08/10/cross-chain-defi-site-poly-network-hacked-hundreds-of-millions-potentially-lost","type":"other","url":""},{"credibility":3,"name":"https://www.chainalysis.com/blog/poly-network-hack-august-2021/","type":"other","url":""},{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-poly-network-hack-august-2021","type":"other","url":""},{"credibility":3,"name":"https://research.kudelskisecurity.com/2021/08/12/the-poly-network-hack-explained/","type":"other","url":""},{"credibility":3,"name":"https://slowmist.medium.com/the-root-cause-of-poly-network-being-hacked-ec2ee1b0c68f","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/resources/blog/HPJ3e0qAWPErSPdGeMXg1-poly-network-exploit","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cointelegraph.com/news/poly-network-hacker-returns-nearly-all-funds-refuses-500k-white-hat-bounty","type":"other","url":""},{"credibility":3,"name":"https://www.cnbc.com/2021/08/23/poly-network-hacker-returns-remaining-cryptocurrency.html","type":"other","url":""},{"credibility":3,"name":"https://en.wikipedia.org/wiki/Poly_Network_exploit","type":"other","url":""},{"credibility":3,"name":"https://protos.com/poly-network-white-hat-offers-500k-once-crypto-returned/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-poly-network-hack-july-2023","type":"other","url":""},{"credibility":3,"name":"https://dedaub.com/blog/poly-network-hack/","type":"other","url":""},{"credibility":3,"name":"https://www.theblock.co/post/237452/attacker-pockets-10-million-from-poly-network-security-attack-beosin","type":"other","url":""},{"credibility":3,"name":"https://decrypt.co/147059/poly-network-attack-conjures-billions-of-dollars-in-tokens-that-did-not-exist","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/tech/2023/07/02/polynetwork-attacker-issues-worthless-billions-in-shib-bnb-busd-in-latest-crypto-hack","type":"other","url":""},{"credibility":3,"name":"https://therecord.media/crypto-platform-poly-network-suspends-service-after-hack","type":"other","url":""},{"credibility":3,"name":"https://polynetwork.medium.com/the-poly-network-exploit-analysis-b0a77aff6078","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://blocksec.com/audit-report/security-audit-report-for-poly-contracts","type":"other","url":""},{"credibility":3,"name":"https://www.vidma.io/blog/poly-network-hack-a-611-million-lesson-in-smart-contract-vulnerabilities","type":"other","url":""},{"credibility":3,"name":"https://dedaub.com/blog/poly-network-hack/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://polynetwork.medium.com/notice-of-complete-termination-of-poly-network-services-3470ef78d9d9","type":"other","url":""},{"credibility":3,"name":"https://neonewstoday.com/development/poly-network-announces-complete-termination-of-all-services/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://en.wikipedia.org/wiki/Poly_Network_exploit","type":"other","url":""},{"credibility":3,"name":"https://dedaub.com/blog/poly-network-hack/","type":"other","url":""},{"credibility":3,"name":"https://therecord.media/crypto-platform-poly-network-suspends-service-after-hack","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/poly-network-hacker-returns-nearly-all-funds-refuses-500k-white-hat-bounty","type":"other","url":""},{"credibility":3,"name":"https://polynetwork.medium.com/notice-of-complete-termination-of-poly-network-services-3470ef78d9d9","type":"other","url":""}]}],"sources_used":[],"summary":"Poly Network was a cross-chain interoperability protocol launched in August 2020 by Neo, Ontology, and Switcheo. It suffered the largest DeFi hack in history in August 2021 (~$611M stolen, nearly all returned), followed by a second exploit in July 2023 (~$10M realized losses) attributed to compromised multisig private keys. The protocol permanently shut down all services on September 30, 2024.","timeline":[{"date":"2020-08-18","event":"Poly Network launches as a cross-chain interoperability protocol, founded by Neo, Ontology, and Switcheo.","source":""},{"date":"2021-08-10","event":"Poly Network suffers the largest DeFi hack in history: approximately $611M stolen across Ethereum (~$273M), BNB Chain (~$253M), and Polygon (~$85M) via an access control exploit in EthCrossChainManager.","source":""},{"date":"2021-08-11","event":"The attacker begins returning stolen funds and claims via on-chain messages that the theft was conducted 'for fun' to expose vulnerabilities. Poly Network begins addressing the attacker as 'Mr. White Hat.'","source":""},{"date":"2021-08-13","event":"Approximately $340M returned. Poly Network offers attacker a $500,000 bug bounty and the role of 'chief security advisor.' Security community criticizes the white hat framing.","source":""},{"date":"2021-08-15","event":"Tether Ltd. confirms it froze $33.4M in USDT linked to the attacker's wallet immediately after the hack.","source":""},{"date":"2021-08-25","event":"All remaining unfrozen funds returned to Poly Network. The attacker declines the $500,000 bounty.","source":""},{"date":"2023-07-02","event":"Poly Network suffers a second exploit: attacker mints tens of billions in notional token value across 57 assets on 10 blockchains. Realized losses estimated at ~$10M. Root cause: alleged compromise of 3 of 4 multisig keeper private keys.","source":""},{"date":"2023-07-03","event":"Poly Network suspends all services and advises users to withdraw assets. Dedaub publishes postmortem attributing the attack to compromised private keys, not a smart contract bug.","source":""},{"date":"2024-09-11","event":"Poly Network announces complete termination of all services, effective September 30, 2024, citing 'changing market conditions.'","source":""},{"date":"2024-09-30","event":"Poly Network permanently shuts down all services, including Poly Bridge.","source":""}]},"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 3a0547e9-76f2-4a65-939d-a3bd3f748283copy
2. #2rescoreby systemsystem

   2026-10-10 18:41:50Z
   Score: 10 → 50 (+40)
   Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 50. Problems weighed by who is responsible: incidents the subject suffered −9.6, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +8; no longer operating, so capped at 50.
   anchoranchored

   chain

   ●mainnet-betaslot 455,361,058

   sig

   3pwcS18Uhv8d…ew4xkpZfcopyexplorer ↗

   hash

   8fNxVCFNTVSp…NgpbxzkTcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (681 B) ▸

   {"actor":"system","decided_at":"2026-10-10T18:41:50.143Z","decision":"rescore","investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","new_score":50,"page_slug":"poly-network","prev_score":10,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 50. Problems weighed by who is responsible: incidents the subject suffered −9.6, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +8; no longer operating, so capped at 50.","score_delta":40,"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 604cb934-9737-41ec-be20-e591c17da313copy
3. #3rescoreby systemsystem

   2026-11-01 22:45:27Z
   Score: 50 → 37 (-13)
   Re-read and rescored after the page was re-researched (2026-11-01). Rescored under Scoring v2, the published formula (avoid.net/scoring): 50 → 37. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −15.2, problems around the subject, caused by others −0.6; legitimacy credit long-running +8; the penalty for incidents it suffered is capped at 20.
   anchoranchored

   chain

   ●mainnet-betaslot 464,264,809

   sig

   2RvxMPWawjyG…UVgpqhzrcopyexplorer ↗

   hash

   9fsJ8ZGkvik7…FFCdxeRNcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (767 B) ▸

   {"actor":"system","decided_at":"2026-11-01T22:45:26.175Z","decision":"rescore","investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","new_score":37,"page_slug":"poly-network","prev_score":50,"reason":"Re-read and rescored after the page was re-researched (2026-11-01). Rescored under Scoring v2, the published formula (avoid.net/scoring): 50 → 37. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −15.2, problems around the subject, caused by others −0.6; legitimacy credit long-running +8; the penalty for incidents it suffered is capped at 20.","score_delta":-13,"score_model":"v2","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 e4eda18a-a177-4d2b-84bd-c423ceba2a3ccopy
4. #4reviewby reviewerreviewer

   2026-11-01 22:46:57Z
   Score: 37 → 37 (no score change)
   The core history (2021 hack and return of funds, July 2023 key compromise, September 2024 termination) is broadly supported by what I checked. Errors and gaps: the Tether freeze is dated August 15 when it was reported August 10 and the funds were later released; one Dedaub quotation could not be found and the Dedaub conclusion is more hedged than the page states; the page omits an August 2024 exploit (about $3-5M) and so wrongly counts two incidents; and one claim about ZachXBT is unsourced. Several sections contain internal merge language that is not suitable for publication. Many cited pages were not individually fetched, and the primary shutdown notice returned 403.
   anchoranchored

   chain

   ●mainnet-betaslot 464,265,237

   sig

   XngJe3rtv9tV…s8CWrva8copyexplorer ↗

   hash

   7ZsVtRm8Vr4s…D4vKD1sjcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1526 B) ▸

   {"actor":"reviewer","artifact_identity":"09414f7799041c314f2b3100f1356e92","decided_at":"2026-11-01T22:46:57.075Z","decision":"review","disputed_pct":0.5,"findings_hash":"4GRam1Cesu5PaVGqoRugdraRNvz38rJoDNquWFHA2vVc","investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":37,"omissions":{"material":1,"total":1},"page_content_hash":"d3fc980b9ea7956c38853410db534dfa66f64365b4dd9f3cc8d21b638f4eb8b5","page_slug":"poly-network","prev_score":37,"reason":"The core history (2021 hack and return of funds, July 2023 key compromise, September 2024 termination) is broadly supported by what I checked. Errors and gaps: the Tether freeze is dated August 15 when it was reported August 10 and the funds were later released; one Dedaub quotation could not be found and the Dedaub conclusion is more hedged than the page states; the page omits an August 2024 exploit (about $3-5M) and so wrongly counts two incidents; and one claim about ZachXBT is unsourced. Several sections contain internal merge language that is not suitable for publication. Many cited pages were not individually fetched, and the primary shutdown notice returned 403.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"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 09e4f842-d9fc-4f04-bde1-7db4587d633acopy
5. #5review reviseby judgejudge

   2026-11-01 22:46:57Z
   Score: 37 → 37 (no score change)
   Of 10 claims checked, 1 was disputed and 3 could not be verified (4 of 10, 40%), which puts the page in the significant-issues band. The core history (the August 2021 exploit and fund return, the July 2023 key compromise, the September 2024 termination) was confirmed or partly supported. The disputed items are the Tether freeze, dated August 15 when it was reported August 10 (claim_findings[0]), and the statement that there were two security incidents, which leaves out a third exploit in August 2024 (claim_findings[5], omission_findings[0]). The page also has an unsourced ZachXBT attribution, an unlocated Dedaub quotation, and internal 'survivor page' and 'merged page' wording that should be removed. The review rested partly on search snippets and secondary sources, so the penalty stops short of a failed factcheck.
   anchoranchored

   chain

   ●mainnet-betaslot 464,265,243

   sig

   3McTu5oaCFc4…UbmSzbdRcopyexplorer ↗

   hash

   4VqK72sMujoa…NyCxobSocopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1865 B) ▸

   {"actor":"judge","artifact_identity":"09414f7799041c314f2b3100f1356e92","band_override":null,"decided_at":"2026-11-01T22:46:57.075Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":37,"page_slug":"poly-network","prev_score":37,"reason":"Of 10 claims checked, 1 was disputed and 3 could not be verified (4 of 10, 40%), which puts the page in the significant-issues band. The core history (the August 2021 exploit and fund return, the July 2023 key compromise, the September 2024 termination) was confirmed or partly supported. The disputed items are the Tether freeze, dated August 15 when it was reported August 10 (claim_findings[0]), and the statement that there were two security incidents, which leaves out a third exploit in August 2024 (claim_findings[5], omission_findings[0]). The page also has an unsourced ZachXBT attribution, an unlocated Dedaub quotation, and internal 'survivor page' and 'merged page' wording that should be removed. The review rested partly on search snippets and secondary sources, so the penalty stops short of a failed factcheck.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"omission_findings[0] (the August 12, 2024 exploit, about $3-5M, six weeks before the shutdown) is material and the page's 'two major security incidents' wording is disputed by claim_findings[5]. The percentage band is already significant, so the override confirms that band and does not move to deny."},"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 c9d956d3-088d-4822-a38b-100d3c7a5acbcopy
6. #6rescoreby systemsystem

   2026-11-01 22:46:58Z
   Score: 37 → 50 (+13)
   Recalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 37 → 50. Problems weighed by who is responsible: incidents the subject suffered −13.2, concerns that are not fraud −9.2, problems around the subject, caused by others −0.6; legitimacy credit long-running +8; 2 section(s) set aside until a failed fact-check is resolved.
   anchoranchored

   chain

   ●mainnet-betaslot 464,265,248

   sig

   5q56fwJJ3fUc…rzmjPHGScopyexplorer ↗

   hash

   3CPV15yGUFDn…zsNbQ8LEcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (755 B) ▸

   {"actor":"system","decided_at":"2026-11-01T22:46:57.075Z","decision":"rescore","investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","new_score":50,"page_slug":"poly-network","prev_score":37,"reason":"Recalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 37 → 50. Problems weighed by who is responsible: incidents the subject suffered −13.2, concerns that are not fraud −9.2, problems around the subject, caused by others −0.6; legitimacy credit long-running +8; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":13,"score_model":"v2","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 a950d2fb-53a9-4c48-9444-47dce8137027copy