Verify a ProofPack
Upload or paste a ProofPack JWS JSON, compact JWT, or Merkle tree JSON. We check what we can and show exactly what passed, failed, or was not applicable. Trust is defined by Zipwire’s policy — see below. Learn about ProofPack verification.
This page uses Zipwire’s trust policy, not a generic “any ProofPack” verifier. A proof can pass structural checks here and still fail your own policy if you expect a different attester or network.
Zipwire platform attester
0x2651ef3d909828eff9a9bdd6454eb5f98b045e76
Root of trust for timestamped proofs and for delegation / human-root attestation chains. On attested proofs, the JWS envelope must be signed (ES256K) by the on-chain attester returned from EAS verification.
EAS networks checked
Base Mainnet, Base Sepolia
By proof type
- Attested ProofPack — fetches the attestation on EAS, checks it exists, is not revoked or expired, and binds to the Merkle root. For IsDelegate and direct IsAHuman root chains, the chain must terminate at the Zipwire platform attester above. Direct PrivateData attestations accept any valid on-chain attester that matches the proof.
- Timestamped ProofPack — no on-chain attestation block; attestation checks are inconclusive. The JWS must be signed by the Zipwire platform attester above.
- Merkle tree only — internal structure only. No signer or attester is verified.