Skip to content
CCPEDIAby Unity Nodes

Tier Validator Rights

cip-discuss3 messagesstarted 08-01-2025
Also mentions:CIP-0024
  1. #1Matt Shilston08-01-2025source ↗
    Good morning, 
     
    Based on CIP-0024, I understand different Super Validator owners are permitted additional validator slots over and above what is required to operate a Super Validator.
     
    - T1 = 3 additional rights
    - T2 = 2 x additional rights
    - T3 = 1 x additional right
     
    What additional governance requirements are there for an operator to standup and start running any additional standalone validators? I don't believe there are any technical controls from memory but I could be mis-remembering. 
     
    What would be the process if a rights owner wished to instruct an operator (MPCH) to spin up additional validators within their tier limits? 
     
    Kind regards, 

    Matt 
  2. #2Eric Saraniecki08-01-2025source ↗
    Hi Matt

    Free to stand them up within your limits - no additional process necessary 

    Thanks 

    toggle quoted message Show quoted text

    On Jan 8, 2025, at 6:47 AM, matthew.shilston via lists.sync.global <matthew.shilston=mpch.io@...> wrote:

    
    Good morning, 
     
    Based on CIP-0024, I understand different Super Validator owners are permitted additional validator slots over and above what is required to operate a Super Validator.
     
    - T1 = 3 additional rights
    - T2 = 2 x additional rights
    - T3 = 1 x additional right
     
    What additional governance requirements are there for an operator to standup and start running any additional standalone validators? I don't believe there are any technical controls from memory but I could be mis-remembering. 
     
    What would be the process if a rights owner wished to instruct an operator (MPCH) to spin up additional validators within their tier limits? 
     
    Kind regards, 

    Matt 

    This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
  3. #3Matt Shilston08-01-2025source ↗
    Many thanks Eric!
     
    Matt