EigenLayer is an Ethereum protocol that introduced a restaking marketplace in which staked assets can be used to provide crypto-economic security to additional protocols and services. Instead of limiting the economic commitment behind staked ETH to Ethereum consensus, EigenLayer allows participants to opt into additional validation tasks and potentially earn rewards for accepting additional responsibilities.
The protocol launched on Ethereum mainnet in 2023 and became one of the projects most closely associated with the concept of restaking. Its central idea is that new decentralised infrastructure should not always need to build a completely separate validator network and security model from the beginning. Services can instead obtain security from assets and operators participating through EigenLayer.
These services are known in the EigenLayer ecosystem as Actively Validated Services, or AVSs. They can include systems for data availability, interoperability, verification, sequencing, zero-knowledge infrastructure, and other functions that require operators to perform objectively verifiable tasks.
EigenLayer is therefore not a new Layer 1 blockchain and does not replace Ethereum staking. It is an Ethereum-based coordination layer connecting capital providers, infrastructure operators, and services seeking economic security. Its architecture effectively creates a marketplace where staked or otherwise eligible assets can be allocated to additional validation responsibilities.
Why EigenLayer Was Created
Launching decentralised infrastructure involves a difficult security problem. A new protocol may require a network of independent operators to verify information or perform computation, but attracting those operators is only part of the challenge. The system also needs economic incentives strong enough to discourage malicious behaviour.
One common approach is to issue a native token and require operators to stake it. The value locked in the protocol then acts as economic collateral. However, this requires the project to establish a sufficiently valuable token and a broad validator community before its security model becomes robust.
It also fragments capital. Ethereum has a large amount of ETH economically committed to Proof of Stake, while every additional network traditionally needs to establish its own pool of security.
EigenLayer was designed to make existing crypto-economic resources reusable. Ethereum stakers and other eligible participants can opt into additional responsibilities, allowing external services to obtain security without necessarily creating an entirely independent validator economy.
The protocol does not simply give an AVS “Ethereum security”. Ethereum consensus remains separate. Instead, EigenLayer creates mechanisms through which capital and operators can make additional commitments that are economically enforceable according to the conditions of participating services.
This distinction matters because the security of an AVS depends on its own design, operator set, allocated stake or other collateral, slashing conditions where applicable, and technical implementation. A service built through EigenLayer does not automatically become as secure as Ethereum itself.
How EigenLayer Works
EigenLayer coordinates several groups with different roles. Restakers provide economic capital, operators perform technical tasks, and AVSs consume validation services.
A participant can delegate economic backing to an EigenLayer operator rather than personally running infrastructure for every service. Operators can then register with selected AVSs and run the software required by those systems.
A simplified EigenLayer workflow can be described as follows:
- A participant commits an eligible asset to EigenLayer’s restaking infrastructure.
- The participant delegates to an operator or, where appropriate, operates infrastructure directly.
- Operators choose which AVSs they want to support.
- Each AVS defines the tasks and conditions associated with its service.
- Operators run the required software and perform validation or other protocol-specific duties.
- AVSs can distribute rewards according to their economic models.
- Where enforceable slashing conditions apply, failures or objectively attributable violations can expose allocated economic security to penalties.
This creates a separation between capital and computation. A user does not need to maintain servers simply because they want economic exposure to restaking. Professional operators can perform the technical work while receiving delegated backing.
Likewise, an AVS does not need to recruit every capital provider individually. It can access operators and economic commitments already participating in the EigenLayer ecosystem.
The model resembles a market for decentralised verification. Different services can compete for security, while operators can decide which services offer an attractive balance between rewards, infrastructure costs, and risk.
Restakers, Operators and AVSs
The relationships between the main EigenLayer participants explain much of the protocol’s architecture.
| Participant | Primary Role | Provides | Potential Return | Main Exposure |
| Restaker | Supplies economic backing | Eligible restaked assets | Restaking-related rewards | Protocol, delegation and service risks |
| Operator | Performs technical tasks | Infrastructure and validation | Operator and AVS rewards | Operational failures and service-specific penalties |
| AVS | Consumes decentralised security | Service rules and reward mechanisms | Security for its protocol | Operator quality and economic security |
| EigenLayer | Coordinates the market | Restaking, delegation and allocation infrastructure | Protocol ecosystem growth | Smart contract and mechanism-design risks |
An operator is not the same as an Ethereum validator, although the same organisation can perform both roles. Ethereum validators have duties defined by Ethereum consensus. EigenLayer operators perform tasks defined by the services they join.
Similarly, AVSs are not Ethereum shards or Layer 2 networks by definition. An AVS is a broad category for a service requiring distributed operators and economic accountability. The actual product can perform very different functions.
This flexibility is one reason EigenLayer attracted projects from several infrastructure categories rather than only one type of blockchain application.
What Are Actively Validated Services?
An Actively Validated Service is a system that uses EigenLayer operators and economic security to perform functions outside Ethereum’s normal consensus responsibilities.
One of the earliest prominent examples was EigenDA, a data availability service developed within the EigenLayer ecosystem. Rollups need data availability so transaction information remains accessible for verification. EigenDA was designed to provide this function through a specialised operator network rather than requiring all data to be published directly through Ethereum’s native data availability mechanisms.
The AVS concept is broader than data availability. Potential and deployed use cases across the ecosystem include:
- data availability infrastructure for rollups;
- oracle networks supplying external information to blockchain applications;
- cross-chain interoperability and message verification;
- decentralised sequencing infrastructure;
- coprocessors performing specialised computations;
- zero-knowledge proof and verification infrastructure;
- monitoring and other services requiring economically accountable operators.
The value proposition differs by application. A new oracle network, for example, needs operators willing to provide correct data. A bridge may need independent parties to verify events across several blockchains. A specialised computation service may need operators to perform work that is inefficient to execute directly on Ethereum.
EigenLayer gives these projects access to an existing marketplace of operators and economic backing.
However, an AVS still needs a viable business model. Restaking can help solve the security bootstrapping problem, but it does not create demand for the service itself. Ultimately, AVSs need users or protocols willing to pay enough for their services to compensate operators and capital providers.
Slashing and the Security Model
The concept of slashing is important to EigenLayer because economic security requires consequences for certain forms of incorrect behaviour.
Ethereum already uses penalties and slashing to enforce validator responsibilities at the consensus layer. EigenLayer extends the general concept of economically enforceable commitments to additional services, but the conditions are not identical to Ethereum’s.
An AVS may need operators to sign correct messages, maintain availability, verify data, or perform another specific task. If a violation can be objectively demonstrated according to the system’s rules, allocated economic security can potentially be penalised.
EigenLayer introduced slashing functionality as its architecture matured rather than treating every early restaking position as immediately exposed to arbitrary AVS slashing. This distinction is important when discussing the historical development of the protocol.
The difficulty is designing conditions that are precise enough to avoid penalising honest participants incorrectly. Not every service failure can be reduced to a simple cryptographic proof. Some tasks involve more complex assumptions, and poorly designed slashing logic could create substantial risk for operators and delegators.
This means that restakers need to evaluate more than headline reward rates. The services selected by an operator determine which additional responsibilities and risks can affect the delegated position.
EIGEN Token and Intersubjective Faults
EigenLayer’s development eventually expanded beyond using restaked assets purely as economic collateral. The ecosystem introduced the EIGEN token, adding another mechanism intended to address types of failures that cannot always be resolved through purely objective on-chain evidence.
Some blockchain faults are objective. For example, two conflicting cryptographic signatures can sometimes provide clear evidence that an operator violated a rule. Smart contracts can evaluate such evidence without asking participants for subjective judgement.
Other disputes are more difficult. Participants may broadly agree that a service behaved incorrectly even though the fault cannot be proven using only deterministic Ethereum computation. EigenLayer has described this category using the concept of intersubjective faults.
EIGEN and the broader intersubjective staking design were developed to address this class of problem. This extends the scope of the ecosystem beyond simply reusing ETH-related economic security.
The distinction is technically significant because not every decentralised service can define all malicious behaviour in a form that Ethereum smart contracts can evaluate automatically. Systems that depend on external information, complex computations, or social agreement may need additional mechanisms.
EigenLayer, Liquid Staking and Liquid Restaking
EigenLayer is closely associated with Liquid Staking Tokens and Liquid Restaking Tokens, but these terms describe different layers of the ecosystem.
An LST represents assets participating in staking. An LRT represents a managed liquid restaking position. EigenLayer itself provides restaking infrastructure rather than being an LST or LRT issuer in the general sense.
Third-party liquid restaking protocols emerged partly to simplify interaction with systems such as EigenLayer. Instead of requiring users to manage restaking positions and operator delegation directly, these protocols can aggregate deposits, select strategies, and issue transferable LRTs.
This can improve usability and liquidity but adds another smart contract and governance layer. A user entering through an LRT provider may be exposed to Ethereum staking, the underlying staking asset, EigenLayer, operators, AVSs, and the LRT protocol itself.
EigenLayer should therefore not be treated as synonymous with liquid restaking. Liquid restaking is one way users and protocols can build financial products around restaking infrastructure.
Risks and Economic Questions Around EigenLayer
EigenLayer increases the potential productivity of staked capital, but the same capital reuse creates interconnected risks. If one pool of economic backing supports several services, failures can potentially propagate between them.
Operator concentration is one concern. Large professional operators may attract substantial delegations and participate in many AVSs. This can make the ecosystem operationally efficient but can also create correlated exposure if a widely used operator experiences a software failure, security breach, or serious configuration error.
Smart contract risk exists at the EigenLayer level and can increase when additional DeFi protocols are added around restaking positions. AVSs introduce their own code and economic assumptions.
Another question concerns sustainable rewards. Early crypto networks frequently use token incentives to attract capital and operators. Long-term restaking economics require services that generate enough genuine demand to pay for the security they consume.
There are also broader Ethereum considerations. Restaking should not create incentives that encourage validators or operators to prioritise external systems over Ethereum consensus. Keeping the base network’s security responsibilities isolated from failures elsewhere is an important design objective.
For users, this means that Total Value Locked or the number of supported services cannot independently demonstrate safety. The distribution of operators, quality of AVSs, reward sources, slashing conditions, contract security, and withdrawal mechanisms all contribute to the actual risk profile.
EigenLayer’s Role in Ethereum Infrastructure
EigenLayer introduced a new way of thinking about Proof of Stake capital. Instead of treating staked assets as useful only for the consensus system to which they were originally committed, the protocol created infrastructure for allocating additional economic commitments to other decentralised services.
This can lower the barrier to launching infrastructure that would otherwise need to build its own validator network from scratch. AVSs can access operators and economic backing, operators can offer their infrastructure to multiple services, and restakers can potentially receive compensation for providing additional security.
The model also creates a new type of coordination problem. The more services share operators and capital, the more important risk isolation becomes. Capital efficiency and systemic independence can pull in opposite directions.
EigenLayer’s significance therefore extends beyond additional staking yield. It is an attempt to create an open market for crypto-economic security on Ethereum, connecting protocols that need validation with operators and capital capable of providing it.
Whether that market becomes a durable part of Ethereum infrastructure will depend on the quality and economic demand of the services built around it. Restaking can provide security resources, but sustainable growth ultimately requires AVSs that solve real problems and generate enough value to compensate the participants securing them.