Skip to main content
HUMΛN
HUMΛN
←Community
Passport
Passport

Selective disclosure and L2 anchoring: proofs today, durable receipts tomorrow

HUMΛN Team··15 min·Web3 + Compliance engineers

Disclosure layer

SD-JWT delivers claim-level selective disclosure with ES256 verifiers today—ideal when presentations do not need unlinkability across verifiers.

BBS+ adds unlinkable presentations when two hiring teams comparing notes must not correlate candidates—see the BBS+ technical post and narrative essay.

Range predicates: Phase 6.1 may ship issuer-issued predicates (e.g. threshold flags computed at issuance) before full cryptographic range proofs land in Phase 6.2. Market honestly: say what the verifier learns and what still requires issuer trust.

Anchoring layer

Testnet anchors validate pipeline and gas behavior without economic finality. Mainnet (e.g. Base) provides durable history and a neutral clock for third parties—verifiers use public RPC and open verification packages; HUMΛN API uptime is not required for inclusion checks.

That independence is the point of anchoring—not “we used a blockchain,” but “verifiers can verify without us.”

Operations

  • BaseAnchorProvider (Viem-style) for submissions with retries and telemetry on failures.
  • KMS for operator keys; rotation runbooks with re-anchor policy documented.
  • Treat anchoring as production infra—on-call, dashboards, not a laptop script.

Checklist: anchoring readiness

  • Testnet → mainnet promotion path documented; no silent environment switch.
  • Operator key rotation exercised in staging with verification script.
  • Verifier package pinned to semver with contract compatibility matrix.

Deep dive: Production DID anchoring. Narrative: credential scanner.

— Part of