Skip to content

← CIP-0073 · votes

VOTES / CIP-0073

Weighted Validator Liveness Rewards for SV-Chosen Parties · current status: Replaced · type: Tokenomics

Vote record for CIP-0073, sourced from the Canton cip-vote mailing list (recent CIPs) and vote-tally PDFs attached to the CIP repo (older CIPs).

7 votes recorded for 5 against 0 abstain 0 unclear 2range 2025-08-192025-08-27MCP: get_cip_votes

On-chain outcome · 1

Super Validators executed 1 DSO vote request whose stated reasoning cites this CIP. This is the ledger record, so it says what was carried out rather than what was discussed.

  • 2026-02-24 · Change AmuletRules config · Accepted 11 for / 0 against

Tally

100%
in favor · 5 against · 0 abstain · 0 unclear · 2

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.

Individual votes · 7

  • in favor
    DrAmandaLMartin
    Hello Super Validator Node Owners,   Please find ready for vote: CIP 0073: Weighted Validator Liveness Rewards for SV-Determined Parties   Digital Asset - SV Sponsor MPCH - SV Endorser All other operators vote please list: <SV Name> votes <in favor | not in favor>
    2025-08-19 18:46 UTC · open on lists.sync.global ↗
  • in favor
    Tradeweb votes
    Tradeweb votes in favor.  From: cip-vote@... <cip-vote@...> on behalf of: DrAmandaLMartin via lists.sync.global <amartin=linuxfoundation.org@...> Date: Tuesday, Aug 19, 2025 at 7:46 PM To: cip-vote@... <cip-vote@...> Subject: [cip-votes] CIP 0073: Weighted Validator Liveness Rewards for SV-Determined Parties CAUTION:This email originated from outside of Tradeweb. Do not open attachments
    2025-08-19 19:31 UTC · open on lists.sync.global ↗
  • in favor
    Orb1 votes
    Orb1 votes in favor Luca Toscani (650) 283-3681   |   Telegram   |  LinkedIn From: cip-vote@... <cip-vote@...> on behalf of Justin Peterson via lists.sync.global <justin.peterson=tradeweb.com@...> Date: Tuesday, August 19, 2025 at 12:31 PM To: cip-vote@... <cip-vote@...> Subject: Re: [cip-votes] CIP 0073: Weighted Validator Liveness Rewards for SV-Determined Parties Tradeweb votes in favor.
    2025-08-19 19:39 UTC · open on lists.sync.global ↗
  • in favor
    Veronica Augustsson
    7RIDGE/C7 is in favor   veronica     V E R O N I C A   A U G U S T S S O N   /   P A R T N E R ​​​​ ​ 7RIDGE IS A PRIVATE MARKETS ASSET MANAGER INVESTED IN TRANSFORMATIVE TECHNOLOGY FOR FINANCIAL SERVICES TO POWER THE GLOBAL ECONOMY Signature for V e r o n i c a A u g u s t s s o n toggle quoted message Show quoted text
    2025-08-21 15:00 UTC · open on lists.sync.global ↗
  • position unclear
    Proof Group votes
    Proof Group votes yes  toggle quoted message Show quoted text
    2025-08-25 20:14 UTC · open on lists.sync.global ↗
  • in favor
    Cumberland DRW is
    Cumberland DRW is in favor.   With our vote, we would like to reiterate a comment we made earlier.  We don’t believe the configurable liveness reward should ever be used to increase a party’s liveness reward on the basis of their participation in the network.  To do so would allocate liveness rewards for purposes that should be address via other mechanisms.    toggle quoted message Show quoted
    2025-08-26 22:19 UTC · open on lists.sync.global ↗
  • position unclear
    Yiannis Varelas
    Hi all, I haven’t voted on CIP-0073 yet. It solves the validator capacity problem, but it also introduces Weighted Licenses and MintingDelegation. That’s basically staking rails. Today it’s harmless. Tomorrow, someone ties weights to token balances and we’ve recreated PoS and whatever it comes with: centralization, governance capture, the whole mess.  That’s not what Canton should bec
    2025-08-27 13:05 UTC · open on lists.sync.global ↗

For AI agents

Same data through MCP:

  • get_cip_votes({cip_id: "0073"}) — 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/0073/mentions — aggregated backlinks (includes mailing-thread references).