← Poloniex5 decisions on this page
Audit log
Every state-changing event for Poloniex: 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-05-20 15:41:11ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 421,014,730
- sig
4Skh21QWc9RA…zWuUbTPcexplorer ↗- hash
CXuAU3sBfM4F…dscmWFkisha256 → base58
verifying row…full verify ↗canonical bytes (6713 B) ▸
{"actor":"system:backfill","investigation_id":"c6694f49-a602-4394-b3dd-d238fce195db","kind":"publish","page_slug":"poloniex","published_at":"2026-05-20T15:41:11.322Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Poloniex","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.bitget.com/academy/12560603878185"},{"credibility":3,"name":"","type":"other","url":"https://coinledger.io/blog/us-residents-losing-access-to-poloniex"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.coindesk.com/markets/2019/11/12/despite-denials-tron-founder-confirms-investment-in-poloniex-crypto-exchange"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/justin-sun-platforms-hacked-4-times"},{"credibility":3,"name":"","type":"other","url":"https://www.cnbc.com/2023/11/23/htx-heco-chain-crypto-hack-115-million-stolen-so-far.html"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://decrypt.co/205465/justin-sun-owned-crypto-exchange-poloniex-hacked-60m"},{"credibility":3,"name":"","type":"other","url":"https://coingape.com/poloniex-hack-total-funds-stolen-reaches-over-126-million-btc-eth-shib-most-impacted/"},{"credibility":3,"name":"","type":"other","url":"https://www.halborn.com/blog/post/explained-the-poloniex-hack-november-2023"},{"credibility":3,"name":"","type":"other","url":"https://www.certik.com/resources/blog/poloniex-incident-analysis"},{"credibility":3,"name":"","type":"other","url":"https://dailyhodl.com/2023/11/10/tron-founder-justin-sun-offers-5-cut-to-hacker-after-poloniex-crypto-exchange-loses-125000000-in-cyber-heist/"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.halborn.com/blog/post/explained-the-poloniex-hack-november-2023"},{"credibility":3,"name":"","type":"other","url":"https://www.bitdefender.com/en-us/blog/hotforsecurity/poloniex-hackers-have-begun-to-move-some-of-the-stolen-120-million"},{"credibility":3,"name":"","type":"other","url":"https://cryptonews.com/news/poloniex-hacker-transfers-massive-32-million-bitcoin-stash/"},{"credibility":3,"name":"","type":"other","url":"https://digifinex.medium.com/poloniex-heist-possibly-linked-to-north-korean-lazarus-group-justin-sun-claims-losses-within-cf4a00de8d84"},{"credibility":3,"name":"","type":"other","url":"https://hacken.io/discover/lazarus-group/"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.sec.gov/newsroom/press-releases/2021-147"},{"credibility":3,"name":"","type":"other","url":"https://www.coindesk.com/policy/2021/08/09/poloniex-agrees-to-10m-settlement-with-sec-for-operating-unregistered-exchange"},{"credibility":3,"name":"","type":"other","url":"https://www.coindesk.com/policy/2023/05/01/crypto-exchange-poloniex-agrees-to-76m-fine-settle-sanctions-violation-charges"},{"credibility":3,"name":"","type":"other","url":"https://blog.volkovlaw.com/2023/05/cryptocurrency-firm-poloniex-reaches-settlement-with-ofac-and-pays-7-5-million-for-sanctions-violations/"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://siliconangle.com/2023/11/10/justin-suns-poloniex-exchange-hit-100m-exploit/"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/justin-sun-platforms-hacked-4-times"},{"credibility":3,"name":"","type":"other","url":"https://www.disruptionbanking.com/2023/11/27/poloniex-offers-white-hat-bounty-to-black-hat-hackers-in-largest-crypto-attack-of-2023/"}]}],"sources_used":[],"summary":"Poloniex is a cryptocurrency exchange founded in 2014 and acquired in 2019 by an investor group led by Tron founder Justin Sun. On November 10, 2023, the exchange suffered one of the largest hot wallet compromises in crypto history, with attackers draining approximately $126 million across Ethereum, TRON, and Bitcoin networks in an attack attributed by multiple blockchain security firms to North Korea's Lazarus Group. The exchange has also faced significant regulatory enforcement actions, including a $7.59 million OFAC sanctions settlement and a $10.4 million SEC settlement for operating an unregistered national securities exchange.","timeline":[{"date":"2014-01-01","event":"Poloniex founded by Tristan D'Agosta; exchange opens for trading.","source":""},{"date":"2014-03-01","event":"Poloniex suffers its first hack, losing approximately 12.3% of its Bitcoin holdings.","source":""},{"date":"2018-02-01","event":"Circle Internet Financial acquires Poloniex for approximately $400 million.","source":""},{"date":"2019-10-01","event":"Poloniex spins out from Circle as Polo Digital Assets, Ltd., backed by an Asian investor group including Justin Sun. U.S. customers notified of service termination.","source":""},{"date":"2019-11-12","event":"Justin Sun publicly confirms his investment in Poloniex via a live stream on Poloniex's official Twitter profile.","source":""},{"date":"2019-12-15","event":"Final deadline for U.S. users to withdraw funds from Poloniex.","source":""},{"date":"2021-08-09","event":"SEC charges Poloniex with operating an unregistered national securities exchange; Poloniex settles for $10,388,309.","source":""},{"date":"2023-05-01","event":"OFAC announces $7.59 million settlement with Poloniex for approximately 65,942 apparent sanctions violations involving users in Crimea, Cuba, Iran, Sudan, and Syria.","source":""},{"date":"2023-09-24","event":"Justin Sun's HTX exchange (formerly Huobi) suffers a $8 million hack.","source":""},{"date":"2023-11-10","event":"Poloniex hot wallets on Ethereum, TRON, and Bitcoin are compromised; approximately $126 million drained. Justin Sun pledges full reimbursement and offers a 5% bounty to the attackers.","source":""},{"date":"2023-11-14","event":"Hackers begin moving stolen funds; approximately 1,100 ETH sent to Tornado Cash mixer.","source":""},{"date":"2023-11-23","event":"HTX and Heco Chain suffer additional exploits totaling approximately $115 million, bringing total losses across Sun-affiliated platforms to over $240 million in roughly two months.","source":""},{"date":"2024-04-12","event":"Poloniex announces bulk asset delistings, signaling platform contraction.","source":""},{"date":"2024-08-23","event":"Further bulk asset delistings announced by Poloniex.","source":""},{"date":"2024-11-07","event":"Additional bulk delistings; platform continues to reduce listed assets.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 58fd9115-1aae-40b9-85c8-2aaca23639cc - #2rescoreby systemsystem2026-10-10 18:49:23ZScore: 10 → 58 (+48)Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 58. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −6.4, problems around the subject, caused by others −0.8; legitimacy credit long-running +10.anchoranchored
- chain
- ●mainnet-betaslot 455,369,374
- sig
5zWd2ZbpSnGZ…dp3yVJjyexplorer ↗- hash
4dq5HTbtM4sp…ypq9e8iisha256 → base58
verifying row…full verify ↗canonical bytes (640 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:49:22.919Z","decision":"rescore","investigation_id":"c6694f49-a602-4394-b3dd-d238fce195db","new_score":58,"page_slug":"poloniex","prev_score":10,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 58. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −6.4, problems around the subject, caused by others −0.8; legitimacy credit long-running +10.","score_delta":48,"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 2fd9d9ba-6a4c-453b-b43f-d0a32e034f1d - #3reviewby reviewerreviewer2026-11-01 23:22:41ZScore: 58 → 58 (no score change)The core facts hold: the SEC settlement ($10,388,309, August 2021), the OFAC settlement ($7,591,630, 65,942 violations), and the November 2023 hack date and headline loss. Two errors are disputed. The base penalty is $99,237,000, not $98.8M, and the 'no business operations and no employees' quote comes from OFAC's release, not the SEC order. The page also blends the platform period with the violation period, which OFAC dates July 2015 to September 2019. Several hack-detail and attribution claims were not independently checked, and the timeline entries carry no sources.anchoranchored
- chain
- ●mainnet-betaslot 464,275,356
- sig
5BJ6TCwN5HVK…HzPKaWtTexplorer ↗- hash
9ZCioQTsYuAM…VYtCYo1Psha256 → base58
verifying row…full verify ↗canonical bytes (1420 B) ▸
{"actor":"reviewer","artifact_identity":"40948502f0569de63cd9d1893c10630a","decided_at":"2026-11-01T23:22:41.287Z","decision":"review","disputed_pct":0.5,"findings_hash":"EjQfNLvupaQerjZ6xGXBKXAZy882zDZsRAA5diVDjTQZ","investigation_id":"c6694f49-a602-4394-b3dd-d238fce195db","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"omissions":{"material":0,"total":1},"page_content_hash":"e561d64c66ffb3646d6afdb889872e7882f4897d04ae1057bdc85b0f28af2a64","page_slug":"poloniex","prev_score":58,"reason":"The core facts hold: the SEC settlement ($10,388,309, August 2021), the OFAC settlement ($7,591,630, 65,942 violations), and the November 2023 hack date and headline loss. Two errors are disputed. The base penalty is $99,237,000, not $98.8M, and the 'no business operations and no employees' quote comes from OFAC's release, not the SEC order. The page also blends the platform period with the violation period, which OFAC dates July 2015 to September 2019. Several hack-detail and attribution claims were not independently checked, and the timeline entries carry no sources.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"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 8f1297ac-0879-4879-a787-02858000549c - #4review reviseby judgejudge2026-11-01 23:22:41ZScore: 58 → 58 (no score change)Of 10 claims reviewed, 2 were disputed and 3 could not be verified, giving 50%, which falls in the significant-issues band. The disputed items are claim_findings[0], where OFAC's own release gives a base penalty of $99,237,000 rather than $98.8 million, and claim_findings[1], where a quote attributed to the SEC order comes from OFAC's release. The unverified items (claim_findings[5], [8], [9]) were not checked rather than contradicted, and the core SEC and OFAC settlement amounts and the November 2023 hack were confirmed. Because reviewer confidence is low (0.5) and the errors are factual details rather than core allegations, the penalty is set at the lighter end of the band.anchoranchored
- chain
- ●mainnet-betaslot 464,275,360
- sig
37kSA7SxtDfh…7iKcsmiNexplorer ↗- hash
AsZWMXCbMHqX…Bp5pPUZxsha256 → base58
verifying row…full verify ↗canonical bytes (1323 B) ▸
{"actor":"judge","artifact_identity":"40948502f0569de63cd9d1893c10630a","band_override":null,"decided_at":"2026-11-01T23:22:41.287Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"c6694f49-a602-4394-b3dd-d238fce195db","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_slug":"poloniex","prev_score":58,"reason":"Of 10 claims reviewed, 2 were disputed and 3 could not be verified, giving 50%, which falls in the significant-issues band. The disputed items are claim_findings[0], where OFAC's own release gives a base penalty of $99,237,000 rather than $98.8 million, and claim_findings[1], where a quote attributed to the SEC order comes from OFAC's release. The unverified items (claim_findings[5], [8], [9]) were not checked rather than contradicted, and the core SEC and OFAC settlement amounts and the November 2023 hack were confirmed. Because reviewer confidence is low (0.5) and the errors are factual details rather than core allegations, the penalty is set at the lighter end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"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 d8557154-13ac-43c0-a5ba-f10399758eb0 - #5rescoreby systemsystem2026-11-01 23:22:42ZScore: 58 → 65 (+7)Recalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 58 → 65. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2; legitimacy credit long-running +10; 3 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 464,275,365
- sig
2vo69Nc1akhU…HHsocmdQexplorer ↗- hash
EpaX5HyjxgyV…bcZGZ92hsha256 → base58
verifying row…full verify ↗canonical bytes (698 B) ▸
{"actor":"system","decided_at":"2026-11-01T23:22:41.287Z","decision":"rescore","investigation_id":"c6694f49-a602-4394-b3dd-d238fce195db","new_score":65,"page_slug":"poloniex","prev_score":58,"reason":"Recalculated after the fact-check of 2026-11-01. Rescored under Scoring v2, the published formula (avoid.net/scoring): 58 → 65. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2; legitimacy credit long-running +10; 3 section(s) set aside until a failed fact-check is resolved.","score_delta":7,"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 707e74ef-9881-4247-9ef7-0362c29348c2
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>.