Reduce Validator and Group de-registration duration

Governance Governance Proposals
,
1

Proposal Key Aspects

  • Receiver Entity: Celo Governance
  • Status: [DRAFT]
  • Title: Reduce Validator and Group de-registration duration
  • Author(s): Aaron Boyd
  • Type of Request: Parameter Changes
  • Funding Request: N/A

  1. Summary

  • Reduce validator deregister duration from 5184000 seconds (60 days), to 86400 (1 day)
  • Reduce group deregister duration from 15552000 (180 days), to 172800 (2 days)
  • There will be no change to the locked gold requirements (10000000000000000000000 wei)

  1. Motivation

Moving into the L2, there is no need to have a multi-month cool down delay on validator and group deregistration since consensus is no longer in danger. Additionally, those who do not wish to run L2 RPC nodes for rewards can exit their locked CELO permissions without delay.

Proposal not to be executed before the L2 migration, and can be tested on Alfajores now, Baklava after the 20th February, and Mainnet (TBD).

  1. Specification

[
    {
      "contract": "Validators",
      "function": "setGroupLockedGoldRequirements",
      "args": [
        "10000000000000000000000",
        "172800"
      ],
      "value": "0"
    },
    {
        "contract": "Validators",
        "function": "setValidatorLockedGoldRequirements",
        "args": [
            "10000000000000000000000",
            "86400"
        ],
        "value": "0"
    }
]

  1. Metrics and KPIs

N/A

  1. Current Status

Community discussion.

  1. Timeline and Milestones

To be submitted on chain as soon as the off-chain governance process finishes.

  1. Detailed Budget

N/A

  1. Payment Terms

N/A

  1. Team

N/A

  1. Additional Support/Resources

N/A

5 Likes
2

Got feedback that the unlock shouldn’t be shorter than the regular locked gold unlock time. Will investigate and update the durations in this proposal.

3

After discussion with @martinvol I learned that we must maintain the validator group and validator cooldown period for at least 6 months after the L2 block.

The reason is that if we don’t, and get a large exodus of validators after say 1 or 2 days from the L2 block, then theoretically the small number of remaining operators could rewrite consensus from the block before the migration block, and propose a different sequencer at the fork block, and all the trouble that would cause.

So this proposal is in draft stage / parked until September 2025. Any comments and suggestions are welcome.

4 Likes