- Create EigenPod address: construct a serialized transaction to generate an EigenPod address, which your validator can use as a withdrawal address.
- Create Staking Request: set up nodes for staking using P2P infrastructure.
- Check Request Status: check the status of the node set-up operation.
- Prepare Staking Transaction: construct a serialized transaction to deposit the stake amount with a smart contract.
- Verify Withdrawal Credentials: construct a serialized transaction to verify the validator withdrawal credentials on-chain.
- Delegate Restake to Operator: construct a serialized transaction to delegate the restake amount to the EigenLayer node operator.
1. Create eigenPod address
- Retrieve a serialized transaction to generate an EigenPod address by sending a POST request to /api/v1/eth/staking/eigenlayer/tx/create-pod. Example request:
serializeTx— serialized .to— recipient address for this transaction.gasLimit— maximum limit for this block.data— transaction data.value— amount this transaction is sending in Wei.chainId— chain ID this transaction is authorized on, as specified by EIP-155.type— EIP-2718 type of this transaction envelope.maxFeePerGas— maximum price per unit of gas this transaction will pay for the combined EIP-1559 block’s base fee and this transaction’s priority fee in Wei.maxPriorityFeePerGas— price per unit of gas in Wei, which is added to the EIP-1559 block’s base fee. This added fee is used to incentivize miners to prioritize this transaction.
-
Use
serializeTxto sign and send the signed transaction to the Ethereum network. By broadcasting this transaction, you are generating an EigenPod address. The Ethereum address used to sign this transaction will become theeigenPodOwnerAddress.
2. Create staking request
-
Prepare
idthat is an arbitrary UUID. Generate it in one of the following ways: -
Set up staking nodes through the P2P infrastructure by sending a POST request with the
RESTAKINGtype to /api/v1/eth/staking/direct/nodes-request/create. Example request:
-
id— arbitrary UUID. You can later use that UUID to check the status of the set-up operation. -
type— staking operation type:RESTAKING— value for initiating a restaking operation.REGULAR— default value used for native staking transactions.
-
validatorsCount— number of validators. One validator is equal to 32 ETH. -
feeRecipientAddress— fee recipient address. -
eigenPodOwnerAddress— owner of the EigenPod address, created in the previous step. -
controllerAddress— for the validators. -
nodesOptions: -
location— node location. Currently, onlyanyis supported.relaysSet— Miner Extractable Value () relay selection.
3. Check request status
Check the status of the node set-up operation by sending a GET request to/api/v1/eth/staking/direct/nodes-request/status/\{id}.
Example request:
id— UUID that was specified in the node set-up request.
-
id— UUID that was specified in the node set-up request. -
status— current status of the node request:init— node request is created.processing— node request is in progress.ready— backend has the deposit data for the node request.cancel— something went wrong and the deposit data was not created.
-
validatorsCount— number of validators. One validator is equal to 32 ETH. -
withdrawalAddress— withdrawal address for the validators that is set tonullby default; corresponds to the EigenPod address. -
eigenPodAddress— EigenPod address also used as the validator withdrawal address. -
eigenPodOwnerAddress— owner of the EigenPod address. -
controllerAddress— for the validators. -
feeRecipientAddress— fee recipient address. -
depositData:pubkey— validator public key.signature— validator signature.depositDataRoot— SHA-256 hash of the SSZ-encoded DepositData object; used as a protection against malformed input.withdrawalCredentials— withdrawal address credentials, passed in the expected format by the Ethereum deposit smart contract.amount— amount of ETH, denominated in Gwei, that is being deposited.depositMessageRoot— cryptographic hash of the Merkle tree’s root, ensuring the integrity and authenticity of the deposit data.forkVersion— version of the network fork that the deposit is intended for. It helps in aligning the deposit with a specific version of the protocol.eth2NetworkName— name of the Ethereum 2.0 network where the deposit is made.depositCliVersion— version of the deposit command-line interface (CLI) tool that was used to generate the deposit data.
-
createdAt— timestamp of the transaction in the ISO 8601 format.
4. Prepare staking transaction
There are two flow to make a deposit:4.1 P2P Proxy deposit
Create a serialized transaction for depositing the stake amount and send it as a POST request to /api/v1/eth/staking/direct/tx/deposit.-
withdrawalAddress— withdrawal address for the validators. For theRESTAKINGoperation type, this corresponds to theeigenPodAddressin the step 3 Check Request Status. -
depositData:pubkey— validator public key.signature— validator signature.depositDataRoot— hash of the deposit data.withdrawalCredentials— withdrawal address credentials, passed in the expected format by the Ethereum deposit smart contract.amount— amount of ETH, denominated in Gwei, that is being deposited.depositMessageRoot— cryptographic hash of the Merkle tree’s root, ensuring the integrity and authenticity of the deposit data.forkVersion— version of the network fork that the deposit is intended for. It helps in aligning the deposit with a specific version of the protocol.eth2NetworkName— name of the Ethereum 2.0 network where the deposit is made.depositCliVersion— version of the deposit command-line interface (CLI) tool that was used to generate the deposit data.
serializeTx to sign and send the signed transaction to the Ethereum network.
By broadcasting this transaction, you are depositing the required stake amount in the Ethereum deposit smart contract by using the P2P smart contract as a proxy.
4.2 Ethereum direct deposit
Use this if you prefer to interact with the official Ethereum contract without a proxy.- Take the pubkey, signature, and depositDataRoot from the deposit-data response.
- Go to the Official Ethereum Deposit Contract
- Manually execute the
depositfunction with your 32 ETH and the provided data.
5. Verify withdrawal credentials
Before starting, ensure your validator has reached theactive_ongoing status. The API identifies your associated EigenPod and ownership via the EigenPod Owner and signer of your request.
- Verify withdrawal credentials by sending a POST request to /api/v1/eth/staking/eigenlayer/tx/verify-withdrawal-credentials. This links your validator’s principal withdrawal path to your EigenPod.
eigenPodOwnerAddress— owner of the EigenPod address.pubkey— validator public key.
- Use
serializeTxto sign and send the signed transaction to the Ethereum network.
6. Delegate restake to operator
Once withdrawal credentials are verified, you can delegate your ETH restaking power to a Node Operator.6.1 Get list of operators
Retrieve the list of available EigenLayer node operators by sending a GET request to /api/v1/eth/staking/eigenlayer/operator.-
list:id— UUID that was specified in the node set-up request.name— name of provider.address— EigenLayer node operator address.
-
limit— number of resources that a single response page contains. -
offset— number of resources to exclude from a response. -
totalCount— total number of validators relevant to the current request, based on filters applied.
6.2 Prepare delegation transaction
Create a serialized transaction for delegating the restaked amount to the node operator by sending a POST request to /api/v1/eth/staking/eigenlayer/tx/delegate-to. The Eigen Pod delegated is associated to the signer of the request.operatorAddress— address of the EigenLayer node operator retrieved from the previous step, to delegate the restaked assets.
serializeTx from the previous step to sign and send the signed transaction to the Ethereum network.
By broadcasting this transaction, you are delegating your restake to the EigenLayer node operator.