Canton Plans to Bill Institutional Traffic in CC Burns

Workloads on Canton's dedicated synchronizers have paid license fees to Digital Asset. An approved framework plans to shift that bill to token burns, with rewards flowing back to whoever pays.
Key Takeaways
- Payment can lag traffic up to 14 days.
- Paymasters burn CC and collect the rewards.
- Traffic reports are self-declared at launch.
- Higher CC prices shrink burns for identical usage.
CIP-0132, authored by Moritz Kiefer and proposed on November 16, sets out an initial version of that payment system. It was still marked “Proposed” on November 22. CIP-0129, the approved framework it builds on, estimates its first phase for the first quarter of 2027 and labels all of its dates as estimates.
From License Fee to Token Burn
Canton runs a shared Global Synchronizer alongside dedicated synchronizers that carry separate workloads on MainNet, a setup covered in Coindoo’s guide to Canton’s institutional network. The two have been paid for in different ways. According to CIP-0129, Global Synchronizer traffic burns Canton Coin (CC), while dedicated-synchronizer traffic burns nothing and has been covered by license fees to Digital Asset.
CIP-0129, written by Yiannis Varelas and Shaul Kfir, brings that dedicated traffic into the same burn-and-reward system. Its first phase switches on the universal burn with interim discounts. The money that reached Digital Asset as license fees is meant to arrive on the network as destroyed CC instead.
That shift creates the first problem for anyone tracking burns. A burn series jumps on the day a dedicated synchronizer starts paying, even if its traffic is unchanged, because activity that already existed moves onto the token’s books. Early rises in burned CC have to be split between synchronizers that newly started paying and growth within those already counted.
The bill is also priced in data. Coindoo’s tally of the first day of CNTN tokenized-share trading counted five purchases worth $40,296. Under the proposed model, trades like these are billed for the megabytes they generate, so a $10,000 purchase and a $100 purchase can cost the network similar amounts.
Who Pays, and Who Gets Paid Back
Each dedicated synchronizer gets one paymaster, registered through a vote of Canton’s super validators (SVs), the operators that govern the network. The paymaster is the only party allowed to burn CC for that synchronizer, and it settles after the traffic has already run.
Every burn also creates reward claims, and CIP-0132 sends them to the paymaster. The party paying the bill is partly reimbursed in newly minted CC, so the gross burn overstates what the bill really costs. CIP-0129 adds that rewards on dedicated traffic are weighted by the CC actually burned after discounts, which means a discounted bill earns proportionally less back.
Why the Burn Trails the Traffic
Because the paymaster pays after the fact, CIP-0132 allows schedules that smooth the bill. In its stepwise example, the paymaster measures a week of traffic and then burns at a constant rate each round of the following week, a delay of up to 14 days. In its continuous example, the paymaster burns each round at the average of the preceding seven days. A round is one of Canton’s short, recurring reward cycles.
Either schedule turns spiky usage into a smooth line. A burst of activity on Monday appears as a slightly higher burn spread over the next week, and a quiet weekend registers days after it happened. These are examples the proposal permits, and operators are free to agree different arrangements.
Same Traffic, Different Burn
The amount burned equals the discounted dollar bill divided by the CC price. Network fees are set in dollars, as Digital Asset’s no-action request to the SEC explains, so the number of tokens needed to cover a fixed bill moves with the market. CIP-0132’s worked example prices traffic at $60 per megabyte.
Discounts are built into the design. In the first phase, SVs approve interim discounts case by case, agreed with each operator off-ledger. A second CIP is meant to replace them with volume pricing and commitment discounts. Under a commitment, an operator pledges a throughput level for a year or more and posts CC as collateral in return for layered discounts. Anyone watching the chain sees the burn, while the discount behind it is negotiated elsewhere.
| Discount | Bill | CC price | CC burned |
|---|---|---|---|
| None | $6,000 | $0.10 | 60,000 |
| 50% | $3,000 | $0.10 | 30,000 |
| 50% | $3,000 | $0.20 | 15,000 |
Coindoo calculations. The reference price and 50% discount come from CIP-0132’s worked example; the CC prices are hypothetical.
Doubling the CC price halves the burn while usage and the dollar bill stay fixed. A falling count of burned tokens can therefore come from a rising token price, and a weaker CC price can lift burns without a single extra megabyte of traffic.
Traffic Reports Rest on Trust
At launch, nothing on-chain checks the traffic figure itself. CIP-0132 treats the operator and paymaster as trusted to report accurately and burn the right amount, and it acknowledges that a malicious operator could under- or over-report. The dedicated synchronizer enforces no traffic limits, so messages go through whether or not they have been paid for, and the link between traffic and burn sits off-ledger.
The on-chain controls work on the reward side. An SV vote creates a registration contract for each synchronizer that names its paymaster and caps the activity weights its traffic can earn, and contract logic keeps rewards in line with the CC burned. That stops a paymaster from claiming more rewards than it paid for. It does nothing to stop an operator from reporting less traffic to shrink the bill.
CIP-0129 asks each operator to publish aggregate traffic reports on the Global Synchronizer, attributed per party, and says those reports depend on the operator’s honesty at launch. Both documents describe the setup as interim. Later phases are meant to tighten enforcement, reduce reliance on operators and paymasters, and eventually make dedicated synchronizers trustless and self-serve.
Burns, Rewards and Supply
Canton’s official tokenomics page describes a burn-mint equilibrium: fees are burned, new coins are minted for participants who add utility, and total supply follows a pre-defined curve. The page calls the system slightly deflationary when burns grow and mildly inflationary when minting outweighs them.
CIP-0129 states that issuance does not change under the new framework and that the reward split among SVs, validators, apps and the Development Fund stays the same. Dedicated-synchronizer traffic therefore joins a reward system whose schedule is already set. Its burns add to the destruction side, and its reward claims are paid from that existing schedule.
Two more details shape the arithmetic. Reward coupons are claims, and CC enters supply only when the separate issuance transactions mint it, so a net-supply figure has to compare burns with coins actually minted over the same dates. Commitment collateral works differently again: CC posted to secure a discount is locked rather than destroyed, which shrinks the liquid float but leaves total supply unchanged.
CIP-0129 expects total burn to rise even at lower per-transaction prices. Whether that translates into a shrinking supply depends on how much minting lands in the same window, how deep the discounts run and where the CC price sits. Canton publishes reward distributions and CC fees, so the claim can be tested once dedicated traffic starts paying.
The Two Numbers to Read Together
The operator’s traffic report and the paymaster’s burn are the only direct link between Canton’s private activity and its token data. At launch, both come from parties the design chooses to trust. Read side by side, they show how much traffic was billed and how far that bill was discounted. A burn figure published without the report behind it shows only how many tokens were destroyed.









