VOTES / CIP-0120

Positions are parsed from each message's body text (most are one-line statements like "Five North in favor"). If parsing was uncertain, the row appears as position unclear below, please flag if you spot a misread.

• in favor
  Amanda Martin

  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 GitHub at the Proposed state 1838cc0cc4d908ed2d6c912636c956b93273e66e No changes will be made to the CIP text after this announcement other than updating the approval date and status. Sponsors / Endorsers MPCH – SV Sponsor 5N – SV En

  2026-08-03 16:08 UTC · open on lists.sync.global ↗
• in favor
  Eric Saraniecki

  hi all - DA isn't actually ready to vote on this topic yet you're of course welcome to do so without us but we wanted to put out the idea for preliminary feedback and examination On Mon, Aug 3, 2026 at 12:08 PM Amanda Martin via lists.sync.global <amanda=canton.foundation@...> wrote: Hello Super Validator Node Owners, Please find ready for vote: CIP-0120: Traffic-Based Validator Rewards and Confir

  2026-08-03 21:12 UTC · open on lists.sync.global ↗
• in favor
  Cumberland votes not

  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. We'll share additional feedback in the discuss thread, one point we want to raise here is that its not clear that allocating validator rewards to this mechanism accomplishes all the sated goals of the

  2026-08-03 22:46 UTC · open on lists.sync.global ↗
• position unclear
  Chris Matturri

  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 take this to a vote. Formally Proof Group votes no to this for now.

  2026-08-04 00:21 UTC · open on lists.sync.global ↗

Same data through MCP:

• get_cip_votes({cip_id: "0120"}): formatted markdown of each vote message in chronological order.
• get_cip_citations: full citation graph (includes the same vote messages plus everything else that references this CIP).
• get_cip_history: status transitions over time (/governance/timeline).
• GET /api/v1/cips/0120/mentions Returns aggregated backlinks (includes mailing-thread references).