Skip to content
PlutusShield
Live on Cardano Preview testnet

Evidence vault

Exploit cover can't settle on an oracle, so claims are assessed. Seal your evidence here: it's encrypted on this device, and only a commitment is meant for the Midnight ledger.

← Back to site

← Depeg claim checker

Midnight · Lace

Not connected

Connect Lace Midnight on Preprod. proveCover / fileClaim from the browser are next; use the claim kit until then.

Midnight · DApp Connector 4.0.1 · Preprod

Connect Lace Midnight

Connect Lace's Midnight edition on Preprod. This reads your address and service URIs, and /claim/evidence drives the Lace circuit-submit path for proveCover / fileClaim (hints, proving strategy, balance + submit). Compact prove uses the local holder prove bridge; until the first finalized File-with-Lace drill tx, use the holder claim kit on that page.

Looking for Midnight wallets…

Connecting is read-only for now: PlutusShield reads your Midnight network, addresses, and Lace service URIs, and never sees your keys. Circuit submits from this wallet are next.

Exploit claim · evidence bundle

1 · Policy and protocol

The 32-byte id of your exploit-cover policy (64 hex). It keys the claim on Midnight.

Chain

Script hashes, script addresses, or validator names. One per line.

2 · What happened
Incident type

How the exploit worked and how it affected your position.

Your local time. The bundle stores UTC.

32-byte transaction ids (64 hex), one per line.

3 · Loss and attachments

Only each file's name, size and SHA-256 go into the bundle. Keep the files: the assessor checks them against these hashes.

Runs in this browser with WebCrypto. Nothing is uploaded.

How the vault works

  1. 1

    Canonical bundle

    Your answers become one deterministic JSON document (sorted keys, normalized hex, UTC times).

  2. 2

    Commit

    commitment = SHA-256("plutusshield:evidence:v1" ‖ SHA-256(bundle) ‖ salt), the contract's evidenceCommitment.

  3. 3

    Encrypt

    AES-256-GCM under a fresh random key. You download the encrypted bundle and a separate key file.

  4. 4

    File, then disclose

    Only the commitment goes to fileClaim on Midnight. You hand the two files to the assessor privately.

Nothing leaves this browser. There is no server and no upload; reload the page and it's gone.

Assessor

Open and verify a bundle

Load the encrypted bundle and key file the claimant sent you, paste the evidence commitment from the policy's Midnight record, and check that this is exactly the evidence that was filed. Decryption runs here.

From the policy's PolicyRecord.evidence on Midnight (64 hex).

Matched against the committed SHA-256 hashes.

Results appear here. Each step is checked separately so you can see exactly what fails.

Private by construction

The bundle is encrypted before it exists anywhere but this tab. The Midnight ledger only ever sees a 32-byte commitment, salted so nobody can confirm a guess about its contents.

Binding for the claimant

Once a commitment is filed, the claimant can't swap the evidence. Any change to the bundle, even one character, produces a different commitment and fails the assessor's check.

Disclosed only to the assessors

You choose who gets the key file. Today that's an off-ledger handoff to the assessor committee. The registry keeps the commitment on an approved claim and clears it on a rejected one.

After you file

How a filed commitment is resolved.

The registry can't read your evidence, so it can't judge it. It can make sure the committee judges exactly what you filed, and that only the committee can decide it.

  1. 1 · Seal

    Claimant, this page

    The bundle is serialized canonically, hashed, and committed with a fresh 32-byte salt: evidenceCommitment = SHA-256(tag ‖ digest ‖ salt). You keep the encrypted bundle and the key file.

  2. 2 · fileClaim

    Holder, on Midnight

    The holder proves in zero knowledge that their policy key opens the record's holder commitment, and the ledger stores only the 32-byte evidence commitment. Status: ACTIVE → CLAIM_PENDING.

  3. 3 · Verify off-ledger

    Assessor committee

    With the bundle and key file, each committee member checks four things: it decrypts, it's a canonical exploit bundle, it opens to its commitment, and that commitment is byte-for-byte the one on the ledger. Anything else is refused before a vote.

  4. 4 · voteClaim

    Committee, on Midnight (v2)

    Each member votes once per claim round; only a seat's role commitment passes the circuit. 2-of-3 approvals → PAID, commitment kept. 2-of-3 rejections → back to ACTIVE, commitment cleared, so a re-filing with a new salt can't be linked to it. The drill below ran on v1, where a single assessor decided by resolveClaim.

Live claims drill · Midnight Preprod

Test policies, demo evidence. No real incident, no real funds.

