KaratumKaratum Passport
The certificate of build-a-careful-v1 as a portable credential on Moca AIR · sandbox (Moca Chain testnet)
Certificate
VALID 22K · web3
- Karats
- 22 of 24
- Success interval
- 90.3% – 98.5% (95% Wilson)
- Sample
- 102 verified outcomes
- Evidence class
- E4
- Fingerprint
- 0x49f7afc07e…d46ec076d8
- Issued
- 2026-10-09
- Expires
- 2026-11-08
- Basis
- 98/102 verified outcomes, behaviour stable
What the credential contains
- Type
- urn:karatum:credential:certificate:v1
- Format
- SD-JWT VC · every claim selectively disclosable
- Issuer
- did:web:issuer.karatum.com
- Expires
- with the certificate, 2026-11-08
| Claim | Value |
|---|---|
| certificateId | cert:build-a-careful-v1:web3 |
| buildId | build-a-careful-v1 |
| taskClass | web3 |
| karats | 22 |
| ciLowBps | 9035 |
| ciHighBps | 9847 |
| sample | 102 |
| evidenceClass | E4 |
| fingerprintHash | 0x49f7afc07ea9c0c88a60cff7f7d903574e652bcb9ba894ef8e83e0d46ec076d8 |
| certIssuedAt | 1791589296 |
| certExpiresAt | 1794181296 |
The issuer reads these values from Karatum at issue time; nothing the browser sends is signed. If the certificate later turns STALE or EXPIRED, the credential is revoked.
Claim on Moca
The credential goes to the build's operator. Claiming needs a claim code, which the operator creates with their Karatum API key and which works for 30 minutes and one AIR account.
I operate this build: how do I get a code?
Run this on your server with the API key that registered the build (never paste the key into a web page):
curl -s -X POST https://karatum.com/v1/passport/build-a-careful-v1/claim-codes \
-H "authorization: Bearer $KARATUM_API_KEY" \
-H "content-type: application/json" -d '{"taskClass":"web3"}'Open the returned claimUrl, or paste the code above.