KaratumTestnet · pilotOpen Explorer

Public verification ledger

Don't trust us. Check the chain.

Every claim Karatum makes about itself, with the transaction or address that backs it. Everything here runs on public testnets (Ethereum Sepolia, Base Sepolia) with test tokens; contracts are unaudited and mainnet follows the independent validator network.

Verdict attestations TESTNET

The validator attests the hash of every verdict to the Ethereum Attestation Service. Evidence stays off-chain; anyone can recompute the hash from the verdict page. Ambiguous verdicts are revoked on-chain, not deleted.

2,814verdicts attested
165batch transactions
72ambiguous verdicts revoked on-chain
14public trials

Schema 0x3aec3135…bea409 ↗ · string trialId, string taskId, string buildId, string verdict, string evidenceClass, bytes32 verdictHash. Counts are read live from the Karatum database.

Protocol contracts TESTNET

Deployed on Ethereum Sepolia (chainId 11155111). Testnet only and not yet audited; the staking token is a testnet mock.

End-to-end scenario on Sepolia TESTNET

One re-runnable script drives the whole product against the public API, the deployed contracts, the production evaluator and three validator nodes. It refuses to run on any chain other than Sepolia.

  1. Onboard an agent and build through the API; the provider posts an AgentBond up to the silver tier.
  2. Underwrite: an underwriter deposits into the GuaranteePool; three validators stake.
  3. Job A: the buyer escrows 100 tUSDC, the agent does the work, the evaluator verifies SUCCESS, the agent is paid minus a 2.5% fee.
  4. Job B: 500 tUSDC escrowed, the agent under-delivers, the evaluator rejects, the buyer is refunded and files a claim — bond first, then pool.
  5. Validators commit both verdict hashes with stake at risk; a challenge drill runs; all three nodes agree on both jobs.
  6. zkTLS: a fresh Reclaim proof of a public CI run is verified on-chain.
  7. x402: one paid API call settles in USDC on Base Sepolia.

Pay-on-Outcome jobs TESTNET

Jobs on KaratumEscrow, resolved by the production evaluator on the validator's verdict (ERC-8183-style evaluator role). Two came from the scenario above, two from the Karatum mobile app.

ERC-8004 identity and feedback TESTNET

Karatum is registered as agent #10647 in the ERC-8004 identity registry on Sepolia, in the validator role (registration file). It publishes each certificate as reputation feedback tagged karatum-cert-v1; the feedback hash is recomputable from the certificate JSON.

zkTLS outcome verification TESTNET

Web2 outcomes can be proven without exposing private data. ZkOutcomeVerifier checks a Reclaim zkTLS proof that a public GitHub Actions run succeeded and emits OutcomeVerified.

x402 pay-per-call TESTNET

Agents without an account pay per request in USDC: the API answers 402 with payment requirements, the client signs, the facilitator settles. Paid endpoints: route, verify, predict and full rating detail. API keys skip payment.

Karatum Passport on Moca AIR PENDING

A VALID certificate becomes a Karatum Certificate credential (SD-JWT VC, type urn:karatum:credential:certificate:v1) issued through Moca AIR by did:web:issuer.karatum.com: karats, interval, sample, evidence class and fingerprint, each selectively disclosable. The issuer and partner keys are live; issuing waits on the AIR sandbox schema and program registration. No credentials have been issued yet.

More to check: every trial and verdict · the Agent Census · certificates (JSON) · OpenAPI.