Policy (Cardano Preview Buy)fileClaimresolveClaimStatus nowCardano payout
72512fac…d745d0Buy 7c3365bb…31386d ↗USDM depeg cover · 50 tADAb5120dd0…0ba1af · block 2,867,361evidence ca7e8da3…622b30cdd32797…632511 · block 2,867,365Approved → PAIDMirrored · ACTIVE on Midnightv2None: depeg pool (oracle-only settle)
a33af805…3b2b3dBuy 1e70f089…0f321f ↗USDM depeg cover · 20 tADAe9878f89…695425 · block 2,867,368evidence dcdd60be…a13721e7a4b0e2…9b9a68 · block 2,867,372Rejected → ACTIVE, evidence clearedMirrored · ACTIVE on Midnightv2None: rejected
c6adbe88…e8648aBuy 4ed98579…9a77e4 ↗Exploit cover · 50 tADAe991bd47…2ea919 · block 2,869,252evidence b05e660e…0f2d7a71d86cd5…3c76e0 · block 2,869,256Approved → PAIDClaim approved · PAID on Midnightv1Paid on Cardano PreviewSettle c35535dd…99ab38 ↗50 tADA, 2-of-3 assessor committee
4db47733…475b19Buy 30281045…16946e ↗Exploit cover · 50 tADA6c008639…010733 · block 2,868,307evidence 3753efd0…1260ad0e6fc759…43ee19 · block 2,868,310Approved → PAIDClaim approved · PAID on Midnightv1Paid on Cardano PreviewSettle 5509c2d9…21cce8 ↗50 tADA, single assessor (v1 pool)

Every bundle was sealed with this page's code (packages/sdk/src/evidence.ts) and checked by the assessor against the on-ledger commitment before each resolveClaim on the v1 registry. “Status now” is decoded live from the registry's public state on the Preprod indexer.

Payout wired for exploit cover. The depeg pool still settles only on an oracle quorum (its parameters are fixed, no admin key), so approved claims on depeg policies stay unpaid on Cardano. Exploit policies live in a separate exploit-cover pool whose Settle needs signatures from 2 of the 3 assessors on its committee, so an approved Midnight claim there is paid in ADA or USDC on Cardano Preview. See the payout.

Exploit cover · Cardano Preview

Approved on Midnight. Paid on Cardano.

A separate exploit-cover pool settles assessed claims. Its validator pays only when 2 of the 3 assessor keys fixed in its parameters sign the Settle, and each assessor signs only after the Midnight registry shows the claim approved. Claims on the live v2 registry are approved by committee voteClaim; the payouts recorded below were approved on v1, and their Settles name that resolveClaim tx in their metadata.

Payouts on Preview

3

  1. 1 · Buy

    Cardano

    Exploit cover is bought from its own pool. No oracle peg check: only the waiting period guards the sale.

  2. 2 · fileClaim

    Midnight

    The holder files a sealed evidence commitment against the policy in zero knowledge.

  3. 3 · voteClaim

    Midnight

    Committee members open the bundle off-ledger, check it against the commitment, and vote: 2-of-3 approvals mark the claim PAID on the live v2 registry. The newest payout below was decided that way, on a claim the holder filed from their own claim kit; the earlier ones were decided on v1 by resolveClaim.

  4. 4 · Settle

    Cardano

    2 of the 3 committee assessors each check the Midnight record and co-sign. The validator counts distinct committee signatures, then pays exactly the coverage and burns the policy.

Assessor committee · fixed in the script parameters

2-of-3 signatures release a payout

No single key can pay a claim. A lost or rogue key can be outvoted.

Below the threshold, the Settle can't exist.

