eigen layer is an Ethereum restaking protocol where restakers supply stake, operators run service software, and services pay rewards for security backed by slashable stake. Because each role’s reward depends on the others doing their jobs, identify your place in eigen layer before committing ETH or running software. EigenLayer’s withdrawal delay also matters when you leave.
Who Are the Three Parties in eigen layer?
Restakers provide staked ETH or a supported liquid staking token (LST) and delegate that stake to an operator. With native ETH, an EigenPod connects an Ethereum validator’s withdrawal credentials to restaking; with an LST, the restaker deposits an eligible token. Delegation determines which operator can use the stake to secure services.
Operators run the software services require and choose which services to support. They may earn a commission from rewards paid for that work. Their choices matter to restakers: an operator’s service commitments determine which tasks delegated stake backs and which failures may expose it to slashing.
Services, often called actively validated services (AVSs), define the work, rewards, and conditions for slashing. EigenDA is one example. An AVS relies on operators to perform its tasks and on restakers’ stake to make failures economically costly.
What Does Each Role Contribute Before Rewards Flow?
A restaker needs eligible stake and an active delegation; an operator needs to join a service and run its software; and the service needs to define tasks and reward terms. Each part must be in place before service work can generate rewards for that stake.
Imagine a restaker delegating to an operator that supports EigenDA. The deposit must be accepted and the delegation active before the operator can use that stake as backing. If the operator has joined no service, the restaker has committed capital but cannot expect rewards from service work that has not begun. In an interface, a confirmed deposit, active operator, and the operator’s service commitments show where the process stands.
Restakers tie up capital and receive rewards under the applicable service and operator terms. Operators pay for machines, monitoring, and reliable execution; commission is their share of rewards for that work. Services fund rewards to attract operators and must specify behavior clearly enough to judge a fault. Payment size and timing vary by service and operator, so Ethereum staking yield alone does not estimate restaking income.
Who Bears Slashing Risk, and How Long Does Exit Take?
Slashing exposure follows the operator’s service choices, and withdrawing backing stake requires waiting through the protocol’s withdrawal delay. For a restaker, choosing an operator is therefore the decisive risk choice.
If that operator joins a service with stricter fault conditions after you delegate, your stake’s exposure can change without another action from you. Review the operator’s supported AVSs and commission before delegating, and revisit its service commitments while you remain delegated. Slashing can remove principal; an advertised reward rate does not set a maximum loss.
Operators must meet each AVS’s requirements. A missed task or faulty software can trigger a service’s stated penalty, so joining another AVS adds obligations alongside potential rewards. A service needs verifiable tasks and enough dependable operators; otherwise, it may lack the security it sought to buy.
An exit request starts the withdrawal process; it does not release ETH at once. The wait depends on protocol settings and the stake’s position in that process. Restakers must allow for illiquidity, operators must plan changes to commitments around the delay, and services must account for backing that leaves on that schedule. Before participating, make sure you can identify the eligible deposit, chosen operator, supported AVSs, commission, slash rules, and applicable withdrawal delay.