← CIP-0120 · citation graph
CITATIONS / CIP-0120
Traffic-Based Validator Rewards and Confirming Validator Incentives · status: Proposed
Every place across CCPEDIA's corpus that references CIP-0120: sibling CIPs, forum threads, the cip-* / grants-* mailing lists, GitHub issues + PRs across all indexed Canton repos, third-party blog coverage, and YouTube transcripts. Each section samples the most recent N; counts above the sample are the totals.
Mailing-list messages · 13 · across 2 threads
Messages on cip-vote, cip-discuss, grants-discuss, and other validator-announce lists. Items with cip_id_match badge come from CCPEDIA-parsed mailing_messages.cip_id: only-here join.
Hi all, Following feedback on CIP-0120, the proposed increase to the validator dynamic minting cap (from 20% to 30% during high-burn perio …
Directionally we like the concept of this CIP and incentivizing decentralization of validators hosting different applications on the network- but agree with DA & Cumberland that it is premature to tak
Cumberland votes not in favor at the moment. While we are open to considering some of the ideas presented in the CIP, we think it represents some significant changes that merit additional discussion.
… Martin via lists.sync.global wrote: Hello Super Validator Node Owners, Please find ready for vote: CIP-0120: Traffic-Based Validator Rewards and Confirming Validator Incentives The CIP text as merged in GitH …
Hello Super Validator Node Owners, Please find ready for vote: CIP-0120: Traffic-Based Validator Rewards and Confirming Validator Incentives The CIP text as merged in GitH …
Hey Alex, In response to your comment about traffic fees, as per CIP-0104 here confirmations don't cost the confirming validators cost traffic anymore - the traffic cost is reimbursed to the confirmin
Hey Anthony, Thanks for your review and questions. Answers below 1. Is it possible to provide some plain-text examples of validator incentives in the current implementation vs. this future proposed im
Hi David, team, thanks for sending this into discuss - a lot of time and thought clearly went into it. One thing I'd like to understand more is the reasoning behind further incentivizing / allocating
Send supports this proposal as well. This proposal ties incentives to the strong, yet overlooked, Canton primitive of networks of networks and decentralization. - Erick Ho Send Foundation
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
David and team - thanks for working on this. I'm echoing Kinga's comment on network resilience and decentralization. Five North has worked with DA and MPCH and already implemented 2-3 co-validation in
Thank you David. This is a very important step towards ensuring network resilience. MPCH is happy to support. From: cip-discuss@... on behalf of David Richards via lists.sync.global Date: Wednesday, J
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 t
GitHub items · 2
Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0120.
This PR removes the "Adjusting Validator Caps for High-Burn Environments" section from CIP-0120 (Traffic-Based Validator Rewards and Confirming Validator Incentives). Author: David Richards
@hythloda : this PR only contains polishing changes, and does not impact the content. It's best reviewed ignoring whitespace. Who is the right person to ask for a review and merge?
For AI agents
Same citation graph through programmatic surfaces:
get_cip_citations: MCP tool. Input:{cip_id}. Output: counts plus sample items per source. Use when an agent needs "everything that references CIP-X across CCPEDIA's corpus" in one round-trip.GET /api/v1/cips/0120/citationsReturns a JSON shape mirroring this page.- The legacy
/api/v1/cips/0120/mentionsstays for backward compat. It returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.