DSync Paymaster Model CIP Merged into Canton Foundation Repository
Pull request #289 adds a CIP describing a paymaster model, under which one registered party pays for traffic on a dedicated synchronizer instead of each member prepaying its own.
A Canton Improvement Proposal titled "DSync Paymaster Model" was added to the canton-foundation/cips repository on GitHub on 16 November 2026, when pull request #289 was merged. The commit record shows contributions signed off by Moritz Kiefer and Amanda L Martin, including adjustments to URLs, an update to the proposal file and a step labelled "number".
The proposal concerns how traffic is paid for on dedicated synchronizers (DSyncs). A separate engineering tracker maintained by ChainSafe, which is building support for the model in Splice 0.11.0, describes it as a replacement for the current prepaid approach.
How the paymaster model works
According to the ChainSafe issue, opened on 27 October 2026, the paymaster model replaces the prepaid model. Today each member of a dedicated synchronizer buys its own traffic on the global synchronizer. Under the new design:
- Members: every member of the dedicated synchronizer gets unlimited traffic.
- Reporting: the sync operator app reports total consumption every 10 minutes.
- Payment: one registered paymaster pays for that consumption through the buy traffic choice.
- Rewards: the paymaster earns app rewards through the CIP-0104 activity hook.
The issue notes that paymaster automation is not part of the work, and that each paymaster builds its own.
Implementation work in Splice 0.11.0
ChainSafe tracks the work as an epic in its canton-extending-mainnet repository, under a milestone named "Phase 2, One Economy (MVP)". The issue says the work is also tracked in the canton-network/splice-multi-sync repository and sets a deadline of 2 December 2026. At the time the issue was read, 11 of its 18 sub-issues were marked complete.
The listed sub-tasks include registering a synchronizer with a paymaster through create, update and archive votes, a paymaster burn for a registered synchronizer through the buy traffic choice, a super validator UI for the registration votes, a four-node dedicated synchronizer Helm deployment, end to end tests of the paymaster flow, and retiring the prepaid model in the tracker and documentation. The issue states the work begins by archiving the current fork main and resetting it to upstream Splice, with features that still fit ported back one per pull request.
Status of the proposal
The merge of pull request #289 places the DSync Paymaster Model text in the Foundation's CIP repository. The sources do not state the proposal's assigned number or whether it has completed any vote. The ChainSafe sub-issues indicate that individual synchronizer registrations with a paymaster are expected to go through votes, with a dedicated interface for super validators.
Why it matters
According to the ChainSafe issue, the paymaster model shifts payment for traffic on a dedicated synchronizer from every member to a single registered paymaster, who earns app rewards through the CIP-0104 activity hook. This changes who bears the cost and who is rewarded. Operators and builders planning around Splice 0.11.0 will want to follow both the proposal and the implementation milestones.
Follow CC on CantonCap.
Written by CantonCap's automated news desk from the sources below.
Sources