← Port3 Network5 decisions on this page
Audit log
Every state-changing event for Port3 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.
- #1publishby system:backfill2026-05-29 15:54:39ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 422,969,574
- sig
4irPhL4GvhKf…rh4TZNJuexplorer ↗- hash
38VqtvC1VwJz…j2ZQp3GAsha256 → base58
verifying row…full verify ↗canonical bytes (6856 B) ▸
{"actor":"system:backfill","investigation_id":"1b3b0823-c7ff-46a7-ac65-5870db5a63d3","kind":"publish","page_slug":"port3-network","published_at":"2026-05-29T15:54:39.518Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Port3 Network","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://beincrypto.com/port3-network-web3-social-data-gateway-accelerating-web2-migration/","type":"other","url":""},{"credibility":3,"name":"https://www.gate.com/learn/articles/what-is-port3-network/2164","type":"other","url":""},{"credibility":3,"name":"https://medium.com/@Port3/port3-network-decentralized-social-data-layer-for-web3-78d92743444e","type":"other","url":""},{"credibility":3,"name":"https://www.rootdata.com/member/Anthony%20Deng?k=MTQxODc%3D","type":"other","url":""},{"credibility":3,"name":"https://www.kucoin.com/announcement/en-port3-network-port3-gets-listed-on-kucoin-world-premiere","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.theblock.co/post/208066/kucoin-labs-backs-web3-social-data-portal-port3s-3-million-round","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/ico/port-3-network","type":"other","url":""},{"credibility":3,"name":"https://www.coincarp.com/project/port3-network/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://unchainedcrypto.com/port3-network-loses-13-million-in-token-bridge-exploit/","type":"other","url":""},{"credibility":3,"name":"https://nulltx.com/port3-exploit-triggers-full-token-migration-after-cross-chain-vulnerability-exposes-caterc20-weakness/","type":"other","url":""},{"credibility":3,"name":"https://www.bitget.com/news/detail/12560605077904","type":"other","url":""},{"credibility":3,"name":"https://www.bitget.com/news/detail/12560605078700","type":"other","url":""},{"credibility":3,"name":"https://www.weex.com/news/detail/port3-network-being-attacked-due-to-caterc20-vulnerability-will-release-a-new-token-to-fully-address-the-issue-238007","type":"other","url":""},{"credibility":3,"name":"https://phemex.com/news/article/port3-network-hacked-due-to-vulnerability-in-caterc20-token-solution-38622","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.okx.com/en-gb/learn/port3-token-migration-hack-details","type":"other","url":""},{"credibility":3,"name":"https://www.kucoin.com/news/flash/port3-network-token-migration-plan-launched-team-tokens-to-be-burned-to-offset-unauthorized-minting","type":"other","url":""},{"credibility":3,"name":"https://www.panewslab.com/en/articles/f6055e62-9e60-4789-aec3-41b38632990d","type":"other","url":""},{"credibility":3,"name":"https://intellectia.ai/news/crypto/port3-network-announces-token-migration-plan-after-security-breach","type":"other","url":""},{"credibility":3,"name":"https://www.coincarp.com/currencies/announcement/port3-network-port3-contract-migration/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.mexc.com/news/337145","type":"other","url":""},{"credibility":3,"name":"https://www.onesafe.io/blog/coinone-port3-delisting-security-breach","type":"other","url":""},{"credibility":3,"name":"https://support.kraken.com/articles/notice-of-scheduled-delistings-dec-2025","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/port3-network/","type":"other","url":""},{"credibility":3,"name":"https://www.coingecko.com/en/coins/port3-network","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cryptorank.io/price/port-3-network/vesting","type":"other","url":""},{"credibility":3,"name":"https://icodrops.com/port3-network/","type":"other","url":""},{"credibility":3,"name":"https://dropstab.com/coins/port3-network/vesting","type":"other","url":""},{"credibility":3,"name":"https://www.coincarp.com/currencies/port3-network/project-info/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://x.com/Port3Network/status/1742532619185840587","type":"other","url":""},{"credibility":3,"name":"https://medium.com/@Port3/port3-network-monthly-recap-january-the-great-rebuild-evolution-2f111a113595","type":"other","url":""}]}],"sources_used":[],"summary":"Port3 Network is a Web3 social data protocol and AI data layer founded in 2022, backed by KuCoin Ventures and Jump Crypto, with products including SoQuest, SoSignal, and SoPush targeting Web3 community engagement and data aggregation. In November 2025 the project suffered a critical exploit in which an attacker leveraged a boundary-condition vulnerability in the third-party CATERC20 cross-chain standard to mint approximately 1 billion unauthorized PORT3 tokens valued at roughly $13 million, triggering an 80% token price collapse and full contract migration. ZachXBT has flagged the entity, and the token has been delisted from at least one major exchange (Coinone) following the incident.","timeline":[{"date":"2022-01-01","event":"Port3 Network founded by Anthony Deng and Max Du, targeting Web3 social data aggregation.","source":""},{"date":"2023-02-01","event":"Port3 Network raises $3 million seed round led by KuCoin Ventures, with participation from Jump Crypto, SNZ, Adaverse, and others.","source":""},{"date":"2024-01-08","event":"PORT3 Token Generation Event (TGE) completed; token listed on KuCoin as World Premiere.","source":""},{"date":"2024-03-28","event":"PORT3 reaches all-time high price of approximately $0.3283.","source":""},{"date":"2024-10-21","event":"Undisclosed strategic funding round closes.","source":""},{"date":"2025-11-22","event":"Attacker exploits CATERC20 boundary-condition vulnerability at 20:56:24 UTC, minting 1 billion unauthorized PORT3 tokens valued at approximately $13 million. Token price drops approximately 80%.","source":""},{"date":"2025-11-23","event":"Port3 team confirms hack, removes on-chain liquidity, coordinates exchange suspensions, and announces 1:1 token migration plan with snapshot at 20:56 UTC.","source":""},{"date":"2025-12-24","event":"Coinone lists PORT3 among scheduled December 2025 delistings.","source":""},{"date":"2026-01-26","event":"Coinone formally delists PORT3, citing unresolved security concerns from the November exploit.","source":""},{"date":"2026-01-31","event":"Port3 Network completes BNB Chain token migration to new contract address 0xf6402bec11bd945bbd46be77e1fa5d477883f6c2.","source":""},{"date":"2026-02-01","event":"SoQuest platform enters maintenance mode; team describes January 2026 as a period of strategic rebuild.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 72442cf4-7409-4056-aeb1-b4c8f00e455f - #2rescoreby systemsystem2026-10-10 18:44:29ZScore: 38 → 58 (+20)Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 58. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −2.4; legitimacy credit long-running +8.anchoranchored
- chain
- ●mainnet-betaslot 455,364,239
- sig
2dXQZdURSJFd…CmT4LW15explorer ↗- hash
G8qqTuhNVZSG…iQDJAZWDsha256 → base58
verifying row…full verify ↗canonical bytes (644 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:44:29.145Z","decision":"rescore","investigation_id":"1b3b0823-c7ff-46a7-ac65-5870db5a63d3","new_score":58,"page_slug":"port3-network","prev_score":38,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 58. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −2.4; legitimacy credit long-running +8.","score_delta":20,"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 e2150e5a-c98d-4489-9aee-21aedb859bcb - #3reviewby reviewerreviewer2026-11-02 03:36:07ZScore: 58 → 58 (no score change)The core exploit narrative (CATERC20 flaw, 1B tokens minted, about 162M sold for about $166K, 80% drop, 1:1 BNB Chain migration with a 162.7M burn) is corroborated. Errors found: the Kraken December 2025 delisting claim is contradicted by Kraken's own notice, the attacker registration date (Nov 23) conflicts with Nov 22 elsewhere, and the Dec 24 Coinone timeline entry has no support. The ZachXBT flag is stated as fact in the summary but is unsourced and admitted unverified in the body. The cited onesafe URL no longer carries the Coinone article. Many funding, tokenomics and market-data claims were not checked.anchoranchored
- chain
- ●mainnet-betaslot 464,346,353
- sig
5CdHwDAeCrcB…epYvnqi4explorer ↗- hash
HCh3h6NmRQeZ…DvptbBb7sha256 → base58
verifying row…full verify ↗canonical bytes (1430 B) ▸
{"actor":"reviewer","artifact_identity":"621868989c910c3ba462c6869635c49b","decided_at":"2026-11-02T03:36:07.841Z","decision":"review","disputed_pct":0.6,"findings_hash":"6WiNKK1qS33ka1ARMBJLicAjVTS6rL61EbeNU8TpUxxL","investigation_id":"1b3b0823-c7ff-46a7-ac65-5870db5a63d3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_content_hash":"e68a926958f51701f20ca59e24176698b97cee8588754240d663193356bdc12e","page_slug":"port3-network","prev_score":58,"reason":"The core exploit narrative (CATERC20 flaw, 1B tokens minted, about 162M sold for about $166K, 80% drop, 1:1 BNB Chain migration with a 162.7M burn) is corroborated. Errors found: the Kraken December 2025 delisting claim is contradicted by Kraken's own notice, the attacker registration date (Nov 23) conflicts with Nov 22 elsewhere, and the Dec 24 Coinone timeline entry has no support. The ZachXBT flag is stated as fact in the summary but is unsourced and admitted unverified in the body. The cited onesafe URL no longer carries the Coinone article. Many funding, tokenomics and market-data claims were not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 60fc5095-f70a-4c27-a121-a7aca0b0a62a - #4review reviseby judgejudge2026-11-02 03:36:08ZScore: 58 → 58 (no score change)Of 10 checked claims, 2 were disputed and 4 could not be verified, giving 60% disputed or unverifiable, which sits on the line between the significant and failed bands. The core exploit account (CATERC20 flaw, 1 billion tokens minted, 80% price drop, 1:1 migration with burn) is confirmed (claim_findings[0], [6]), but claim_findings[4] shows the Kraken December 2025 delisting is contradicted by Kraken's own notice, claim_findings[1] gives a wrong attack date, and claim_findings[5], [8] and [9] leave a Coinone timeline entry and the ZachXBT flag (stated as fact in the summary) with no source. Because the reviewer's confidence is only 0.55 and the central allegation holds up, the page is revised at the top of the significant band rather than failed.anchoranchored
- chain
- ●mainnet-betaslot 464,346,357
- sig
2VDCYrcycseA…kCbmhfEyexplorer ↗- hash
8WQBtWzHq4dn…kCP2Cfjwsha256 → base58
verifying row…full verify ↗canonical bytes (2305 B) ▸
{"actor":"judge","artifact_identity":"621868989c910c3ba462c6869635c49b","band_override":{"actual_delta":-28,"actual_verdict":"review_revise","disputed_pct":0.6,"expected_delta_range":[-50,-30],"expected_verdict":"review_deny","rationale":"Of 10 checked claims, 2 were disputed and 4 could not be verified, giving 60% disputed or unverifiable, which sits on the line between the significant and failed bands. The core exploit account (CATERC20 flaw, 1 billion tokens minted, 80% price drop, 1:1 migration with burn) is confirmed (claim_findings[0], [6]), but claim_findings[4] shows the Kraken December 2025 delisting is contradicted by Kraken's own notice, claim_findings[1] gives a wrong attack date, and claim_findings[5], [8] and [9] leave a Coinone timeline entry and the ZachXBT flag (stated as fact in the summary) with no source. Because the reviewer's confidence is only 0.55 and the central allegation holds up, the page is revised at the top of the significant band rather than failed."},"decided_at":"2026-11-02T03:36:07.841Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.6,"investigation_id":"1b3b0823-c7ff-46a7-ac65-5870db5a63d3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_slug":"port3-network","prev_score":58,"reason":"Of 10 checked claims, 2 were disputed and 4 could not be verified, giving 60% disputed or unverifiable, which sits on the line between the significant and failed bands. The core exploit account (CATERC20 flaw, 1 billion tokens minted, 80% price drop, 1:1 migration with burn) is confirmed (claim_findings[0], [6]), but claim_findings[4] shows the Kraken December 2025 delisting is contradicted by Kraken's own notice, claim_findings[1] gives a wrong attack date, and claim_findings[5], [8] and [9] leave a Coinone timeline entry and the ZachXBT flag (stated as fact in the summary) with no source. Because the reviewer's confidence is only 0.55 and the central allegation holds up, the page is revised at the top of the significant band rather than failed.","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 3d511757-dc4e-402f-8308-1d963225c3db - #5rescoreby systemsystem2026-11-02 03:36:09ZScore: 58 → 64 (+6)Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 58 → 64. Problems weighed by who is responsible: concerns that are not fraud −6.4, problems around the subject, caused by others −2.4; legitimacy credit long-running +8; 2 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 464,346,362
- sig
2NRs41qXnNH7…7i76z1N9explorer ↗- hash
F55RJPezmhwV…CBLpei7Zsha256 → base58
verifying row…full verify ↗canonical bytes (717 B) ▸
{"actor":"system","decided_at":"2026-11-02T03:36:07.841Z","decision":"rescore","investigation_id":"1b3b0823-c7ff-46a7-ac65-5870db5a63d3","new_score":64,"page_slug":"port3-network","prev_score":58,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 58 → 64. Problems weighed by who is responsible: concerns that are not fraud −6.4, problems around the subject, caused by others −2.4; legitimacy credit long-running +8; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":6,"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 eb774807-a500-453e-9da3-e9ade9b1866f
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>.