Canton’s core design: the “public chain” where a small set can rewrite the rules

Canton’s tokenomics are built around one blunt reality. Super Validators can change core economic parameters, and the system is engineered so those changes are operationally smooth, not socially slow. In the Canton Coin (CC) MiCA whitepaper, “all actions taken by Super Validators” over the Global Synchronizer and the Canton Coin application are “subject to a ⅔ majority action of all Super Validators,” explicitly including the set of active Super Validators, the minting curve and rights split, fees, and protocol improvements.

That governance posture matches the product pitch. The Canton Network whitepaper frames Canton as a “network of networks” where each application provider defines its own privacy, scaling, permissions, and governance while still operating within a broader “decentralized public permissioned network.”

CC’s job is narrower than “governance token,” and more politically salient. It is the token used to pay for shared synchronization services, where fees are burned and rewards are minted to operators and builders based on measurable activity.

Structurally, this is a “public network” whose neutrality is mediated by institutions. The Global Synchronizer Foundation, supported by the Linux Foundation, positions itself as providing transparent governance and organizational neutrality for the network’s public infrastructure.

If you want more reading on institutional crypto designs and governance surfaces, our crypto research page collects related work.

What CC pays for: traffic, transfers, and the burn-first fee model

The simplest way to understand CC is that it is consumed to buy access to shared coordination.

All fees are USD-denominated, paid by burning CC. The MiCA whitepaper describes users paying fees denominated in USD, burning CC rather than paying another party directly, as part of the burn-mint equilibrium.

There are two fee families in the design docs. The payment-application whitepaper spells out two fee families as (1) percentage transfer fees based on value transferred with a regressive structure, and (2) resource usage fees tied to shared infrastructure consumption.

The same document publishes concrete parameter values for CC transfers at launch configuration. These are not “gas” in the Ethereum sense. They are a schedule of burn inputs that also feed reward accounting.

Transfer fee tiers (per output coin where the receiver is not the sender): first $100 at 1.0%, above $100 up to $1000 at 0.1%, above $1000 up to $1M at 0.01%, and everything above at 0.001%.

Resource usage fees (parameter values): base transfer fee $0.03 per output coin, lock holder fee $0.005 per lock holder on a locked output coin, and a holding fee of $1/year per coin (UTXO-like record).

The holding fee matters because it creates an explicit storage rent. The payment-application whitepaper states that when a coin’s effective value reaches zero because holding fees exceed the coin amount, the coin expires and the records are archived.

Separate from CC transfer fees, the Global Synchronizer charges “traffic” as a capacity resource. Traffic is denominated in megabytes, and the MiCA whitepaper describes a “synchronizer traffic fee” where someone burns CC to create a traffic balance for a validator node using the current USD/MB price and conversion rate. It also states traffic is non-transferable and cannot be converted back to CC.

The payment-application whitepaper gives a specific parameter for this: traffic price beyond the free tier is $17/MB, and it also states that a small amount of free traffic is given to all validators to enable onboarding and baseline activity recording.

Supply mechanics: the minting curve, burn-mint equilibrium, and emissions as a governance choice

Public narratives around CC often fixate on an implied maximum supply. Canton’s own blog is explicit that this is the wrong mental model. It says there is no hard cap, and the system is “unlimited in theory, but fairly stable in practice” because CC is burned on usage and minted as rewards.

The canonical emission specification lives in the Canton Coin MiCA whitepaper. It defines a “minting curve” that sets how much CC can be minted over time and how that minting availability is split across roles. Over the first ten years of Global Synchronizer operation, 100 billion CC can be minted, with availability split 50/50 between infrastructure providers and application providers. After those first ten years, the system allows 2.5 billion CC per year to be minted, with approximately 75% going to application providers and 25% to infrastructure providers. For a contrast case with a more conventional capped-supply framing, see our Zilliqa tokenomics.

The burn side is mechanically direct. Fees are burned to cover usage, and minted rewards are earned by participants when they contribute measurable utility. The FAQ emphasizes that there is “no pre-mine” and “no VC allocations,” and that “every token in circulation has been earned by delivering utility.”

The equilibrium target is also explicit. In the MiCA whitepaper’s description of the burn-mint mechanism, it states that at steady state the system allows minting of 2.5 billion CC per year, and that network usage would need to burn 2.5 billion CC per year to keep the number of coins in circulation stable.

Distribution / allocation of minting availability (not pre-minted allocations):

The MiCA table also makes the early bootstrapping bias concrete. In years 0-0.5, the split is shown as 80% to Super Validators, 5% to Validators, and 15% to Applications. In years 0.5-1.5, it shifts to 48% SV, 12% Validators, and 40% Applications. Later, the SV share falls to 20% in years 1.5-5 and 10% in years 5-10.

