You can keep Canton Coin off your balance sheet. You can't keep it out of your settlement process.
That's the argument here, and it matters to anyone in treasury, finance or operations asked to sign off on a Canton pilot. Every transaction on Canton's shared network pays a fee in a token, and most finance teams would rather not explain a token to their auditor.
The question in the title isn't mine. Digital Asset's Canton Network FAQ, in its version dated 27 July 2026, asks it in those exact words on page 31 and answers with three routes. I've already graded the narrower question, whether you have to hold the coin at all, claim by claim on Do we have to hold Canton Coin to use Canton?. The short answer there is no. This piece asks what each way of saying no costs your organisation, and what to ask the provider you end up relying on. I re-read every source cited here on 19 November 2026.
The evidence for this article is graded claim by claim on Do we have to hold Canton Coin to use Canton?.
How the fee works
AnnouncedEvery message sent through the Global Synchronizer, the shared layer that sequences Canton's transactions so every party agrees on their order, uses traffic, which is Canton's word for transaction fees. The Canton docs say traffic is priced in US dollars by the megabyte and paid for by burning Canton Coin, which destroys it (claim 02). The validator that sends the message pays, and recipients don't (claim 03). A validator is the node that connects your organisation to the network. CIP-0129, the fee framework the Super Validators approved, gives the list price as $60 per MB, about $1 for a typical transaction before rewards (claim 17).
So the coin has to exist somewhere and someone has to burn it. The routes only decide who.
The first route, paying for traffic in fiat
AnnouncedThe FAQ's first route is to disable coin earning and pay for traffic in fiat through a third-party "gas station" service or your node operator. On page 20 the FAQ says prepaying for traffic in fiat "is not a purchase of Canton Coin" (claim 10).
For treasury, this is the cleanest. You pay an invoice in a currency you already account for. For finance, it looks like a prepaid service, though no source I've reviewed says how prepaid traffic should be booked. For operations, it adds a supplier to a core workflow.
Two details in the Canton docs make that supplier matter. Traffic credits can't be transferred, and once bought they can only be spent on that validator (claim 07). And burning coin for traffic earns the validator a reward coupon that lets it mint new coin (claim 06), which is why the FAQ pairs this route with switching coin earning off. Leave it on, and you may end up holding the coin you were trying to avoid.
Not confirmedThis is my own assessment. If the provider stops operating in the middle of a business day, you hold prepaid credit you can't move, and nobody tops up your traffic.
The second route, a separate entity
AnnouncedThe second route is to delegate coin holding to a separate entity, or to use escrow to defer minting.
Treasury still manages a coin position, just in another legal box. Finance inherits the hardest question in this piece, which is whether that entity is consolidated into the group accounts. That's a question for your auditors, and no public source I've found answers it. Operations now depends on an affiliate, or an escrow agent, in every settlement.
Not confirmedIn my view this route can move the coin off one balance sheet and onto another that you may still have to report.
The third route, your counterparty pays
AnnouncedThe third route is to let your counterparty buy traffic on your behalf and adjust the economics of the trade to reflect it.
Treasury holds nothing. Finance sees the fee folded into the price of each trade, which makes it harder to see and harder to compare across counterparties. Operations relies on the other side's validator staying funded.
Not confirmedI think this suits two firms that trade often and trust each other's operations. With a new counterparty, the network cost becomes one more term to negotiate on every deal.
The fourth option is to hold it
AnnouncedThe same FAQ says some institutions are choosing to hold the coin directly on their balance sheet (claim 13). That keeps the accounting, custody and capital questions in your own building, where at least you control the answers. Your position would also be visible to anyone, because the docs say Canton Coin balances and transaction history are public through Scan, the network's explorer (claim 08). I haven't reviewed the capital treatment for a bank that holds it.
Who owns the record
In my work with enterprise data, the first question I ask isn't who owns the asset. It's who owns the record. In every route above, someone else keeps the ledger of how much traffic you bought, how much you used and who burned what on your behalf. When the invoice and your own usage logs disagree, you need a copy you trust, and a contract that says whose copy wins.
A date to keep in view
ConfirmedCIP-0129 carries the status Approved in the Canton Foundation's CIP repository, dated 23 October 2026 (claim 15).
AnnouncedIt says every synchronizer running production workloads will burn Canton Coin at the same list price, dedicated synchronizers included, and its timeline puts that in Q1 2027 while calling the dates estimates, not deadlines (claim 16). An operator who wants a commitment discount would post collateral in Canton Coin (claim 18). If you hoped to sidestep the coin by running your own synchronizer, that path is set to narrow too.
Five questions to put to your provider
Who holds the Canton Coin burned for our traffic, and on whose balance sheet does it sit?
If you stop operating, what happens to our traffic, given credits can't move to another validator?
Is coin earning disabled on our validator, and if it isn't, who receives the rewards?
How is our traffic priced against the list price per megabyte, and what is your margin?
What changes in our contract when CIP-0129 reaches dedicated synchronizers?
The evidence behind each claim above is graded, with the open points I couldn't close, on Do we have to hold Canton Coin to use Canton?.
Which of the three routes would your auditor be most comfortable signing off?
The Sunday letter follows these routes as providers publish their terms. Get it on Substack.
I hold $CC and $CNTN. The full disclosure is on the site.
References and further reading
- Digital Asset, Canton Network FAQ, version 27 July 2026, pages 20, 30 and 31, read 19 November 2026 (canton.network)
- Canton documentation, Tokenomics of the Global Synchronizer, read 19 November 2026 (docs.canton.network)
- Canton documentation, Canton Coin and Traffic, read 19 November 2026 (docs.canton.network)
- Canton documentation, The Global Synchronizer, read 19 November 2026 (docs.canton.network)
- CIP-0129, Universal Burn and Synchronizer Pricing (Status: Approved, 23 October 2026) (github.com)
- The Golden Record, Do we have to hold Canton Coin to use Canton?, 19 graded claims (thegoldenrecord.xyz)
More from The Golden Record: dedicated synchronizers and the Global Synchronizer, do we have to hold Canton Coin, or how we grade.
Graded and published by The Golden Record
Lead claim graded announced, as stated by Digital Asset's own FAQ
Last checked 19 November 2026
Corrections are kept on this page.