As discussed in the Relay Voting proposal, in order to make on-chain management of the vetted relay lists more nimble in the near term (until the mechanism can be Easy Tracked). As suggested in the proposed updates to the Block Proposer Rewards Policy, it is proposed that the DAO delegate authority to the RMC to make decisions about which relays are added to or moved between the “relay lists”, provided that RMC decisions are posted publicly on the Lido research forums prior to any on-chain actions being taken and giving the DAO and community a reasonable amount of time to consider. The DAO retains the right to a final decision and community members may post a Snapshot vote to change or counteract RMC decisions and/or reconstitute the RMC with different participants.
This is a proposal to identify and empower the participants for the Relay Maintenance Committee (RMC), which will be a Gnosis Safe multisig that will be manage the vetted relay list on behalf of the day (see Deployed Contracts | Lido Docs).
Based on interest received from various parties, the proposed composition of the RMC is the following and will be run as a 4/7 or 5/7 (TBD):
I would be honoured to take part in the relay maintenance multisig on behalf of Sigma Prime. I will use the address 0x6B29132ea388a308578c1d3Be068D0e4fc9915a2 (michaelsproul.eth). I’ve signed a message from this address and published it to Twitter here:
Hi, I would like to request the community to consider @Dharmendra, a colleague and also a contributor of karpatkey, to replace me as a member of the RMC with address 0x2d0669db84f11a9ead41e57ce2f242d92111a58f. He will be able to serve this committee better moving forward, giving his focus on Ethereum validators and its related infrastructure.