Cere Protocol / The economics room ROOM 02 / 04
Deposits in, attested usage out: the settlement machine, the clusters that run it, and the five surfaces any conformant implementation has to cover.
Compute, storage, and data activity are measured, verified, and paid out automatically to the participants who power the network. The token is the meter, the bond, and the vote.
// indicative split, set per cluster by on-chain governance. developers are paid at the marketplace layer: launch your own marketplace on the protocol and set your own creator split.
Node operators stake $CERE to join a cluster on-chain through the staking pallets.
Providers post $CERE bonds against the SLAs and data-availability commitments they declare. Miss them and the bond is slashed.
Independent validators verify usage and the protocol pays operators automatically. No invoicing, no reconciliation.
$CERE governs infrastructure commitments on-chain. Trusted parts replicate freely; staked parts scale with the network.
Assumed: some nodes misreport or fail; no single validator is trusted. Detected: validator inspection catches misreported activity, out-of-scope compute, and missed SLAs. Consequence: unattested activity never pays out, bonds are slashed, and repeat offenders are removed from the cluster set.
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. No other token can walk you down this chain.
Run your own cluster, or build on someone else's. Some participants operate infrastructure; many more just use it. Dragon 1 is the flagship cluster, one instance of many by design.
Want to earn $CERE with your GPU? Join Dragon 2 →Run the cluster software, register it on-chain through the ddc-clusters pallets, post your bond, declare your SLAs. No permission needed.
cluster software →Propose a cluster through OpenGov for shared resources and incentives. Public, transparent, voted by $CERE holders.
propose a cluster →Want help with architecture, region, SLA, or compliance? We help teams design and launch tailored clusters.
talk to us →// every cluster is registered, bonded, and inspected on-chain. browse them on the chain explorer.
SCP defines five interfaces for conformant participants: identity and delegation, vault access, event streams, portable memory, and conformance. Cere Protocol and Dragon 1 are first implementers, not owners: the standard is open, and intended to move to an external standards body as it stabilizes.
// stage: draft v0 · five surfaces scaffolded · identity-and-delegation leads · an open change process ships with the public drafts
Wallet-owned identity and signed, scoped, time-limited grants. The load-bearing surface.
How agents read and write a user's vault, partitioned by scope.
Real-time context as a first-class, subscribable surface.
Portable agent memory that survives provider switching. The reference implementation calls these containers cubbies.
What a conformant participant must demonstrate, plus audit and lineage.
