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):
@Izzy, Lido contributor (myself)
@George, Lido contributor
@eliasimos, Rated co-founder
@yorickdowne , Cryptomanufaktur founder and Node Operator participating in Lido
@michaelsproul , representing Sigma Prime (Ethereum consensus client team and Node Operator participating in Lido)
@philknows , representing ChainSafe (Ethereum consensus client team and Node Operator participating in Lido)
@Sisyphos , Karpatkey
This feels like a fairly balanced RMC list (2 Lido, 3 Node Operators, 2 third parties). I support this group to manage the relay list multisig.
I would be honoured to take part in the relay maintenance multisig on behalf of Sigma Prime. I will use the address
michaelsproul.eth). I’ve signed a message from this address and published it to Twitter here:
I have also published the same signature as a Github Gist: Lido DAO Relay Maintenance Committee · GitHub
Thanks for including us. It’s a pleasure to be included and part of ensuring the best interests for Lido and the health of the Ethereum network here.
I am honoured to be part of this team and have the opportunity to do well for the Lido community.
You can find my tweet with corresponding address (mrsisyphos.eth) and signature verification here.
I would be honored to be part of the Relay Maintenance Committee
@IsdrsP is looking to join the @LidoFinance DAO Relay Maintenance Committee multisig with address 0x783EA934d543CD1ccfd920639A7539a0BD3895e2
Tweet with signed message is at https://twitter.com/yorickdowne/status/1601284004631941120?s=20&t=Qv2CBYDSEtNaWBIdQtKvYQ
“@yorickdowne is looking to join Lido DAO Relay Maintenance Committee multisig with address 0xeCbb058Fc429941124a2b8d0984354c3132F536f”
The Snapshot vote for the proposal to update the Block Proposer Rewards Policy and form and authorize the RMC is live
The omnibus vote is launched! The main phase lasts 48 hours and ends an Thu, Jan 12, at 2 PM UTC.
Please cast your votes!
If you have any questions about the vote, feel free to ask!
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.
Hi there, thank you so much for the opportunity, feeling great to be part of the community! Looking forward to learn and contribute here!
Below is my tweet and here is my sign has - 63dd5d74c369c80586697b59521521454b9d51307e6bb70c4f7beababfc849d17acaac1830bef45c2ef12e61367128cc8bd09d1666ea802c8ae8e8e191cb41e600
Thank you for your service and welcome @Dharmendra . The RMC membership swap was actioned late last week and can be seen here
Ethereum Transaction Hash (Txhash) Details | Etherscan.