Purpose
The Community Staking Module is approaching the mainnet. Most of the CSM features are designed to function automatically and permissionlessly. While critical management functions like creating or updating bond curves, setting charge penalty recipient, and others are controlled by the on-chain voting to ensure protocol security and reliability, the committee multi-sig can control some less critical and non-essential features.
Responsibilities
It is proposed to form a CSM Committee with a corresponding multi-sig and delegate the following permissions regarding CSM’s most common actions to it:
- Report facts of MEV stealing committed by CSM Node Operators (
REPORT_EL_REWARDS_STEALING_PENALTY_ROLE); - Cancel MEV stealing penalty if needed (
REPORT_EL_REWARDS_STEALING_PENALTY_ROLE); - Starting EasyTracks to settle MEV stealing penalty (
trustedCallerfor the corresponding ET factory); - Switching the bond curve for the particular Node Operator or resetting it to the default one (
SET_BOND_CURVE_ROLEandRESET_BOND_CURVE_ROLE); - Pausing CSM in case of emergency via Gate Seal (
sealing_committeefor CSM’s instance of GateSeal);
All of the functions mentioned above might require frequent usage or fast reaction. It is reasonable to allow a committee multi-sig to support smooth operations.
Funding
The only funding required for the committee to operate is a moderate amount of ETH to pay for the gas when executing transactions.
It is proposed that the committee be added to the Gas Supply Committee list of wards.
Multi-sig composition
It is proposed that six members be on the committee and a multi-sig:
- One Lido contributor from the CSM development workstream
- One Lido contributor from the NOM workstream
- One Lido community lifeguard
- Three independent persons from the solo and community staking space
- @lanski COO at DAppNode -
0x6aC2dF117C82F51BfdEF1A249672b9A9cA6b3d86 - @eridian an independent solo-staking enthusiast -
0x7aFd3C7f16FdBB3AdF331Fcc20A585d768ECf60d - @POSTHUMAN founder of the Validator School -
0xCbC39c37Ee315E4A504Cc1AD0D7956A76e20D90d
- @lanski COO at DAppNode -
It is proposed to set a signing threshold for the committee multi-sig to 4/6 so that any decision should be supported by both Lido contributors and independent participants to be executed.
On-chain requirements
Committee multi-sig should be deployed before CSM deployment on the mainnet to ensure proper role assignment.
The committee’s lifespan
It is proposed that the committee will exist until CSM sunset / significant update on the mainnet or until the token holders decide to dismantle the committee via Snapshot vote.
Reporting
The committee members will report on actions taken every quarter using the Lido research forum.
CSM Node Operators can use a special section on the Lido research forum to contact the committee with their questions and complaints.