1-of-3 (#2) against policy c6adbe88…e8648a: rejected by lucid-evolution local UPLC evaluator and by the provider evaluator (Blockfrost /utils/txs/evaluate) on Preview. Nothing was submitted, so there is no tx hash: the script fails before a transaction can be built.

Pool v2 · 2-of-3 assessor committee · current
Exploit policy (Cardano Preview)Midnight decisionCardano payout
c6adbe88…e8648aBuy 4ed98579…9a77e4 ↗50 tADA cover · premium 5 tADA71d86cd5…3c76e0block 2,869,256Approved → PAID (v1)Paid on Cardano PreviewSettle c35535dd…99ab38 ↗50 tADA to the holder · signed by #1 + #3 (2-of-3)
496dced8…39a594Buy 9e261a3d…2d5439 ↗25 tADA cover · premium 5 tADAbeb6d9f5…7470cfblock 2,953,3812 of 3 seats approved → PAID (v2)Filed by the holder from a claim kitPaid on Cardano PreviewSettle dbf0ba7a…ba15e0 ↗25 tADA to the holder · signed by #1 + #3 (2-of-3)
9bdef8cb…f076aeBuy 3c1fc629…547fff ↗10 tADA cover · premium 5 tADAClaim pending on MidnightAwaiting 2-of-3 committee signatures
Pool v1 · single assessor key · history (superseded by v2)
Exploit policy (Cardano Preview)Midnight decisionCardano payout
4db47733…475b19Buy 30281045…16946e ↗50 tADA cover · premium 5 tADA0e6fc759…43ee19block 2,868,310Approved → PAID (v1)Paid on Cardano PreviewSettle 5509c2d9…21cce8 ↗50 tADA to the holder · single-assessor signature (v1)
Exploit pool v2 script
097ba40a…7994f0 ↗
v1 pool (single assessor)
ef2f1001…b9509c ↗
Terms
4.50% base · 30–365 days
Sale and claim window
10 min wait · 3-day grace

Trust model, plainly: Cardano can't read Midnight, so the committee's signatures are the bridge. The validator counts distinct committee members among the tx signers (outsiders and repeats don't count) and needs 2 of 3; it enforces everything else (exact coverage from the policy's tranche, both policy tokens burned, active cover released, claim window). The payouts above were decided on the v1 Midnight registry, where resolveClaim is one assessor role key — that alone couldn't move Cardano capital. The live v2 registry decides by 2-of-3 committee voteClaim instead. The three Cardano committee keys are Preview keys run by the PlutusShield team today, not yet independent operators. Test value only, not audited.

Claims committee · Midnight Preprod · policy-cover v2

2-of-3 on Midnight, 2-of-3 on Cardano.

v2 replaces the single-assessor resolveClaim with voteClaim. Each committee member proves its seat by opening one of three public role commitments inside the circuit. 2 approvals mark the claim PAID, 2 rejections send it back to ACTIVE with the evidence cleared, and a split vote waits for the last seat. One vote per seat per claim round, every vote on the public ledger.

Committee votes on Preprod

5

  • Seat #0 · role commitment

    9371bf48…b6461f

    Approved, Approved

  • Seat #1 · role commitment

    c0aa4178…07d44f

    Rejected

  • Seat #2 · role commitment

    592b8621…165caf

    Approved, Approved

v2 ledger, read from the Preprod indexer

Snapshot

Policies
4
Cover proofs
4
Claims filed
2
Committee votes
5
  • Policy7c24be86…468ccbon the ledger now:PAID· claim round 1
  • Policy496dced8…39a594on the ledger now:PAID· claim round 1
  1. voteClaimCommittee seat votedbeb6d9f5…7470cf · block 2,953,381
  2. voteClaimCommittee seat votedcefd3f5a…7973f1 · block 2,953,377
  3. fileClaimClaim filed with sealed evidence00989a6a…873630 · block 2,953,373
  4. proveCoverCover proven in zero knowledge1778409d…056918 · block 2,953,369
  5. registerPolicyPolicy mirrored from Cardano21de296c…c92df0 · block 2,953,364
Policy 7c24be86…468ccb · Cardano Preview Buy 94c4dc05…1325ff ↗
StepWhoMidnight txTally after (approve · reject)Status
registerPolicyIssuerec1e22e7…7acdcbBinding to the Cardano datum re-checked in circuitACTIVE
proveCoverHolder4b0e0fc2…fefb20Cover proven without revealing amount or holderACTIVE
fileClaimHolder96e17dfa…41c6c0Evidence commitment 013e08eb…996ac1CLAIM_PENDING
voteClaim · approveSeat #0 9371bf48…b6461fdb60e9d7…2dfc4eblock 2,870,333·Pending
voteClaim · rejectSeat #1 c0aa4178…07d44fb0271165…0cedfcblock 2,870,337·Pending
voteClaim · approveSeat #2 592b8621…165cafbd62e689…2f7d74block 2,870,341·PAID
Policy 496dced8…39a594 · Cardano Preview Buy 9e261a3d…2d5439 ↗
StepWhoMidnight txTally after (approve · reject)Status
registerPolicyIssuer21de296c…c92df0Binding to the Cardano datum re-checked in circuitACTIVE
proveCoverHolder1778409d…056918Cover proven without revealing amount or holderACTIVE
fileClaimHolder00989a6a…873630Evidence commitment 9260a87e…019fecCLAIM_PENDING
voteClaim · approveSeat #0 9371bf48…b6461fcefd3f5a…7973f1block 2,953,377·Pending
voteClaim · approveSeat #2 592b8621…165cafbeb6d9f5…7470cfblock 2,953,381·PAID
v2 contract
5430b803…eb8110
Deploy tx
00532855…aba6d4block 2,870,317
Compiler
compactc 0.31.1

Trust model, plainly: the three seat secrets are held by the PlutusShield team on Preprod today, not yet by independent operators. Each seat checks the sealed evidence off-ledger before voting. Demo evidence and test policies only, not audited.

The live registry on Midnight Preprod is the v2 committee contract (policy-cover-v2.compact); the claims drill above ran fileClaim and resolveClaim on the v1 registry (policy-cover.compact) from the operator relay, and is kept as its history. Lace Midnight connect is live on this page (Preprod address + Lace service URIs). The evidence vault now drives the Lace circuit-submit path for proveCover / fileClaim (proving strategy, prover health, permission hints, balance + submit via the connector). Compact prove comes from the local holder prove bridge (pnpm midnight:prove-bridge); File with Lace uses it automatically when it is up. Without the bridge, seal the bundle or download the holder claim kit for policy-cover-preprod.mjs --claim … --kit …. Exploit cover is bought in the browser on /cover from the Preview exploit pool (your Midnight key is saved in this browser for this page), and an approved claim is paid on Cardano by a Settle signed by 2 of the 3 assessors on the pool's committee. Read the vault's trust model and the assessed claim flow.