Skip to main content

Staking Nodes

Your Vault is created but not yet operational. Your infrastructure must be ready.

Staking Nodes​

Ensure your node infrastructure meets the technical requirements below for reliable operation.

IconAutomated Node Setup Available

A new experimental feature allows the Operator Service to automatically install and manage execution and consensus clients (Reth and Lighthouse). See Automated Node Setup → for details.

Execution Client​

Your execution node must be fully synced and running. Any client that supports the ETH Execution API specification ↗ can be used:

IconConfigure execution client

Preserve event logs to ensure the Operator Service functions correctly. Some clients require specific configuration to sync event logs and prevent event log pruning:

# Ethereum Mainnet
erigon --prune=receipts --prune.to=18470089

# For other networks, adjust the block number to the Keeper contract creation block

These flags prevent pruning of event logs as required by the Operator Service.

Consensus Client​

Your consensus node must be fully synced and running. Any client that supports the ETH Beacon Node API specification ↗ can be used:

Validator Client​

Configure the suggested-fee-recipient of your validator client with the correct fee recipient address. This is the Block reward recipient shown in the Details section at the bottom of your Vault page. An incorrect value will result in penalties for your Vault in the Smoothing Pool and will trigger a warning on the Vault page, alerting users to an invalid validator setup.

MEV-Boost​

Set up MEV-Boost ↗ to capture execution layer rewards. MEV-Boost is open source middleware that connects your validator to a network of block builders competing to produce the most profitable block, maximizing your Vault's execution-layer revenue.

If your Vault uses the Smoothing Pool, you must use one of the StakeWise DAO-approved MEV relays (see Smoothing Pool Relays →). Learn more about MEV Strategy →.

Last updated on