Skip to main content

​
Why use this method?

Opting-in validators through the Lido Registry is ideal for validators that already exist through Lido and want to earn additional rewards.

​
Overview

⚠️ Important Notes:
  • This contract is only deployed on Hoodi testnet at the moment. Mainnet and frontend integration coming soon!
  • Operators must be whitelisted by our team before registering (see step 1 below).

​
Contract

You can interact directly with the Hoodi contract on Etherscan using the “Write as Proxy” tab: Lido Registry Hoodi Contract

​
Registering as an Operator

​
Step 1: Get Whitelisted

To register, you must first be whitelisted as an operator. To request whitelisting, please fill out this short google form with your operator info, or reach out to our team through telegram.

​
Step 2: Call addStake

Once whitelisted, you can register by calling: 
addStake(bytes[] blsKeys)
  • blsKeys: Provide a list of your validator public keys.
  • You must also provide the required ETH collateral when calling.
Formatting Note for Etherscan: When providing bytes[] input on Etherscan, use the format: 
0xkey1,0xkey2,0xkey3,...
(No brackets, no quotes)

​
Stake Requirement

The parameter VanillaRegistry.minStake determines how much ETH must be staked per validator pubkey to opt-in to mev-commit:
  • Mainnet: 1 ETH (not live yet)
  • Hoodi: 0.1 ETH

​
Withdrawing

If you need to deregister and withdraw:
  1. Call unstake(bytes[] blsKeys) to start the process. Validators are considered opted out during this time.
  2. Wait 96 blocks on Hoodi (the unstaking period).
  3. Call withdraw(bytes[] blsKeys) to receive your ETH back.

​
Relay Filtering

Opting in on mainnet requires agreement to only use opted-in relays, but these requirements do not exist on Hoodi at this time.
⌘I