How it works
Four steps. One trust anchor. Zero trust in us.
Every credential issued through LearnCoin goes through the same four-step pipeline. The verifier — a recruiter, an HR system, an AI agent, or the recipient themselves — never has to trust LearnCoin. The cryptography and the public chain do the trusting.
Issue
Tenants call POST /v1/batches
An issuer — a university, an employer, a training platform like Ewance — sends a of credentials to the REST API with a lrn_live_ . Each credential carries the pseudonymous ID, the , to skill frameworks, and optional metadata.
The call returns 202 Accepted with a batch ID instantly. Signing and anchoring happen asynchronously — the tenant is unblocked the moment the request lands.
Sign
Per-tenant keys in HSM-protected GCP KMS
Each has a dedicated signing key held inside , never exported. LearnCoin's signing worker each credential with , hashes the N-Quads output to , and submits the digest to KMS for signing.
The signing key is exposed publicly only as a fragment inside the LearnCoin at /.well-known/did.json. The private side never leaves the .
Anchor
Merkle batch → Ethereum L2 (Base — OP Stack)
Signed credentials within a are hashed into a binary, the root is written to a single transaction on Base — Coinbase's open-source built on Optimism's OP Stack.
Per-credential cost at scale is effectively zero: one transaction commits the whole batch. The on-chain footprint is only the plus issuer reference plus timestamp plus transaction ID — never , never the credential content itself.
Base settles back to via the 's withdrawal bridge. That chain of settlements is the trust anchor — Ethereum, not any single company, is the root.
Verify
Any Blockcerts-compatible tool, any time, forever
Each credential gets a shareable public URL at learncoin.me/c/{id}. The public verification page runs the blockcerts-verifierWeb Component client-side — the verification happens in the viewer's browser, not on a LearnCoin server.
The walks the proof path from the credential's canonical hash up to the Merkle root, confirms the landed on , resolves the issuer DID, and validates the signature. Five green checks: schema, signature, issuer, , .
Because the proof is a on a self-containeddocument, verification continues to work even if LearnCoin shuts down tomorrow. The recipient's own copy of the credential, the Base chain, and the DID document are sufficient.
Ten lines of code. Your first credential on testnet.
Test mode is free, forever. When you're ready for real credentials on Base mainnet, upgrade to Starter.