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

Why mainnet inclusion—not a testnet hash—is the receipt

HUMΛN Team··10 min·Web3 + Enterprise compliance

A compliance officer asks: can a third party verify this DID attestation in five years without calling your API? If the answer is “we hashed it on a testnet once,” you have a demo—not a receipt.

Production DID anchoring is the move from promissory note to durable, independently checkable history. Passport selective disclosure and L2 anchoring context: selective disclosure + L2.

Testnet vs production

Testnet hashes prove the pipeline works—gas estimation, retries, KMS plumbing. Mainnet (for example Base) provides durable history and economic alignment: verifiers in another jurisdiction can check inclusion years later with public RPC and open-source verification packages.

If your compliance story stops at “we hashed something on a dev chain,” auditors will eventually notice.

Implementation stack

  • BaseAnchorProvider (Viem) for submissions, gas retries, structured errors
  • KMS for operator keys; rotation runbooks with explicit re-anchor policy
  • Telemetry on failures—anchoring is ops, not a laptop script on hotel Wi‑Fi

Independent verification (why this matters)

Open packages + Merkle proofs mean HUMΛN API downtime does not erase verifiability. Third parties verify against chain state, not against our SLA.

That property is the economic and legal point of anchoring—not “we used crypto,” but others can verify without trusting our servers today.

Chain choice

Founder-level gate until the final L2/L1 choice is locked—document alternatives honestly in internal ADRs. Public posts should match shipping code; when they diverge, code wins. Do not claim a chain is production-canonical before the operator runbooks and provider path say so.

Scroll-stopper: A testnet hash is a promissory note. A mainnet inclusion proof is a receipt someone else can cash without calling you.

So that…

…you refuse “we anchored it” as marketing without naming network and verification path; you design ops for KMS rotation and failed submissions; and third-party verifiers stay viable when HUMΛN’s API is offline.

Go deeper