Audit log

Every state-changing event for Unleash Protocol: 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-26 19:42:36Z
   Score: ? → ? (no score change)
   anchoranchored

   chain

   ●mainnet-betaslot 422,349,677

   sig

   5t33CncG6wmq…rGoLxyBbcopyexplorer ↗

   hash

   5dDYvSMt4j2n…jYxofEqNcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (6079 B) ▸

   {"actor":"system:backfill","investigation_id":"52ea6c6f-9de0-4ac0-809e-729d8224fa64","kind":"publish","page_slug":"unleash-protocol","published_at":"2026-05-26T19:42:35.984Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Unleash Protocol","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/business/2025/12/30/unleash-protocol-hit-by-usd3-9-million-exploit-with-funds-routed-through-tornado-cash","type":"other","url":""},{"credibility":3,"name":"https://www.bleepingcomputer.com/news/security/hackers-drain-39m-from-unleash-protocol-after-multisig-hijack/","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/news/unleash-protocol-hack-drains-3-9m-after-multisig-exploit-peckshield-reveals/","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/academy/article/unleash-protocol-loses-dollar39m-in-governance-exploit","type":"other","url":""},{"credibility":3,"name":"https://www.scorechain.com/blog/unleash-protocol-incident-shows-how-governance-failures-escalate-risk","type":"other","url":""},{"credibility":3,"name":"https://coinjournal.net/news/how-a-governance-failure-led-to-the-unleash-protocol-hack/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://coinjournal.net/news/how-a-governance-failure-led-to-the-unleash-protocol-hack/","type":"other","url":""},{"credibility":3,"name":"https://www.scorechain.com/blog/unleash-protocol-incident-shows-how-governance-failures-escalate-risk","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/news/unleash-protocol-hack-drains-3-9m-after-multisig-exploit-peckshield-reveals/","type":"other","url":""},{"credibility":3,"name":"https://www.bleepingcomputer.com/news/security/hackers-drain-39m-from-unleash-protocol-after-multisig-hijack/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/business/2025/12/30/unleash-protocol-hit-by-usd3-9-million-exploit-with-funds-routed-through-tornado-cash","type":"other","url":""},{"credibility":3,"name":"https://www.bleepingcomputer.com/news/security/hackers-drain-39m-from-unleash-protocol-after-multisig-hijack/","type":"other","url":""},{"credibility":3,"name":"https://www.cryptotimes.io/2025/12/31/unleash-protocol-exploit-3-9m-stolen-via-multisig-governance-breach/","type":"other","url":""},{"credibility":3,"name":"https://www.scorechain.com/blog/unleash-protocol-incident-shows-how-governance-failures-escalate-risk","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.bleepingcomputer.com/news/security/hackers-drain-39m-from-unleash-protocol-after-multisig-hijack/","type":"other","url":""},{"credibility":3,"name":"https://www.cryptopolitan.com/unleash-protocol-unauthorized-withdrawals/","type":"other","url":""},{"credibility":3,"name":"https://defillama.com/protocol/unleash-protocol","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/news/unleash-protocol-hack-drains-3-9m-after-multisig-exploit-peckshield-reveals/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://docs.unleashprotocol.xyz/others/team","type":"other","url":""},{"credibility":3,"name":"https://coinjournal.net/news/how-a-governance-failure-led-to-the-unleash-protocol-hack/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://bitcoinethereumnews.com/tech/unleash-protocol-exploit-causes-3-9m-loss-ip-token-dips-on-story-concerns/","type":"other","url":""},{"credibility":3,"name":"https://defillama.com/protocol/unleash-protocol","type":"other","url":""},{"credibility":3,"name":"https://www.scworld.com/brief/crypto-heist-pilfers-about-3-9m-from-unleash-protocol","type":"other","url":""},{"credibility":3,"name":"https://www.cryptotimes.io/2025/12/31/unleash-protocol-exploit-3-9m-stolen-via-multisig-governance-breach/","type":"other","url":""}]}],"sources_used":[],"summary":"Unleash Protocol is a decentralized intellectual property finance (IPFi) platform built on the Story Protocol blockchain, launched in early 2024. On December 30, 2025, the protocol suffered a confirmed $3.9 million exploit in which an attacker gained unauthorized administrative control through its multisignature governance system, executed an unauthorized smart contract upgrade, and laundered 1,337 ETH through Tornado Cash. The protocol subsequently paused all operations; as of early 2026 no recovery or user compensation plan has been publicly confirmed.","timeline":[{"date":"2024-01-01","event":"Unleash Protocol founded by 11-member team, positioning as an IPFi (Intellectual Property Finance) platform on Story Protocol.","source":""},{"date":"2025-12-30","event":"Attacker gains unauthorized administrative control via Unleash Protocol's multisig governance system, executes unapproved contract upgrade, and drains approximately $3.9M in WIP, USDC, WETH, stIP, and vIP tokens.","source":""},{"date":"2025-12-30","event":"PeckShieldAlert and CertiK flag the incident publicly. Attacker bridges stolen assets to Ethereum and begins depositing 1,337.1 ETH into Tornado Cash across 34 structured transactions over 11–12 hours.","source":""},{"date":"2025-12-30","event":"Unleash Protocol announces the breach on X (formerly Twitter), pauses all operations, and advises users to halt all contract interactions. States no compromise to Story Protocol infrastructure.","source":""},{"date":"2025-12-31","event":"Multiple security outlets including BleepingComputer, CoinDesk, and Coinpedia publish detailed coverage. LookonChain and Scorechain confirm governance-layer root cause.","source":""},{"date":"2026-01-01","event":"Unleash Protocol TVL recorded at $0 on DefiLlama. No user compensation or recovery timeline announced as of available reporting.","source":""}]},"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 9ad7efcb-0d74-4c20-8167-016efc64d6abcopy