This is a policy choice, not an accident. The MiCA whitepaper explicitly says the early infrastructure allocation is biased toward bootstrapping Super Validators because they bear early deployment and maintenance costs.

Utility flows and minting rights: CC is burned by users, then reissued by “value providers” under caps

CC’s fiscal flow is unusual in one key way. Users do not pay CC fees to validators or super validators directly. They burn CC to cover fees. The indirect “payment” to operators happens because operators can mint CC as rewards. The MiCA whitepaper describes this explicitly as an “indirect” usage fee from user to provider via burn-and-mint.

That creates a governance-sensitive system because the “who gets paid” decision is embedded in minting eligibility and caps. The MiCA whitepaper lists four scenarios under which CC can be minted and then details how application providers, validators, and super validators earn minting rights.

Application providers mint based on activity-weighting tied to fees burned by users through the application, but the document emphasizes that minting caps exist to prevent gaming and arbitrage. It also introduces a politically charged concept: “featured” applications. Super Validators can lift an initial cap with a ⅔ majority vote by marking an application as “featured.”

Featured status is not cosmetic. The MiCA whitepaper states that featured application providers may mint up to 100x more CC than was burned as fees in CC transfers coordinated by their applications. The payment-application whitepaper repeats the same 100x figure.

Validators can mint for “Coin usage” based on the value of CC transfers initiated by users of that validator. If validators do not mint all available CC for usage in a minting cycle, remaining validator mints can be distributed as “liveness” (uptime) rewards across active validators, with per-validator caps intended to avoid early movers resisting new joiners.

Super Validators can mint for running a node in the Global Synchronizer. The MiCA whitepaper says the total SV pool is defined by the minting curve and is split among super validators relative to efforts or commitments to grow the network, as determined and agreed by ⅔ of the Super Validators, and that these weighted allocations are part of the BFT network configuration.

Finally, CC introduces a conversion-rate governance surface that most L1 users underestimate. All fees are settled in CC using an on-chain CC/USD conversion rate published as part of the minting cycle every ten minutes. Super Validators operate the oracle by submitting proposed conversion rates, and the median is published at the start of each minting cycle.

The payment-application whitepaper also documents a placeholder default conversion rate of $0.005 per CC at network launch, unless super validators propose a different value.

Governance/parameter control: “decentralization with control” means SV-controlled monetary policy

When a project says “decentralization with control,” the analyst move is to ask: control by whom, with what thresholds, and over which levers.

On Canton’s public infrastructure, the control plane is visibly SV-centric. The Canton Foundation’s “About” page states that Super Validator nodes in the Global Synchronizer are entitled to vote on governance matters and changes to code and services.

The Foundation also acts as a representative bloc. The “Join The Foundation” page says the Canton Foundation runs a Super Validator node for its members and “votes according to the direction of its Members.”

Membership is explicit and priced. The Foundation membership agreement is marked APPROVED 9/26/2024 and specifies annual fees including $150,000 for Premier membership and a sliding fee schedule for General members, with Associate membership free.

That does not automatically mean “pay-to-govern the chain.” It does mean governance participation is not an anonymous right. It is a coordinated institutional function.

On the protocol side, the MiCA whitepaper’s governance clause is unusually explicit for an institutional L1 token. It does not confine governance to upgrades. It includes the minting curve, rights split, and fees under the ⅔ SV action umbrella.

Canton’s CIP process is one visible coordination mechanism for SV-set evolution. For example, CIP-0060 is titled “Add Zero Hash as SV of Weight 7.5,” and includes milestone-style deliverables tied to earning SV reward weight, including product integrations and ecosystem activities.

Token governance here is not about “token holders voting.” It is about who sits inside the SV set, how SVs coordinate on parameter changes, and how the system encodes “good behavior” as reward eligibility.

The most power-sensitive lever is the conversion rate oracle. If super validators can collectively reshape the CC/USD conversion rate that governs burn amounts and the economic meaning of “USD-denominated fees,” they control the unit economics of every shared-service interaction. The MiCA whitepaper makes clear that the oracle is operated by super validators and uses a median of submitted rates every ten minutes.

The second is the featured-app gate. A 100x minting cap for featured apps is a powerful, centrally adjudicated subsidy. It can be a strong bootstrap tool. It is also, unavoidably, patronage.

History and structural milestones that actually change the model

July 2024 matters because it anchors the time-based minting curve phases in the MiCA whitepaper. The Linux Foundation press release describes the public infrastructure launched in July 2024.

September 22, 2025 is a governance-brand milestone. The Foundation announced it changed its name from the Global Synchronizer Foundation (GSF) to the Canton Foundation, described as a name change intended to clarify its role in governing the Global Synchronizer within the Canton Network.

