EigenLayer has crossed 5 million ETH in restaking deposits across operators, marking another major scale milestone for one of Ethereum’s most closely watched DeFi infrastructure protocols.

The figure includes native ETH and liquid staking token deposits, so it needs to be read carefully. Still, 5 million ETH is a huge number, and it shows how large the restaking market has become.

EigenLayer’s pitch has always been simple but ambitious: let staked ETH secure more than Ethereum alone.

That idea has pulled in capital quickly, but it also created a new set of risks that the market is still learning how to price.

For more details, visit the official Defillama platform.

TL;DR

• EigenLayer restaking deposits have crossed 5 million ETH.
• The figure includes native ETH and liquid staking token deposits.
• Restaking scale is growing, but the model carries additional risk.

Why Restaking Became So Big

Ethereum staking created a large pool of capital earning yield.

EigenLayer asks a natural next question: can that same economic security be reused to support other services? Those services, often called AVSs, can include data availability layers, oracle systems, middleware, rollup infrastructure, and other networks that need security.

For depositors, the attraction is extra yield.

For builders, the attraction is access to Ethereum-linked security without bootstrapping everything from zero.

That combination explains why restaking has grown so quickly.

5M ETH Is A Serious Milestone

Crossing 5 million ETH puts EigenLayer into a different scale category.

This is no longer a small experiment. It is a major concentration of staked assets being routed through a restaking system. That can strengthen Ethereum’s wider infrastructure economy, but it also means failures would matter.

The larger restaking gets, the more important risk controls become.

Slashing conditions, operator performance, AVS security, smart contract risk, and liquidity assumptions all need to be understood properly.

Native ETH And LSTs Are Not The Same

The deposit figure combines different kinds of exposure.

Native ETH restaking is not identical to restaking liquid staking tokens. LSTs already carry their own smart contract, liquidity, and staking-provider risks. Adding restaking on top can create a more layered risk profile.

That does not make the model bad.

It means users need to understand what they are depositing and what risks they are accepting.

A headline number is useful, but the composition behind it matters.

AVS Growth Is The Other Half

Deposits alone do not complete the story.

EigenLayer also needs Actively Validated Services that create real demand for restaked security. If AVSs grow and generate sustainable fees, the model becomes more compelling. If deposits grow faster than useful services, the market may start asking whether the yield is durable.

Protocol metrics point to 18 active security networks, which gives the milestone more context.

Restaking is not only attracting deposits. It is also building out the services that are meant to use those deposits.

The Risk Conversation Is Not Going Away

Restaking has supporters and critics for good reason.

Supporters see it as a way to make Ethereum’s security more productive. Critics worry about correlated risk, complex slashing, leverage-like behavior, and contagion if restaking systems fail.

Both sides have a point.

EigenLayer’s 5 million ETH milestone shows the market wants the product. Now the harder work is making sure the risk is understood as clearly as the opportunity.

This article draws on EigenLayer restaking data from DeFiLlama and related protocol metrics.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released by Defillama. at Defillama

EigenLayer’s forum is debating ELIP-018, a draft proposal that introduces a framework called RETIRE, short for Retirement Enabling Terminal, Irreversible Restaking Exit.

The name is a mouthful, but the goal is fairly direct: create a terminal exit route for restakers who want to leave certain restaking positions in a final and irreversible way, without triggering unnecessary slashing mechanics.

This is still a draft proposal. It has not been implemented or approved by the DAO.

Still, it touches one of the more important questions in restaking: how users exit safely when the system becomes more complex.

Restaking can increase capital efficiency and security coordination, but it also creates layers of obligations between stakers, operators, AVSs, slashing rules, and withdrawal paths. The more layered the system becomes, the more important clean exits become.

TL;DR

• EigenLayer is debating draft proposal ELIP-018.
• The proposal introduces the RETIRE framework for terminal, irreversible restaking exits.
• It is a draft and has not been implemented or approved.

Why Restaking Exits Are Complicated

Restaking is powerful because it lets staked assets support additional services.

Instead of securing only Ethereum, restaked capital can help secure actively validated services, or AVSs, through EigenLayer’s framework. That creates new economic opportunities for stakers and operators.

But it also creates new risk.

If restaked assets are tied to additional services, then exiting is not just a simple withdrawal question. The system has to account for obligations, slashing windows, service responsibilities, operator commitments, and the timing of when a restaker is no longer exposed.

That is where proposals like ELIP-018 become relevant.

A messy exit process can make users nervous. If restakers do not understand when their obligations end, or whether an exit could accidentally trigger penalties, they may be less willing to participate.

A clear terminal exit route can reduce that uncertainty.

RETIRE Is About Finality

The word “irreversible” is doing a lot of work here.

A terminal exit route is not meant to be a casual toggle. It is designed to be final. Once a restaker chooses that path, the system treats the exit as a permanent move rather than a temporary state change.

That can simplify accounting and reduce ambiguity.

In complex staking systems, ambiguity is dangerous. If one part of the protocol believes a restaker is still active and another believes they are leaving, slashing and responsibility questions can become messy.

RETIRE appears aimed at making the end state clearer.

That does not mean the proposal is automatically the right design. It means the issue being addressed is real.

Slashing Risk Shapes User Confidence

Slashing is necessary in many proof-of-stake and restaking systems because it creates consequences for bad behavior. But users also need confidence that they will not be punished unfairly because of unclear exit mechanics.

That is especially important in restaking, where users may be exposed to multiple services and risk layers.

If exit routes are confusing, conservative users may stay away. If exits are too easy or poorly designed, services may face weaker security guarantees. The protocol needs a balance.

ELIP-018 is part of that balance debate.

It tries to create a route that helps restakers leave while preserving the logic of the system.

Draft Stage Means Debate Comes First

The proposal is still a draft, which is exactly how it should be treated.

EigenLayer’s community still needs to evaluate whether RETIRE is necessary, whether the mechanics are safe, whether edge cases exist, and how the framework interacts with existing withdrawal and slashing rules.

That means no one should assume the feature is live.

Crypto governance discussions can sound final because the language is technical and formal. But drafts are drafts. They are where design gets tested in public before implementation.

For restakers, the practical takeaway is not to change behavior today. It is to watch how the exit framework evolves.

EigenLayer Is Moving From Growth To System Design

EigenLayer’s early story was about growth: restaking demand, AVS launches, operator networks, and the possibility of reusing Ethereum security across many services.

Now the ecosystem is moving deeper into system design.

That means governance has to answer less glamorous but more important questions. How do exits work? How do emissions work? How does slashing interact with different services? How should operators be managed? How do users understand risk?

ELIP-018 belongs in that second phase.

It is not a hype announcement. It is infrastructure governance. But for a restaking protocol, that is exactly where long-term trust is built.

If EigenLayer wants restaking to become a durable security marketplace, exits need to be as carefully designed as deposits.

RETIRE may or may not become the final model, but the discussion shows the ecosystem is taking that problem seriously.

This article is based on the EigenLayer forum draft proposal for ELIP-018 and the RETIRE framework.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released in disclosures at primary source documentation.