Quick setup: verification context
Configuring verification context and verifiers for ProofPack (JS and C#)
Last updated
Configuring verification context and verifiers for ProofPack (JS and C#)
ProofPack uses different setup for (1) wallet-only verification (IsDelegate) and (2) full proof verification (AttestedMerkleExchangeReader with attestation verifier factory and routing). The exact APIs and config shapes are in the ProofPack repo.
JavaScript: Path 1 shows the real IsDelegateAttestationVerifier config (delegationSchemaUid, acceptedRoots, preferredSubjectSchemas, schemaPayloadValidators). For full-document verification, the repo uses createVerificationContextWithAttestationVerifierFactory with an AttestationVerifierFactory and routing config — see ProofPack JavaScript README and Ethereum package: Using with Verification Context.
C# / .NET: Verifier uses IsDelegateVerifierConfig (AcceptedRoots, DelegationSchemaUid, etc.) and IsDelegateVerifierOptions (Chains or Lookup). Reader uses AttestedMerkleExchangeVerificationContext.WithAttestationVerifierFactory with routing. See ProofPack .NET README and EXAMPLES.md.
Conceptually you configure trusted roots and schemas, then create a verifier (for wallet checks) and a reader + verification context (for JWS/JWT). Copy-paste config from the repo rather than from this page.
Last updated