2. #2rescoreby systemsystem

   2026-10-10 18:48:45Z
   Score: 18 → 55 (+37)
   Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 55. Problems weighed by who is responsible: incidents the subject suffered −6.4, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +4.
   anchoranchored

   chain

   ●mainnet-betaslot 455,368,625

   sig

   ipuiWR4SSxRD…XQHK4uZfcopyexplorer ↗

   hash

   5xBWiWFu1Pnt…5ZZp5RPocopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (647 B) ▸

   {"actor":"system","decided_at":"2026-10-10T18:48:45.605Z","decision":"rescore","investigation_id":"52ea6c6f-9de0-4ac0-809e-729d8224fa64","new_score":55,"page_slug":"unleash-protocol","prev_score":18,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 55. Problems weighed by who is responsible: incidents the subject suffered −6.4, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +4.","score_delta":37,"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 3d74fea1-995f-4bc3-9abd-43fc2fb16b36copy
3. #3reviewby reviewerreviewer

   2026-11-02 09:35:46Z
   Score: 55 → 55 (no score change)
   The core incident (about $3.9M, multisig takeover, unauthorized upgrade, 1,337 ETH to Tornado Cash, operations paused, no recovery plan) is well corroborated. The 34-transaction and 11-12 hour detail was not found in the sources I read. The launch date and team page are unverifiable, and the cited team docs URL now 404s. Several sources were not fetched, such as DefiLlama and the TVL figures.
   anchoranchored

   chain

   ●mainnet-betaslot 464,447,071

   sig

   65KKxcSakqy1…DjzXvBBGcopyexplorer ↗

   hash

   CfSPrayuVWvf…2aWmAM4Kcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1250 B) ▸

   {"actor":"reviewer","artifact_identity":"3adb14428f4c50941090a50551fc5724","blocked_count":1,"decided_at":"2026-11-02T09:35:46.113Z","decision":"review","disputed_pct":0.3333,"findings_hash":"G5p5HvTtuFdrAXWtRJfTLayw2cV4TgYTzFdxf9G3MyQK","investigation_id":"52ea6c6f-9de0-4ac0-809e-729d8224fa64","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_content_hash":"892e791bcf3b210e7035e396875b290622ab08bb515ccd04f3970a510e3d7e20","page_slug":"unleash-protocol","prev_score":55,"reason":"The core incident (about $3.9M, multisig takeover, unauthorized upgrade, 1,337 ETH to Tornado Cash, operations paused, no recovery plan) is well corroborated. The 34-transaction and 11-12 hour detail was not found in the sources I read. The launch date and team page are unverifiable, and the cited team docs URL now 404s. Several sources were not fetched, such as DefiLlama and the TVL figures.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"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 07f9501d-0652-42f2-ad0f-34c7d34a986dcopy
4. #4review reviseby judgejudge

   2026-11-02 09:35:46Z
   Score: 55 → 55 (no score change)
   The core incident (about $3.9M lost through a multisig takeover and unauthorized upgrade, 1,337 ETH sent to Tornado Cash, operations paused, no recovery plan) is confirmed by independent outlets (claim_findings[0], [2], [3]). Two of six scored claims could not be verified: the 34-transaction, 11-12 hour Tornado Cash detail was not found in the sources read (claim_findings[1]), and the early-2024 launch and team description rests on an official docs page that now returns 404 (claim_findings[4], [5]). That puts the unverifiable share at about 33%, in the significant-issues band. Because the unverified items are peripheral, the penalty sits at the mild end of the band. One TVL claim was not scored because the source blocked the reviewer, which limits coverage but is not a defect of the page. The reviewer's confidence was moderate (0.55) and no omissions or status contradictions were found.
   anchoranchored

   chain

   ●mainnet-betaslot 464,447,076

   sig

   5jmBadq1ULHE…Da91DKsEcopyexplorer ↗

   hash

   24brMV5G4ZCg…YmvUuQQBcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1585 B) ▸

   {"actor":"judge","artifact_identity":"3adb14428f4c50941090a50551fc5724","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T09:35:46.113Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"52ea6c6f-9de0-4ac0-809e-729d8224fa64","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_slug":"unleash-protocol","prev_score":55,"reason":"The core incident (about $3.9M lost through a multisig takeover and unauthorized upgrade, 1,337 ETH sent to Tornado Cash, operations paused, no recovery plan) is confirmed by independent outlets (claim_findings[0], [2], [3]). Two of six scored claims could not be verified: the 34-transaction, 11-12 hour Tornado Cash detail was not found in the sources read (claim_findings[1]), and the early-2024 launch and team description rests on an official docs page that now returns 404 (claim_findings[4], [5]). That puts the unverifiable share at about 33%, in the significant-issues band. Because the unverified items are peripheral, the penalty sits at the mild end of the band. One TVL claim was not scored because the source blocked the reviewer, which limits coverage but is not a defect of the page. The reviewer's confidence was moderate (0.55) and no omissions or status contradictions were found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"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 8c7857f6-99d2-47d9-9cf5-1255bc8d18d8copy
5. #5rescoreby systemsystem

   2026-11-02 09:35:47Z
   Score: 55 → 59 (+4)
   Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 55 → 59. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +4; 2 section(s) set aside until a failed fact-check is resolved.
   anchoranchored

   chain

   ●mainnet-betaslot 464,447,080

   sig

   4h51nxKCLqUg…jNMCBtbocopyexplorer ↗

   hash

   5JsDLvr3LNkS…rWK6QWwRcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (757 B) ▸

   {"actor":"system","decided_at":"2026-11-02T09:35:46.113Z","decision":"rescore","investigation_id":"52ea6c6f-9de0-4ac0-809e-729d8224fa64","new_score":59,"page_slug":"unleash-protocol","prev_score":55,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 55 → 59. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +4; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":4,"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 2336f499-4da5-4a1d-9c54-fb04e6b8bcaccopy