Update SV Reward Weight

1. #1Amanda Martin28-04-2026source ↗
   Some changes are needed for the onchain vote due to the recent addition of Locking values

    

   Changes from last vote:

   • Copper → No reduction, funded over 70% (this includes Copper Clearloop CIP-0039 and Copper CIP-0015)
     

   
   

   Remains the same:

   • Broadridge → No reduction, funded over 70%
   • Figment → No reduction, funded over 70%
   • DFNS → Reduce to Tier 2 (60% weight)
   • Tradeweb → Reduce to Tier 2 (60% weight)
   • MPCH → Reduce to Tier 2 (60% weight)
   • Taurus → Reduce to Tier 2 (60% weight), reduce minting weight by from 3.0 to 1.8, keep escrowed weight at 2
   • Fireblocks →  due to no disclosed locking PartyIDs, reduce minting weight by 2.08 to 0, keep escrowed weight at 2, and unminted at 0.92
   • Ledger → due to no disclosed locking PartyIDs, reduce minting weight by 2.0 to 0, keep escrowed weight at 3
   • Elliptic → Reduce to 0 weight due to not funding locked PartyIDs  
2. #2Wayne Collier28-04-2026source ↗
   It sounds like this means we will need to reject both of the currently active votes related to the SV weights hosted on the Global Synchronizer Foundation / Canton Foundation SV node. Could you confirm this and provide the vote proposal contractIDs for the proposals that should be rejected in light of this change? 
3. #3Amanda Martin30-04-2026source ↗
   Hello SVs, 
   

   
   

   Please reject the vote the following votes 

   • Update Foundation SV Reward Weight with ContractID: 009f8f7faa01130361482e29979f7894b3bcc916fa6f7bd1b6f06f7a8aabbe48a4ca1212207c930ecd0162f71ae4547d0e888035cb7386f602c37eea51eea6d6acda83e2d1
   • Update MPCH SV Reward Weight with ContractID: 005b306eb1fc1fcfed6a9c9159d94540bd754181a1d85d81b1ec150b2264878b00ca121220e65096c51f5e11c667d275559320cf536cc120781fbecf942697aa3d2fdd9413

   A New vote will be created that continues with the reduction:

   • DFNS → Reduce to Tier 2 (60% weight)
   • Tradeweb → Reduce to Tier 2 (60% weight)
   • Ledger → due to no disclosed locking PartyIDs, reduce minting weight by 2.0 to 0, keep escrowed weight at 3
   • Elliptic → Reduce to 0 weight due to not funding locked PartyIDs  

   No longer included in vote:

   • MPCH →  No reduction, funded over 70% [was at 60% reduction]
   • Copper → No reduction, funded over 70% (this includes Copper Clearloop CIP-0039 and Copper CIP-0015) [was at 60% reduction]
     
   • Fireblocks →  No reduction, funded over 70% [was at 100% reduction]
   • Taurus →  No reduction, funded over 70% [was at 60% weight, reduce minting weight by from 3.0 to 1.8, keep escrowed weight at 2]
   • Broadridge → No reduction, funded over 70%
   • Figment → No reduction, funded over 70%

   
   
4. #4Oleksii Maiko30-04-2026source ↗
   Please reject the following votes on the DevNet and TestNet:

   • Dev:
     • MPCH: 0017eb4422cee7056c5823a4db4bc7cba32b2da054ceb56c7a3facdbc8959f856bca1212206de688ff6acb1c7abd4302d0b63f87e20889766754f3d97aa28c26a733f84563
     • GSF: 004d2e144a38df5d80e02d9ec206304d93df97529e1baef1371eca2a0502dc8bf4ca121220b872541023d3925f756207991c9b51583b8f677645475c1988d842a7897fddc2
   • Test:
     • MPCH: 007f140e9fb255414b3defe3ce743b25ec92c7648bdbd58bfc1e7d4c15acfe6412ca1212203cbbff641a399830656df3064dcd2363a1ec6d261f12ef16b828ff0e20c8838b
     • GSF: 007d9159e76d234573574a68705db395386974552a9ca86afe0b044d91c8e3f4deca12122004d0011e94e314eff29a29a2adec96236665365fc49d42df6049192ddca39a37

   A new set of votes was created that continues with the reduction:

   • Dev: 00cfd43ce7c80da1b85500eb0dd7e462668b152cf3e916d4fce596a1cb62677596ca121220f79063f6876d3d73e833159c2ecac775795bd91d987fa13ba5264f4a28ad08af
   • Test: 00d4849ac0759848cc184c151293e7c8f79174f3b24de5b63d070929862b81699aca121220b6aaa1dfbe947e7559f93faf17ce1c22b1285d954febaf4bb7f67a3773d4ce31
   • Main: 006304c3de2bf0dd09c23f990dbc6addb4e8d6789f76f50c4e7da62a273c2951e4ca12122096d66a862c8ed4e4b36e6bca153857aaff092987520af2d846321d41975e0d4c

   Votes expire on 2026-04-30 at 23:00 UTC
   Votes become effective on 2026-05-01 at 23:00 UTC

   
   Also, please reject this proposal on the MainNet as it has incorrect dates. Should have a threshold deadline on April 30th, and effectivity on May 1st:
   00ea5da84ec6469c43f9be8a7c89544c339acb56755f97c37e791816510ca09c26ca121220201b85b8588125c685785606d8767f70ea855d36491715d055d596b58e3c6d48