Skip to main content
AVOID.NET
← PrismaLST5 decisions on this page

Audit log

Every state-changing event for PrismaLST: 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-20 15:27:01Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 421,012,601
    sig
    2vGoVP3RXqsM…U8RfJVDRexplorer ↗
    hash
    87GaV9gwajjL…ZyFf4qQKsha256 → base58
    verifying row…full verify ↗
    canonical bytes (6385 B) ▸
    {"actor":"system:backfill","investigation_id":"3dce0aa8-69c3-4cb1-9c80-b11a0b3c6b92","kind":"publish","page_slug":"prismalst","published_at":"2026-05-20T15:27:01.740Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"PrismaLST","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://prisma-finance.medium.com/prisma-finance-liquid-staking-08127169ff46"},{"credibility":3,"name":"","type":"other","url":"https://thedefiant.io/news/defi/prisma-introduces-ultra-stablecoin-backed-by-liquid-restaking-tokens"},{"credibility":3,"name":"","type":"other","url":"https://defillama.com/protocol/prisma-finance"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://hackmd.io/@PrismaRisk/PostMortem0328"},{"credibility":3,"name":"","type":"other","url":"https://www.certik.com/resources/blog/prisma-finance-incident-analysis"},{"credibility":3,"name":"","type":"other","url":"https://immunebytes.com/blog/prisma-finance-exploit-march-28-2024-detailed-analysis/"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/prisma-finance-exploited-10-million"},{"credibility":3,"name":"","type":"other","url":"https://thedefiant.io/news/defi/prisma-finance-suffers-usd12-million-exploit"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.coinspeaker.com/identity-prisma-finance-hacker/"},{"credibility":3,"name":"","type":"other","url":"https://crypto.news/blockchain-sleuth-uncovers-identity-of-prismafis-hacker-who-stole-11m/"},{"credibility":3,"name":"","type":"other","url":"https://www.theblock.co/post/285590/prismafi-hacker-moves-stolen-eth-tornado"},{"credibility":3,"name":"","type":"other","url":"https://hackmd.io/@PrismaRisk/PostMortem0328"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.theblock.co/post/285776/prisma-finance-hacker-defends-exploit-demands-public-apology"},{"credibility":3,"name":"","type":"other","url":"https://cryptobriefing.com/prisma-finance-hacker-apology-demand/"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/prisma-finance-540k-still-at-risk-hack-exploit-smart-contract"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/prisma-finance-protocol-restart-dao-vote"},{"credibility":3,"name":"","type":"other","url":"https://cryptonews.com/news/prisma-finance-gains-strong-community-support-for-protocol-restart-with-dao-approval/"},{"credibility":3,"name":"","type":"other","url":"https://defillama.com/protocol/prisma-finance"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://olympix.ai/blog/prismas-11-6m-exploit-was-a-trust-trap-and-olympix-would-have-triggered-it"},{"credibility":3,"name":"","type":"other","url":"https://quadrigainitiative.com/casestudy/prismafinancetrovemanagerexploit.php"},{"credibility":3,"name":"","type":"other","url":"https://cryptoslate.com/prisma-finances-11-6-million-exploit-leads-to-asset-value-plummet-mkusd-stablecoin-instability/"},{"credibility":3,"name":"","type":"other","url":"https://www.fxstreet.com/cryptocurrencies/news/prisma-finance-hacker-could-be-uncovered-after-investigations-by-on-chain-analyst-202404162351"}]}],"sources_used":[],"summary":"Prisma Finance is a Liquity-forked, Ethereum-based DeFi protocol that allowed users to mint overcollateralized stablecoins (mkUSD and ULTRA) against liquid staking tokens (LSTs) such as wstETH, rETH, sfrxETH, and cbETH. On March 28, 2024, a critical vulnerability in the protocol's MigrateTroveZap helper contract was exploited for approximately $11.6 million, with a total loss across all attacker wallets of roughly $12.3 million; the primary exploiter sent the majority of stolen funds through Tornado Cash while claiming a 'whitehat rescue,' and as of 2026 the protocol's TVL has collapsed from a pre-exploit peak of approximately $220 million to under $300K.","timeline":[{"date":"2023-09-01","event":"Prisma Finance launches on Ethereum mainnet, offering LST-backed stablecoin minting via mkUSD.","source":""},{"date":"2024-01-01","event":"Prisma introduces ULTRA, a second stablecoin backed by liquid restaking tokens (LRTs).","source":""},{"date":"2024-03-28","event":"Exploit begins at 11:25 UTC. Primary attacker (EOA 0x7E39E3B3ff7ADef2613d5Cc49558EAB74B9a4202) exploits MigrateTroveZap vulnerability, draining approximately $11.6 million. Two copycat attackers follow, bringing total losses to approximately $12.3 million.","source":""},{"date":"2024-03-28","event":"Emergency multisig pauses Prisma protocol at 12:51 UTC. Official post states mkUSD and ULTRA stablecoins remain overcollateralized and are not at immediate risk.","source":""},{"date":"2024-03-29","event":"Attacker-linked wallets begin routing stolen ETH through Tornado Cash. Approximately 1,850 ETH confirmed through the mixing protocol.","source":""},{"date":"2024-03-31","event":"Primary attacker sends on-chain messages claiming 'white hat rescue' and demanding a public press conference, team doxing, and a formal apology before discussing fund return.","source":""},{"date":"2024-04-01","event":"Prisma Finance confirms approximately $540,000 in user funds remain at risk. Disputes attacker's white hat framing given Tornado Cash deposits.","source":""},{"date":"2024-04-05","event":"Core contributor Frank Olson proposes plan to safely unpause the protocol. DAO governance vote yields 100% approval to resume operations.","source":""},{"date":"2024-04-06","event":"Prisma Finance resumes operations following a post-exploit security audit. Users can again deposit LST/LRT collateral and mint stablecoins.","source":""},{"date":"2024-04-16","event":"ZachXBT publishes investigation alleging identification of primary exploiter, linking wallet funding to FixedFloat, Bybit, and TRON withdrawals, and connecting the attacker to prior exploits including Arcade_xyz and Pine Protocol.","source":""},{"date":"2026-05-01","event":"DeFiLlama data shows Prisma Finance TVL below $300,000, down from a pre-exploit peak of approximately $220 million, indicating near-total user exit from the protocol.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision ee867975-1234-4214-b4cc-26ef47cfb280
  2. #2rescoreby systemsystem
    2026-10-10 18:48:40Z
    Score: 10 → 55 (+45)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 55. Problems weighed by who is responsible: incidents the subject suffered −12.8, problems around the subject, caused by others −0.8; legitimacy credit long-running +4.
    anchoranchored
    chain
    ●mainnet-betaslot 455,368,596
    sig
    3qADrwvy1U7J…cpT1JkkNexplorer ↗
    hash
    DL7UkSxWaUf1…pWcxQYmVsha256 → base58
    verifying row…full verify ↗
    canonical bytes (607 B) ▸
    {"actor":"system","decided_at":"2026-10-10T18:48:40.031Z","decision":"rescore","investigation_id":"3dce0aa8-69c3-4cb1-9c80-b11a0b3c6b92","new_score":55,"page_slug":"prismalst","prev_score":10,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 55. Problems weighed by who is responsible: incidents the subject suffered −12.8, problems around the subject, caused by others −0.8; legitimacy credit long-running +4.","score_delta":45,"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 fe380cab-be0a-482b-b89a-3a25f3a602d0
  3. #3reviewby reviewerreviewer
    2026-11-02 09:37:36Z
    Score: 55 → 55 (no score change)
    The core exploit facts (time, pause time, addresses, 3,479 ETH total loss) match the official post-mortem. The 'pre-exploit peak' TVL framing is doubtful and the current TVL could not be verified. Several secondary claims were not checked, such as the DAO vote percentage, ZachXBT allegations and the flash loan amount. The page omits the Resupply migration and shutdown proposal and the reimbursement plan, which materially affect how the protocol's current state should be read.
    anchoranchored
    chain
    ●mainnet-betaslot 464,447,524
    sig
    unmUbcvsfQdq…UBuRbHshexplorer ↗
    hash
    85JTL17tL88H…WJUtVLjEsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1326 B) ▸
    {"actor":"reviewer","artifact_identity":"794c9109141265cafd8a7ab6c9682ef4","decided_at":"2026-11-02T09:37:36.613Z","decision":"review","disputed_pct":0.3333,"findings_hash":"6jZo6eQuTq2ib28BKUAqUnuuyRBg86H4g8apHgeWmYky","investigation_id":"3dce0aa8-69c3-4cb1-9c80-b11a0b3c6b92","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"omissions":{"material":2,"total":2},"page_content_hash":"8c287927d823dce7925374990852c908adadf1fb409a64382d281b7fd82bf452","page_slug":"prismalst","prev_score":55,"reason":"The core exploit facts (time, pause time, addresses, 3,479 ETH total loss) match the official post-mortem. The 'pre-exploit peak' TVL framing is doubtful and the current TVL could not be verified. Several secondary claims were not checked, such as the DAO vote percentage, ZachXBT allegations and the flash loan amount. The page omits the Resupply migration and shutdown proposal and the reimbursement plan, which materially affect how the protocol's current state should be read.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":true,"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 3c05a551-6982-47f8-83ab-deeb4af38fe4
  4. #4review reviseby judgejudge
    2026-11-02 09:37:36Z
    Score: 55 → 55 (no score change)
    The core exploit facts (timing, pause time, attacker address and the 3,479 ETH total loss) match the official post-mortem (claim_findings[0-2]). Three of nine claims could not be verified (the flash loan amount, the DAO vote percentage and the ZachXBT legal-proceedings claim, claim_findings[3, 7, 8]), which puts the unverified share at about 33%. The 'pre-exploit peak' TVL framing is doubtful and the current TVL figure could not be checked (claim_findings[6]). The page also omits the shutdown proposal and Resupply migration and the user reimbursement plan, both rated material. Because reviewer confidence is moderate and no core allegation was disputed, the penalty is set in the lower-middle of the significant band.
    anchoranchored
    chain
    ●mainnet-betaslot 464,447,529
    sig
    4pAK1phwt6ba…74EiWeyoexplorer ↗
    hash
    5iVKqXHyH1uv…aP5PapzSsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1780 B) ▸
    {"actor":"judge","artifact_identity":"794c9109141265cafd8a7ab6c9682ef4","band_override":null,"decided_at":"2026-11-02T09:37:36.613Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"3dce0aa8-69c3-4cb1-9c80-b11a0b3c6b92","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_slug":"prismalst","prev_score":55,"reason":"The core exploit facts (timing, pause time, attacker address and the 3,479 ETH total loss) match the official post-mortem (claim_findings[0-2]). Three of nine claims could not be verified (the flash loan amount, the DAO vote percentage and the ZachXBT legal-proceedings claim, claim_findings[3, 7, 8]), which puts the unverified share at about 33%. The 'pre-exploit peak' TVL framing is doubtful and the current TVL figure could not be checked (claim_findings[6]). The page also omits the shutdown proposal and Resupply migration and the user reimbursement plan, both rated material. Because reviewer confidence is moderate and no core allegation was disputed, the penalty is set in the lower-middle of the significant band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports two material omissions (the PIP-46 shutdown proposal and Resupply migration, and the DAO user reimbursement plan) and says the page's current-state picture is contradicted. The page's silence on the wind-down changes how readers interpret the low TVL, so the page is judged in the significant band."},"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 9473c43a-92ed-4f93-b16c-d9e2ab27ab7a
  5. #5rescoreby systemsystem
    2026-11-02 09:37:37Z
    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: incidents the subject suffered −9.6, problems around the subject, caused by others −0.8; legitimacy credit long-running +4; 1 section(s) set aside until a failed fact-check is resolved.
    anchoranchored
    chain
    ●mainnet-betaslot 464,447,675
    sig
    XgJV515LxQnf…UVbiV2Pxexplorer ↗
    hash
    8X1VaAFdZqJ8…R3YzG7yvsha256 → base58
    verifying row…full verify ↗
    canonical bytes (716 B) ▸
    {"actor":"system","decided_at":"2026-11-02T09:37:36.613Z","decision":"rescore","investigation_id":"3dce0aa8-69c3-4cb1-9c80-b11a0b3c6b92","new_score":59,"page_slug":"prismalst","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: incidents the subject suffered −9.6, problems around the subject, caused by others −0.8; legitimacy credit long-running +4; 1 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 d5bfd564-a48f-4428-af97-1ae6d23e686e
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>.