Cere The Sovereign Context Protocol

The protocol for verifiable AI compute.

Agents can use private data only within permissions signed by the data owner. Each operation creates a verifiable activity record that validators can attest and the protocol can settle.

Dragon 1 is the live flagship cluster, serving DDC on mainnet since 2024. See Dragon 1 →
Identity & delegation OWNS · DATA-WALLET YOUR WALLET OWNS THE VAULT · AGENTS HOLD DERIVED PERMISSIONS layer 05 ED25519 DELEGATION signed delegation · scoped + time-bound Global Agent Registry CONSENTS · GAR ED25519 VERIFY ON EVERY WRITE · CONSUMERS FAIL CLOSED 04 immutable versions scope-of-record · audits read before pay Independent validators PROVES · DAC RANDOM ROTATING SUBSETS · ⅔ SUPERMAJORITY (DESIGN) 03 hashes, never plaintext quorum attestation · validate_node pass/fail Settlement PAYS · FEE-HANDLER DEBIT DEPOSITS · CREDIT PROVIDERS · TREASURY + RESERVE SPLIT 02 ClusterEraPaid / era extrinsics · era finalization on-chain Cere Network L1 ANCHORS · SUBSTRATE DDC-STAKING · DDC-CLUSTERS · DDC-CUSTOMERS · FEE-HANDLER 01 bonds slashable GAR MULTICAST · CONSENT → ALL DDC CLUSTERS
The problem

AI compute is a black box.

You get an answer and a bill. What ran, on which data, at what cost: unverifiable.

Opaque

The execution trail stops at the vendor's API. No receipts, no replay, no independent audit.

Centralized

Model, data, and metering all live with the same vendor. The auditor is the auditee.

Disconnected

Your context is locked inside apps. Agents that need context often have to hand it to whoever runs the model.

Proof of Compute turns AI from a black box into an auditable economic network.

The token · $CERE

Most tokens claim utility.
$CERE shows the receipt.

Every transfer can name the work it paid for, who attested it, and the era that settled it. Unattested activity never pays out: token flow is proven work, by construction.

the full economics → // illustrative trace · every hop is a signed or on-chain artifact
How the protocol works

From signed access to paid execution.

signrecordattest · DACsettleWalletidentityGrantsigned scopeGARconsent of recordValidatorsproof of compute$CEREauto-settle

A grant is signed once, recorded by GAR, attested by validators against captured activity, then settled in $CERE. Proof of Compute, end to end.

01

Data lives in vaults and streams

Identity is a wallet. The vault, partitioned into scopes, belongs to it. Enterprise or personal, the data never moves to the model vendor.

data := vault[scope]
02

Agents get permissioned access

A grant is a signed agreement: which scopes, for how long. The Global Agent Registry verifies every access against it, and revoking is a signature change.

GAR.verify(grant) → ok
03

Compute runs next to the data

Agents execute on cluster compute, serverless and GPU-backed, inside the permission boundary instead of behind a vendor API.

run(agent, scope) @ cluster
04

Every operation is captured

DAC emits a signed activity record per operation: data touched, compute burned, result hash. Off-chain payloads, on-chain integrity.

dac.capture(op) → record
05

Validators attest it happened

Independent validators attest captured execution records against independently observed activity; decisions are designed as a ⅔ supermajority of a rotating random subset. Only attested records are eligible for settlement.

quorum.attest(record) ≥ ⅔
06

The money clears

Each window closes automatically: customer deposits debited, operators, validators, and the protocol treasury paid in $CERE.

settle(era) → paid
Go deeper

Four rooms behind this page.

The short version lives here. Each room holds the full depth: receipts you can read, numbers you can check, code you can run, votes you can cast.

Room 01

The proof

Five primitives, four receipt shapes you can read line by line, and why this is not a dashboard promise. Plus the honest status table.

enter the proof room →
Room 02

The economics

Who pays whom, era by era. Clusters: launch one, join one, what the bond commits you to. The five surfaces of the standard.

enter the economics room →
Room 03

Build

What it makes possible, then the SDK: claim a vault, sign a grant, publish an event, read your receipt. Quickstart in five steps.

enter the build room →
Room 04

Participate

Two governance tracks, never conflated: one $CERE one vote on-chain, one member one vote in the Swiss association. And ten honest FAQs.

enter the governance room →