Node Operator Registry - Name & Reward address change

Node Operators
24

The voting has been restarted again.
The main phase will last until January 25th, Thursday, 14:01.
Please vote!! Lido DAO Voting UI

1 Like
25

The on-chain vote gathered quorum and was executed! Thank you for taking part and casting your votes!

2 Likes
26

Request to change on-chain name from “CryptoManufaktur” to “Galaxy”:

  • #id - 23

  • on-chain name (change): Galaxy

  • reward address (change): 0x3C3F243263d3106Fdb31eCf2248f9bC82F723c4B

2 Likes
27

Hello Zane. For reward address changes, a signed message to that effect is needed both from the current address as well as the new address (I’ve bundled the name change in there too for good measure, albeit not strictly necessary).

Instructions can be found here: Verifying address ownership for Lido DAO ops | Lido Docs

I think the below would work, but want a confirm from @zuzu_eeka :

“As a part of the Galaxy Digital acquisition of CMF, a name change request to ‘Galaxy’ and a reward address change from ‘0x59eCf48345A221E0731E785ED79eD40d0A94E2A5’ to ‘0x3C3F243263d3106Fdb31eCf2248f9bC82F723c4B’ is requested.”

and publish a link to the signed messages here.

3 Likes
28
1 Like
29

Signed with the new wallet: Ethereum Verified Signed Message

4 Likes
30

Hey Yorick. Thanks, the message looks OK from NOM side.

Just a quick note from my side re: timing of the administrative changes discussed here in relation to the acquisition and “continuance” discussion + possible vote in the other thread here. The way I see it, name and address changes are things that NOs could ostensibly do on their own without requiring a snapshot => on-chain vote flow, were the appropriate governance rails for such actions set up via Easy Track, just like key limit increases. Since these rails currently aren’t set up (and IIRC there was no specific reason they weren’t apart from that they happen so rarely as to necessitate a full ET-based ability to do so), I think an on-chain vote to make the name and address changes to effectively reflect the reality of the acquisition isn’t something that should affect or prejudice a vote by tokenholders on whether Galaxy (ex CMF) should continue or not.

Thus, I personally don’t see a reason not to proceed with bundling the requested updates with the next on-chain vote, even if the possible Snapshot for for continuation of participation by Galaxy may happen a bit later due to the governance schedule.

4 Likes
31

On-chain voting has started to change the name and reward address for node operator #23 in the curated set.

Cast your vote here: Lido DAO Voting UI

The main phase will continue until August 15, 2024, at 14:00 UTC. Remember to participate!

1 Like
32

We are excited to introduce our guide on how to verify on-chain voting #177 items! This note is designed to help you navigate the process with ease. If you have any questions or need further clarification, please don’t hesitate to reach out.

1 Like
33

Request to change on-chain name from “Numic” to “Pier Two”:

  • #id - 36
  • on-chain name (change): Pier Two
  • reward address (change): 0x35921FB43cB92F5Bfef7cBA1e97Eb5A21Fc2d353

Published signed messages:

3 Likes
34

Thanks! Similar to the suggestion regarding CMF and Galaxy above, I’d suggest that (provided there are no objections and that they DAO Ops contributors also think it’s OK) this get added to the next possible on-chain vote as it’s administrative while the discussion around whether Pier Two (ex Numic) should be reinstated as an active participant in the curated operator module is ongoing.

3 Likes
35

Dear Lido Community,
On-chain vote #178 has been completed and enacted. Node operators #23 and #36 have had their names and reward addresses changed.
Thank you for your votes!

4 Likes
36

Requesting a reward address change for Simply Staking operator:

  • ID: 16
  • on-chain name (no changes): Simply Staking
  • operator address (change): 0x1EC3Cbe8fb1D8019092500CcA2111C158a35bC82

Etherscan verification from old address - link here

Tx to confirm the ownership of the new multisig address (see tx data for the encoded message and can be verified via duplichecker) - link here

3 Likes