Native Restaking

EigenLayer and SSV are fully compatible and complementary for native restaking.

The only necessary configuration is setting the EigenPod as the validator's withdrawal credentials

EigenLayer is a protocol built on Ethereum that introduces restaking, allowing the reuse of ETH on the consensus layer. Thanks to EigenLayer smart contracts, users can restake their ETH or LST and extend cryptoeconomic security to additional applications on the network to earn additional rewards (head over to EigenLayer docs for more information).

This page provides guidance on how to setup EigenLayer's Native Restaking through SSV.

If you have an existing validator, you need to verify the Withdrawal Prefix. EigenLayer has a good guide to do this on this dedicated page.

Create an EigenPod

An EigenPod is a smart contract that facilitates the EigenLayer protocol in monitoring and managing balance and withdrawal statuses.

Head over to the dedicated guide on EigenLayer docs for indications on how to create an EigenPod.

The smart contract address you will get at the end of the process will be responsible for all subsequent restaking and withdrawal activities associated with that EigenPod.

Create a new validator

Native Restaking is the process of pointing an Ethereum validator's withdrawal credentials to the user's EigenPod. So in order to do that, you need to create a new validator.

You can do that using this guide in our documentation, but the most important thing is to set the validator's withdrawal credentials to the EigenPod. So when generating the validator keys using this command:

./deposit new-mnemonic --num_validators 1  --chain mainnet  --eth1_withdrawal_address [YOUR_EIGENPOD_ADDRESS]

The --eth1_withdrawal_address parameter should be set to the EigenPod address from the previous step.

Best practices

One important thing to note is that EigenLayer limits the creation EigenPod to one per account (wallet address). This means users with multiple validators have two options:

  1. Use the same EigenPod as withdrawal credentials for multiple validators

  2. Create multiple accounts, create an EigenPod for each one, use each EigenPod as withdrawal credentials

The best practice would clearly be reusing the same EigenPod, as it means less wallet addresses to manage, less dispersion of resources, and most importantly: claiming rewards will be much cheaper.

On the other hand, it appears that the trend for EigenLayer users at the moment is to create multiple accounts and multiple EigenPods, this is likely because of airdrops, which will likely be distributed on a per-account basis.

Register validator on SSV

Thanks to, it is not necessary to operate your own validator by setting up, running and managing dedicated hardware. You can simply register it on the network, and choose which operators will run validator operations for you.

Follow this guide in our documentation to register the new validator with restaking capabilities on, just like you would do with any other Ethereum validator.

It is important to NOT direct execution rewards (suggested_fee_recipient) to the EigenPod as these funds would be irretrievable.

For more information on this topic, please refer to the dedicated learning page.

Last updated