Eigen layer restaking: when you need a validator, and when you do not

Eigen layer restaking does not require every user to run a validator: native ETH restaking does, while supported liquid staking tokens (LSTs) let holders participate without operating one. Both routes put assets behind additional services, known as Actively Validated Services, or AVSs. The choice is less about which route earns more and more about what you hold, what you can operate, and which risks you are willing to take.

Before restaking, ETH holders generally chose between running an Ethereum validator themselves and staking through a provider that issued an LST. Restaking adds another layer: assets already committed to Ethereum can also back services with their own rules and penalties. The eigen layer model makes that additional commitment possible through native ETH and supported tokens. The trade-off is that one pool of capital now supports more than one system.

Do you need a validator for eigen layer restaking?

No, unless you choose the native ETH route. Native restaking starts with ETH staked directly on Ethereum. The validator’s withdrawal credentials point to an EigenPod, which connects the stake to EigenLayer. The person or organization using this route must run the validator or arrange for an operator to do so. The validator continues to perform Ethereum duties; restaking adds separate duties and exposure tied to AVSs.

With an LST route, the holder deposits an eligible token representing ETH staked through another provider. They do not need to run an Ethereum validator because that provider already handles the underlying validator operation. They can then delegate their restaked position to an EigenLayer operator, who runs the software needed by selected services. The LST holder supplies capital; the operator supplies the service work.

That distinction matters. “Validator” can mean an Ethereum validator securing the base chain, or an EigenLayer operator performing work for an AVS. These roles can overlap, but they are not the same requirement for every restaker. A token holder can participate without becoming either kind of operator.

How do native ETH and LST restaking differ?

Native restaking offers a more direct relationship with the Ethereum stake. The staker controls the validator setup and avoids depending on an LST issuer to represent the position. In exchange, the route requires validator infrastructure, ongoing maintenance and understanding of withdrawal credentials. It fits experienced home stakers and professional operators who want direct control over their stake.

An LST makes the entry point simpler for people who already hold a supported token. It avoids running validator hardware, but it adds dependencies: the LST’s issuer and redemption process, the EigenLayer contracts, the chosen operator, and the AVSs to which that operator commits. The token may also trade away from the value of the ETH it represents. A liquid token is not a promise of immediate redemption at par.

Neither route removes the need to choose how the position is used. Restakers delegate to operators, and operators opt into services whose rules can differ. A service may impose penalties for failing to perform its work or for violating its requirements. Rewards, where offered, depend on the service and its terms; a restaked asset does not guarantee a particular return.

For most people who do not already operate an Ethereum validator, an eligible LST is the more accessible route. That convenience is useful only if they accept the extra issuer and token risks. A validator operator may prefer native restaking for direct control, but it still adds AVS obligations and slashing exposure. If neither set of trade-offs is clear, holding ETH or an LST without restaking is a reasonable alternative.

What should you check before restaking?

Check the complete chain of responsibilities before depositing. In particular, identify who controls the validator, who selects AVSs, and what withdrawal and slashing rules apply. EigenLayer’s contracts support withdrawals through a queue, so a restaked position should not be treated as cash that can be recalled immediately. The time and outcome can depend on the asset, protocol state and any applicable penalties.

• Confirm that the token is currently supported and understand how its issuer handles redemption.
• Review the operator’s service commitments, fee terms and approach to selecting AVSs.
• Read each AVS’s penalty rules and identify which portion of the position is exposed.
• Check the current withdrawal process and plan for a delay before funds become available.

Restaking is not simply another way to stake ETH. It reuses staked capital to support additional services, and that reuse is the source of both its potential rewards and its added risk. Native ETH suits people prepared to run validator infrastructure; LSTs suit holders who want to delegate the work and accept the token’s extra dependencies. The signals to watch are changes in supported assets, operator and AVS commitments, slashing rules, reward terms and withdrawal conditions.