Canton Improvement Proposals

Hello Everyone, Following the recommendations of the last office hours meeting, I am sending a draft of a new CIP submission for refinement. I look forward to working with the editorial team to advance this. If I am missing any crucial steps, I would appreciate any guidance from the team on the process. Kind Regards, -- John Bui Business Development Specialist Republic Operations LLC john.bui@... | republic.com This email and any files transmitted with it are confidential and intended solely for

Hi everyone Another great topic that has been coming up a lot lately - SV governance. Both of these are early drafts and all feedback welcome. I would suggest we focus on the voting one prior to the operating one but I present them together because it is ultimately related. Thanks Eric -- W Eric Saraniecki+1 (773) 719-1983Co-Founder, Head of Network Strategyeric@... of Canton Network This message, and any attachments, is for the intended recipient(s) only, may contain information that is privile

Hi all - this is really interesting! Thanks for all of your effort putting it together. I'm posting some questions below mainly because the CIP itself is quite technical and I'm guessing we aren't the only ones who can't draw economic conclusions directly from the proposal. Is it possible to provide some plain-text examples of validator incentives in the current implementation vs. this future proposed implementation? A typical featured application runs its own validator in a 1-of-1 set-up today

Hi all, I'd like to share with you the "2026-06 - CNS 2.0 Proposal for Next Steps" presentation , which summarizes the current thinking of the Identity and Metadata SIG ( #cf-identity-and-metadata ) on the first set of CIPs that will simplify identifying parties on Canton and associating metadata with them. I'm sharing that with you for two reasons: To give you a heads-up on the CIP drafts expected to be announced on this mailing list in the coming months. To invite you to provide early feedback

Dear community, Please find attached a proposal for making three primary improvements to the validator rewards; adjust the calculation of validator rewards to be based on actual traffic usage rather than CC burn for traffic purchases, introduce a reward split between the submitting validator and confirming validators and increase the validatorRewardCap to 30%. This CIP aims to incentivize the multi-hosting of parties across validators, enhancing network security and decentralization. You can fin

Dear community, please find attached a proposal for improving the quality of the app reward incentives by removing featured app markers and instead basing an app’s rewards on the actual traffic spent on (sub-)transactions that change the state managed by the app. You can find the corresponding PR here: https://github.com/canton-foundation/cips/pull/157. Feedback is most welcome. For your convenience, a copy of today's state of the PR can be read here, and is inlined into the email below. Kind re

CIP: CIP XXXX (to be assigned) Title: Add Halborn as a Weight 4 Super Validator Author: Edgar Cepin Status: Draft Type: Governance Created: 2026-07-02 License: CC0-1.0Abstract Add Halborn Inc. as a Weight 4 Super Validator Halborn agrees to a multi-year basket of security-focused contributions to the Canton ecosystem, including infrastructure and custody security audits, a public security standards publication, EU regulatory readiness advisory, a subsidized security-testing tier, and a Daml pack

During design of the implementation of automated rewards locking it became clear that we needed to spell out which enforcement steps would be automated, and how automated enforcement would work. I'd like to propose the following text be added to CIP-0105 and CIP-0116 to describe automated enforcement: CIP-0105: Automated Onchain Weight Reduction Super Validators that fall below a locking threshold will have a time-configured (default: seven-day) grace period. During this grace period the Super V

Hello All, Tokenomics has requested an amendment to CIP-0104 that allows on-ledger voting to set application reward weights per app. This proposed featured app weight extension to CIP-0104 fulfils that request and is fast to deliver. What were proposing specifically is to add an "activity weight" to the on-chain featured app status. This weight is adjustable per application through the same on-chain voting process that grants and revokes featured app status in the first place. The weight default

Number: CIP-TBD Author: Matthew Longhurst, Co-founder and CIO, TreasurySpring Type: Governance Created: 2026-06-16 Status: Proposed License: CC0-1.0 1. Summary This CIP proposes that TreasurySpring Management (Jersey) Limited (TreasurySpring) be admitted as a Super Validator applicant with a core maximum earnable SV reward weight of 5, plus an additional accelerated-delivery bonus of up to 0.5. The application uses a milestone-based representative-SV structure, with rewards initially escrowed an