Update SV Reward Weight
Dear Super Validators,
Following review under CIP-0105 (SV Locking) and the governance process outlined in CIP-0111, Tokenomics recommends the following SV weight adjustments due to non-compliance with locking requirements. The Foundation has initiated the corresponding on-chain votes, as outlined below.
Changes
MPCH → Reduce to Tier 2 (60% weight) due to falling below Tier 1 locking threshold
Broadridge → Reduce to 0 weight due to not funding locked PartyIDs
Copper → Reduce to 0 weight due to no disclosed locking PartyIDs
DFNS → Reduce to 0 weight due to not funding locked PartyIDs
Elliptic → Reduce to 0 weight due to not funding locked PartyIDs
Figment → Reduce to 0 weight due to not funding locked PartyIDs
Fireblocks → Reduce to 0 weight due to no disclosed locking PartyIDs
Ledger → Reduce to 0 weight due to no disclosed locking PartyIDs
Taurus → Reduce to 0 weight due to no disclosed locking PartyIDs
Rationale
CIP-0105 requires SVs to maintain the required percentage of lifetime rewards in disclosed locking wallets
Failure to maintain threshold or disclose locking PartyIDs results in weight reduction, including to zero where no compliant structure exists
Action Required
Please review and provide your vote via the standard off-chain process.Voting Window
Start: April 23 ~14:00 UTC
End: April 30 ~14:00 UTC (7 days)
Next Steps
If approved, an on-chain vote will be initiated within 3 days in accordance with CIP-0111
Weight changes will take effect 7 days following the initial breech. Any objections need to happen within this timeline.
Impacted SVs will have 30 days from the original breach date to restore their locking threshold under CIP-0105
Failure to restore within this window may result in permanent loss of tier or offboarding if weight reaches zero
If there are any questions or additional information to consider, please share ahead of the voting deadline.
For reference, the current public dashboards are:
Official Documentation
- toggle quoted message Show quoted textSome of the SVs have provided an update concerning the locking. Please see below the updated recommendations
Changes from prior announcement:
- Broadridge → No reduction, funded over 70%
-
Figment → No reduction, funded over 70%
-
DFNS → Reduce to Tier 2 (60% weight) they are now funded > 45% rate
-
Taurus → Reduce to Tier 2 (60% weight), they are now funded > 45% rate
- Tradeweb → Reduce to Tier 2 (60% weight), they are now funded > 45% rate
Continued weight change
-
MPCH → Reduce to Tier 2 (60% weight)
-
Elliptic → Reduce to 0 weight due to not funding locked PartyIDs
-
Copper → Reduce to 0 weight due to no disclosed locking PartyIDs (this includes Copper Clearloop CIP-0039 and Copper CIP-0015)
-
Fireblocks → Reduce to 0 weight due to no disclosed locking PartyIDs
-
Ledger → Reduce to 0 weight due to no disclosed locking PartyIDs
On Thu, Apr 23, 2026 at 9:11 AM Amanda Martin via lists.sync.global <amanda=canton.foundation@...> wrote:Dear Super Validators,
Following review under CIP-0105 (SV Locking) and the governance process outlined in CIP-0111, Tokenomics recommends the following SV weight adjustments due to non-compliance with locking requirements. The Foundation has initiated the corresponding on-chain votes, as outlined below.
Changes
-
MPCH → Reduce to Tier 2 (60% weight) due to falling below Tier 1 locking threshold
-
Broadridge → Reduce to 0 weight due to not funding locked PartyIDs
-
Copper → Reduce to 0 weight due to no disclosed locking PartyIDs
-
DFNS → Reduce to 0 weight due to not funding locked PartyIDs
-
Elliptic → Reduce to 0 weight due to not funding locked PartyIDs
-
Figment → Reduce to 0 weight due to not funding locked PartyIDs
-
Fireblocks → Reduce to 0 weight due to no disclosed locking PartyIDs
-
Ledger → Reduce to 0 weight due to no disclosed locking PartyIDs
-
Taurus → Reduce to 0 weight due to no disclosed locking PartyIDs
Rationale
-
CIP-0105 requires SVs to maintain the required percentage of lifetime rewards in disclosed locking wallets
-
Failure to maintain threshold or disclose locking PartyIDs results in weight reduction, including to zero where no compliant structure exists
Action Required
Please review and provide your vote via the standard off-chain process.Voting Window
-
Start: April 23 ~14:00 UTC
-
End: April 30 ~14:00 UTC (7 days)
Next Steps
-
If approved, an on-chain vote will be initiated within 3 days in accordance with CIP-0111
-
Weight changes will take effect 7 days following the initial breech. Any objections need to happen within this timeline.
-
Impacted SVs will have 30 days from the original breach date to restore their locking threshold under CIP-0105
-
Failure to restore within this window may result in permanent loss of tier or offboarding if weight reaches zero
If there are any questions or additional information to consider, please share ahead of the voting deadline.
For reference, the current public dashboards are:
Official Documentation
- Some of the SVs have provided an update concerning the locking. Please see below the updated recommendationsChanges from last vote:
- 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
Remains the same:- Broadridge → No reduction, funded over 70%
- Figment → No reduction, funded over 70%
- Tradeweb → Reduce to Tier 2 (60% weight), they are now funded > 45% rate
- MPCH → Reduce to Tier 2 (60% weight)
- Elliptic → Reduce to 0 weight due to not funding locked PartyIDs
- DFNS → Reduce to Tier 2 (60% weight) they are now funded > 45% rate