Skip to content
PlutusShield
Live on Cardano Preview testnet

Assessors

Exploit claims can't settle on an oracle, so a committee decides them: two of three seats on both chains, and no single key that can move capital. Here is how an independent assessor takes a seat.

← Back to site
Testnet onlyNot auditedCardano PreviewMidnight Preprod

Three seats. Two signatures. No single key.

Honest status: today all three Cardano Preview committee keys and all three Midnight Preprod seats are run by the PlutusShield team. The rules are already enforced on-chain; who holds the seats is what changes next. Independent operators come before any mainnet capital, and the enrollment kit for them is in the repo.

Committee seats

2-of-3 on both chains

  • Seat 0

    Team-run

  • Seat 1

    Team-run

  • Seat 2

    Team-run

Independent operators
0 / 3
Enrollment kit
Shipped, offline

Why 2-of-3

The committee is the bridge, so it can't be one key.

Cardano can't read Midnight state. An exploit payout on Cardano therefore rests on the people who checked the Midnight decision. PlutusShield makes that a threshold on both chains instead of a trusted operator.

  • 0single keys that can release capital
  • 1lost key can't stall a payout
  • 1bad key is simply outvoted
Cardano Preview · money

Settle needs two committee signatures

The exploit-cover validator takes Committee { assessors, threshold } as a script parameter. It counts distinct committee key hashes among the tx signers (outsiders and repeats don't count) and pays only at 2. A 1-of-3 Settle was built and rejected by both the local and the Preview evaluator.

exploit_cover.ak
Midnight Preprod · secrets

voteClaim decides, in zero knowledge

policy-cover v2 stores only a commitment per seat. Each voteClaim proves its voter holds that seat's secret, one vote per seat per claim round, and the claim flips to PAID at 2 approvals. The evidence itself never touches the ledger, only its commitment.

policy-cover-v2.compact

On every exploit claim

What an assessor actually does

  1. 01Off-ledger

    Receive the sealed evidence

    The claimant seals the bundle in their browser and files only a 32-byte commitment on Midnight. The encrypted bundle and its key file reach the committee privately, never on a public channel.

    How evidence is sealed
  2. 02Midnight

    Verify it against the ledger

    Open the bundle yourself and check it hashes to the evidence commitment the Midnight registry holds for that policy. Any edited byte fails. Recuse if you have a conflict.

    Open the verifier
  3. 03Midnight

    Vote on Midnight

    voteClaim proves in zero knowledge that you hold your seat's secret; the secret never leaves your machine. Votes are public and attributable to the seat, one per seat per claim round, and the claim flips to PAID at two approvals.

    policy-cover-preprod.mjs --vote <policyId> --member <seat> --approve
  4. 04Cardano

    Co-sign the Cardano Settle

    Only after Midnight shows the claim PAID. The Settle carries the Midnight decision tx in its metadata (label 7732), and the validator pays only with two distinct committee signatures.

    Assessed claim flow

The vote command is the Midnight Preprod relay (policy-cover-preprod.mjs, PLUTUSSHIELD_COVER_VERSION=2), run from the assessor's own machine with their seat file as midnight-committee/member-<seat>.json. It refuses to vote unless the bundle opens to the commitment on the ledger.

Enrollment kit · contracts/committee

Take a seat in five commands. Offline.

No wallet, no network, no transaction. Your secrets are generated on your machine and never leave it; the only thing you share is a signed public record.

  1. 01

    Get the kit

    A plain checkout is enough. The kit is offline and has no npm dependencies: Node built-ins plus the PlutusShield SDK source.

    git clone https://github.com/Kshot3000/PlutusShield && cd PlutusShield

    Node 22.6+. No pnpm? Use node --experimental-strip-types --no-warnings contracts/committee/cli.ts in place of pnpm committee.

  2. 02

    Generate your seat, on your machine

    A fresh Cardano Preview assessor key and a Midnight Preprod seat secret, written 0600 into a 0700 directory, plus a public enrollment record signed by the Cardano key.

    pnpm committee keygen --out ~/plutusshield-assessor --handle @you --affiliation ExampleDEX

    --affiliation is repeatable: list every protocol you work for or hold a position in, so conflicts are visible. keygen never overwrites an existing identity.

  3. 03

    Self-check

    Re-derives your key hash and address, checks the ed25519 signature and encodings, and confirms your local secret files open the record.

    pnpm committee verify ~/plutusshield-assessor/enrollment.json --secrets ~/plutusshield-assessor
  4. 04

    Share only enrollment.json

    It carries your handle, Cardano vkey, key hash and address, and your Midnight seat commitment: nothing secret. The team verifies it and confirms your handle out of band, then assigns a seat.

    pnpm committee seat --dir ~/plutusshield-assessor --seat 1

    Relabels your local seat file so it matches the relay's member-<n>.json. The commitment does not change.

  5. 05

    Agree on the plan

    With three records, every operator builds the same dry run: the exploit-cover Committee parameter and its CBOR, the policy-cover-v2 constructor args, a diff against today's team-run seats, and a planSha256 to compare before anything is deployed.

    pnpm committee plan a.json b.json c.json --threshold 2 --out plan.json

What keygen writes

  • cardano-assessor.sk

    Cardano Preview signing key (bech32 ed25519_sk)

    Secret · 0600
  • cardano-assessor.skey

    Same key as a cardano-cli TextEnvelope

    Secret · 0600
  • midnight-seat.json

    Midnight Preprod committee seat secret

    Secret · 0600
  • cardano-assessor.vkey

    Verification key

    Public
  • enrollment.json

    Signed public record: share this one

    Public

Nobody from PlutusShield will ever ask for the secret files. Back them up offline.

Inside enrollment.json

{
  "schema": "plutusshield/assessor-enrollment@1",
  "operator": { "handle": "@you", "affiliations": ["ExampleDEX"] },
  "cardano":  { "network": "preview", "vkey": "…",
                "keyHash": "<blake2b-224(vkey)>", "address": "addr_test1v…" },
  "midnight": { "network": "preprod",
                "seatCommitment": "<SHA-256 role commitment>" },
  "statement": "I control … I will vote or sign only after
                checking sealed evidence myself … recuse …",
  "signature": { "alg": "ed25519", "sig": "…" }
}

The Cardano key signs a canonical payload binding your handle to this exact seat commitment. Owning the Midnight seat secret can't be shown by a signature (it is a hash preimage), so it is proven by a voteClaim on a drill claim after the redeploy.

Want a seat?

Run the kit, then open an issue on the repo with your public enrollment.json pasted in. Never attach the .sk, .skey or midnight-seat.json files.

Open an enrollment issue (opens in a new tab)

From the public deployment records

Today's committee, seat by seat

Public values only: the Cardano key hashes the validator checks and the Midnight commitments the contract stores. The keys and seat secrets behind them never leave the operator's machine.

Exploit-cover pool v2 · Cardano Preview2-of-3 Settle
Script hash
097ba40ad0…7994f0
preview-exploit-v2.json
policy-cover v2 · Midnight Preprod2-of-3 voteClaim
Threshold
2 approvals of 3 seats
preprod-v2.json
  • Seat 0 · assessor-1

    Team-run
    Cardano key hash
    312e6108d7c87ec1b053d3ba33711804d8dd8527e57e0adc224ea79a
    Preview address
    addr_test1vqcjucgg6ly8asds20fm5vm3rqzd3hv9yljhuzkuyf820xs9pq4qa
    Midnight seat commitment
    9371bf48c0345615555cef18a39edd4f52855738574db57013684436ccb6461f
  • Seat 1 · assessor-2

    Team-run
    Cardano key hash
    d8e3c13c9821d0a8cbe9455b04cc8ace9430973ce3f8ce51a985af0b
    Preview address
    addr_test1vrvw8sfunqsap2xta9z4kpxv3t8fgvyh8n3l3nj34xz67zcl9pt7w
    Midnight seat commitment
    c0aa4178666044f0c4c4ea5d21c8611c1d454a008064ca3304cbdb94cd07d44f
  • Seat 2 · assessor-3

    Team-run
    Cardano key hash
    60b3e35beb92550b0275e827189c7941a11c40c61b5fa201cb035a4f
    Preview address
    addr_test1vpst8c6mawf92zczwh5zwxyu09q6z8zqccd4lgspevp45ncxqz8uc
    Midnight seat commitment
    592b8621f90773e9c267dd5c384b1383683d2727b10192e0a10755eacf165caf

Seat n here is Cardano committee index n+1 and Midnight member n, the same pairing the kit's plan uses.

Proof it works

The first committee drills, on-chain

Demo evidence and test value, decided by the team-run seats. The point is the mechanics: a split vote still resolves, and a payout needs two keys.

Cardano Preview · Settlepolicy c6adbe88…e8648a

50 tADA

paid from the exploit-cover pool, co-signed by assessor-1 + assessor-3

The same Settle with one signature (assessor-2 alone) failed script evaluation locally and on Preview, so it could never be submitted. This payout followed a claim approved on the v1 Midnight registry; the live v2 registry decides by the voteClaim committee shown alongside.

InitPool with the 2-of-3 committee

Before mainnet

From team-run seats to independent ones

The committee is a script parameter on Cardano and a constructor argument on Midnight, so seating new operators means a new exploit-cover pool and a new policy-cover v2 contract. Nothing is rotated in place, and today's pool and contract stay readable as history. The redeploy is not automated by the kit, on purpose.

  1. 1Three operators enroll and share their records.
  2. 2The team verifies each record and confirms each handle out of band.
  3. 3All three re-run the plan on the same records and match planSha256.
  4. 4Redeploy: a new exploit-cover pool on Cardano Preview, a new policy-cover-v2 contract on Midnight Preprod.
  5. 5Drill: one test claim, each seat votes from its own machine, two seats co-sign the Settle.
  6. 6Retire the team-run committee. Today's pool and contract stay readable as history.

Preview and Preprod test value only. Not audited, not an offer of insurance. Committee facts are mirrored at build time from preview-exploit-v2.json and preprod-v2.json; the kit commands are the ones in contracts/committee.