The vote on Canton’s Universal Burn framework has passed, Digital Asset chief executive Yuval Rooz announced on October 21 . The framework would extend Canton Coin fees and rewards to dedicated transaction systems used by businesses. It is not yet a live change to network charges. The result follows Five North’s sponsorship of CIP-0129 and Cumberland DRW’s endorsement . The public voting thread includes affirmative replies from Proof Group and Digital Asset on October 21. Bringing two charging models together Canton applications can use the shared Global Synchronizer , which helps coordinate transactions, or dedicated synchronizers configured for particular needs. Those dedicated systems are already part of MainNet. The vote concerns how they pay for traffic, not whether they can join the network. The difference is economic. Traffic on the Global Synchronizer already burns CC to pay fees, permanently removing those coins from circulation. Eligible applications and validators, the network’s nodes, earn rewards. Dedicated synchronizers have historically paid licence fees to Digital Asset instead, without that traffic taking part in the same burn-and-reward model. CIP-0129 would extend CC traffic charges to all synchronizers running production workloads. Applications and validators on dedicated infrastructure would also enter the existing reward system as licence fees phase out. This is not a percentage tax on the value of assets being traded. Traffic charges are based on network data . Nor does the framework require every application to move onto the Global Synchronizer: businesses could retain dedicated infrastructure while contributing to the same CC economy. Editorial comparison of the current charging model and the framework once implemented. A passed vote is not activation. Source: CIP-0129 , checked October 21, 2026. What changes for applications and CC holders? For a business using dedicated infrastructure, the change would affect both its charges and its eligibility for rewards. A useful comparison with an existing licence agreement therefore needs to consider both. The authors’ explanation of costs after rewards also makes clear that rewards are not guaranteed. For Canton, the practical gain would be a closer connection between production activity and CC usage. More of the network’s traffic would contribute burn, while more applications and validators would compete for the existing reward pools. The framework does not increase issuance or change the reward split. Initially, dedicated operators would report activity for rewards. Those reports could not claim rewards for more traffic than was paid for, but dishonest reporting could divert rewards among a dedicated system’s participants. The first implementation therefore still relies on operators reporting honestly. That wider reach does not establish how much extra CC would be burned. Total activity, discounts and adoption would all matter. The distinction between coins burned and coins newly issued remains important: extending fees does not, by itself, prove that burn will exceed minting. Discounts come with a second decision The Global Synchronizer’s price would stay unchanged. The framework provides for volume pricing on dedicated synchronizers, with optional further discounts for operators that commit to usage for at least a year and post CC as collateral. That collateral would be a deposit backing the commitment, not an immediate burn. It could cover usage shortfalls, and failing to top it up when required could lead to forfeiture. Remaining collateral would be returned when the commitment ends. The detailed pricing curve, discount levels and collateral rules belong in a second CIP. Illustrative prices in the accompanying presentation are not approved rates. Until standard discounts are implemented, Super Validators could approve interim discounts case by case. The vote is a step towards implementation The proposal estimates universal burn in Q1 2027 and volume pricing with commitment discounts in Q3 2027. These are estimates, not launch deadlines. Software work and a deployment vote still follow; the second phase also needs its own proposal approved. For operators, the useful change is knowing the direction before committing to infrastructure. The next decision is whether the eventual prices and deposit terms suit the activity they actually expect to run. Status checked October 21, 2026 at 14:04 UTC: the GitHub entry still carried a “Proposed” label. Rooz’s public announcement is the source for the passed-vote result. Read the Universal Burn and Synchronizer Pricing framework .