Participate

Two governance tracks.

$CERE holders vote on-chain on protocol parameters, treasury spends, and cluster updates. Separately, the Cere Network DAO operates as a Swiss association with member voting through its General Assembly.

Track A · on-chain · OpenGov

1 $CERE = 1 vote

Token holders steer the protocol.

Propose and vote on referenda via Polkassembly, across graduated tracks: protocol parameters, treasury spends, cluster protocol updates. Stake $CERE to secure the network and back provider bonds.

govern on Polkassembly →stake →

Track B · off-chain · the association

1 member = 1 vote

Members steer the association.

The Cere Network DAO is a Swiss association seated in Zug. Members vote in its General Assembly: one member, one vote, on charters, entities, and mandates. It never votes inside Track A, and Track A never votes here.

become a member →

Beyond governance

More ways in.

Operate a node or a cluster

Contribute compute to any cluster through the ddc-staking and ddc-nodes pallets, post a bond, earn a share of validated usage. Or launch a cluster of your own.

clusters →

Build and publish

Publish agents once, signed under your own key, or launch your own marketplace on the protocol. Any conformant marketplace can carry your manifest; users bring their own vaults.

build →

Claim your vault

Claim a vault, connect agents under grants you sign, revoke with a signature. Your data and your agents' memory stay yours when you switch providers.

use cases →

FAQ

Straight answers, this room only.

Is there a DAO? +

Yes, and it is distinct from on-chain voting. On-chain, any $CERE holder votes on referenda on Polkassembly: one token, one vote, on protocol parameters and the on-chain treasury. The Cere Network DAO is a Swiss association (Baar, Zug) with its own track: members vote one member, one vote in its General Assembly, which amends the articles, approves financials, and admits Observers. Token holders can apply to become members. The first referendum, a token burn, is on-chain for anyone to verify.

What is $CERE actually for? +

Four jobs, all live in the pallets: it meters and settles usage (storage bytes, streams, puts and gets, compute), paid out automatically per era; it bonds operators and clusters to their declared SLAs, with slashing on breach; it votes, one $CERE, one vote, on OpenGov referenda; and active grants meter against a wallet-signed token allowance. The difference from other utility tokens: the utility is auditable end to end. Every transfer traces deposit → grant → activity record → attestation → settlement, and unattested activity never pays out.

Do enterprises need to hold $CERE? +

Not necessarily, by design. Enterprises can be billed in familiar cloud-style terms while verified usage settles through the protocol underneath; cluster operators, validators, and protocol participants settle in $CERE. Fiat onboarding is in active development.