Generate proof. Store proof. Verify proof.

Quickstart

Install the SDK and generate your first proof in a few lines.

$ npm install @pfp/sdk

import { PFP } from '@pfp/sdk';

const pfp = new PFP({ issuer: 'org:acme/treasury' });

// commit to the event — raw data stays private
const proof = await pfp.generate({
  type: 'proof_of_approval',
  commitment: pfp.hash(event),
});

const result = await pfp.verify(proof);
console.log(result.verified); // true

Generate → Store → Verify

Verification guide

Verification is purely mathematical and requires no access to the issuer’s systems. A verifier confirms four things:

• IntegrityRecompute the data commitment and compare it to the artifact.
• AuthenticityValidate the digital signature against the issuer’s public key.
• AuthorityConfirm the signing key is authorized and active.
• TimingConfirm the timestamp is anchored and consistent.

const result = await pfp.verify(proof);

// result.verified -> boolean
// result.checks   -> { integrity, signature, authority, timing }
if (!result.verified) {
  throw new Error('Proof failed verification');
}

Architecture

PFP is deliberately minimal. Your systems emit proofs at the moment events occur; the proofs are small, portable artifacts; verifiers check them anywhere. There is no shared database of secrets and no central authority in the verification path.

Learn the concepts in depth in the cryptographic verification and proof artifact articles.

API reference

Security model