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

From testnet promissory note to on-chain receipt

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

Testnet vs production

Testnet hashes prove the pipeline works—gas estimation, retries, KMS plumbing. Mainnet (e.g. 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,” you have a demo, not a receipt.

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 one-off script run from a laptop 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 blog posts should match shipping code; when they diverge, code wins.

Pairs with: selective disclosure + L2 anchoring.