Set L2 Compliance Proofs

verify(proof, public_inputs)  ──▶ valid?
sha256(proof) == proofHash    ──▶ same proof that was anchored?
policyHash    == expected     ──▶ the policy you actually meant?

all three ──▶ the policy held.

import { createHash } from "node:crypto";
import { verify } from "@stateset/nsr"; // STARK verifier

// 1. On-chain metadata for the batch
const { proofHash, policyHash, allCompliant } = await setL2.getBatchProof(batchId);

// 2. The artifact itself, from your prover storage
const proof = await proofStore.get(proofHash);

// 3. Verify it against the policy's public inputs
const valid = await verify(proof, publicInputs);

// 4. Both hash comparisons — neither is optional
const sameArtifact = createHash("sha256").update(proof).digest("hex") === proofHash;
const rightPolicy = policyHash === EXPECTED_POLICY_HASH;

if (!(valid && sameArtifact && rightPolicy)) {
  throw new Error("proof did not establish the policy held");
}

# The same three checks from the CLI, against a batch id
stateset set verify-compliance \
  --batch "$BATCH_ID" \
  --policy-hash "$EXPECTED_POLICY_HASH"