Mid-January 2026 is flagged as a tokenomics milestone in Canton’s own analysis. The Canton blog describes an upcoming issuance event at round 78,840 around mid-January 2026, where total issuance per block is cut in half and the SV share falls from 48% to 20%, with a similar “double-halving” three years later that drops SV share from 20% to 10%.

July 21, 2025 is also structurally relevant because it indicates governance can redirect meaningful supply flows. CIP-0067 authorizes a one-time allocation of historical unclaimed rewards from the validator reward pool to the GSF treasury, and states that at the time of drafting it was expected that 1.6 to 1.7 billion CC would transfer to GSF from that action.

February 19, 2026 is the date the Canton Foundation announced a Protocol Development Fund and described it as a “programmatic 5% allocation,” explicitly not from a pre-mined treasury.

Risk analysis: dominant risk and Top 3 risks

Dominant risk: Governance capture of the Global Synchronizer’s economic parameters, because the model concentrates the ability to change monetary policy, fee logic, and conversion-rate infrastructure in the Super Validator set.

The mechanism is not subtle. The MiCA whitepaper says a ⅔ majority of Super Validators governs the minting curve, rights split, fees, the active SV set, and protocol improvements. That means “tokenomics stability” is not guaranteed by immutable code. It is guaranteed socially by the governance norms and incentive alignment of SV operators.

In practice, the most fragile surface is the conversion rate oracle. Fees are USD-denominated but settled in CC at an on-chain CC/USD conversion rate published every ten minutes, and the oracle is run by Super Validators via a median of proposed rates. If the set that also controls upgrades and key parameters controls the oracle inputs, then “fee stability” becomes a governance outcome. That is operationally flexible. It is also political. You do not need a hostile takeover to get bad outcomes. You only need a coalition that decides that some constituency should be subsidized, or that some growth objective justifies changing conversion behavior, featured-app treatment, or reward caps.

The featured-app gate amplifies this. Featured applications can mint up to 100x more than the burned fees their CC transfers coordinate, and featured status is a Super Validator decision. That is a direct lever to create winners. It can be justified as bootstrapping. It also creates obvious lobbying incentives. Once meaningful value is at stake, governance becomes about coalition maintenance.

There is a trade-off here that Canton seems to accept. Institutional networks need predictable change management and the ability to patch and upgrade without “governance theater.” Canton’s structure can do that. The price is that decentralization claims should be read as “many institutions share power,” not “no one can change the rules.” The latter is not what the docs describe.

  1. Trigger: a concentrated coalition within the Super Validator set coordinates on parameter changes or oracle behavior that materially shifts costs or reward flows; Mechanism: ⅔ SV governance authority over fees, minting curve/rights split, and the SV-operated conversion-rate oracle that sets CC burns for USD-denominated fees; Who bears it: application providers and end users paying USD-denominated fees in CC, plus validators whose reward economics depend on governance-set minting rules; Measurable indicators: frequent governance-driven fee parameter changes, sudden shifts in the published CC/USD conversion rate relative to market reference, and abrupt changes in featured-app designations.
  2. Trigger: “bootstrapping exceptions” persist and become structural, especially around featured applications and early emission bias; Mechanism: featured apps may mint up to 100x more than burned fees, and early minting curve phases allocate very high shares to Super Validators, creating long-lived constituencies for privileged treatment; Who bears it: late-joining builders and users who do not receive privileged minting multipliers or early infrastructure allocations; Measurable indicators: a small subset of featured apps capturing a disproportionate share of application-provider mints, and repeated governance decisions expanding or extending featured-app parameters.
  3. Trigger: governance-authorized reallocations or “one-time” transfers become a recurring financing tool for institutions coordinating the network; Mechanism: governance can authorize transfers from pools like unclaimed rewards, as exemplified by CIP-0067’s one-time allocation of historical unclaimed rewards to the GSF treasury (expected 1.6-1.7b CC at drafting); Who bears it: all CC participants via supply-flow and legitimacy impacts, with the most direct impact on parties expecting rule stability around reward pools; Measurable indicators: repeated CIPs that redirect unclaimed or reserved pools, and a growing share of supply movements tied to governance-authorized reallocations rather than organic burn/mint.

If you are modeling CC or advising a team integrating Canton, treat governance risk as first-order. The docs make it clear that Canton prioritizes operational flexibility. That can be good engineering. It also means your “token economy design” assumptions are only as durable as the current SV coalition.

If you need tokenomics consulting to stress-test how CC fees, burn rates, and governance-controlled parameters would behave under institutional usage patterns, insist on scenario work that explicitly includes SV-driven parameter changes and oracle dynamics.

One advisor deliverable that matters here is a governance power map, not just an emission chart, and it should be grounded in the design components that actually move incentives (fees, minting rights, caps, and control thresholds).



This article is part of our Tokenomics Deep Dive series.