A liquid Restaking Token (LRT, such as weETH or pufETH) is the receipt token you get for depositing ETH into the EigenLayer ecosystem, letting holders earn restaking yield without running Validator infrastructure themselves. The key difference from plain ETH Staking is that LRT capital is further delegated to operators who validate for multiple AVSs — the source of the extra yield, and the extra risk.
This gap exists because it's practically impossible for an individual holder to independently evaluate every operator's reliability and every AVS's slashing conditions and track record — that information is scattered, partly non-standardized, and EigenLayer's own safety-scoring system is still under development. LRT protocols abstract this complexity away in exchange for usability, at the cost of holders being unable to see the real risk composition behind their yield.
The mechanics run as follows: a holder deposits ETH and receives an LRT → the protocol delegates that capital across multiple operators according to its strategy → each operator chooses which AVSs to validate for → if any AVS or its operator commits a provable violation (like double-signing) or suffers an external exploit, slashing triggers at that layer → the loss is reflected proportionally in the net value of the entire underlying asset pool, shared by every holder of that LRT regardless of whether they knew about or chose that particular AVS.
For a holder, this means the headline APY isn't risk-free interest — it's compensation for absorbing an entire delegation chain's worth of risk. Before deciding how much of a portfolio to put into an LRT, it's worth spending a few minutes looking at the protocol's published operator concentration and AVS list, not just the yield number — especially now that slashing is live onchain and no longer a hypothetical risk described only in a Whitepaper.
EigenLayer activated production slashing on mainnet on April 17, 2026. Depending on how it is counted, restaked assets sit somewhere between about $15 billion and $20 billion, with more than 4.3 million ETH delegated. For most people holding a liquid Restaking Token (LRT) like weETH or pufETH, the experience is simple: deposit ETH, receive a token that appreciates over time, and watch a clean APY figure in a wallet or dashboard. What that number doesn't show is the full delegation chain sitting underneath it — and holders typically only see the very front of that chain.
The full path runs like this: you deposit ETH into an LRT protocol, the protocol delegates that capital to a set of operators (Node runners), and each operator chooses which AVSs (Actively Validated Services — new Oracle networks, bridge validation layers, and similar infrastructure) to validate for. When a slashing event is triggered, it happens at the operator-AVS layer, but the loss flows straight through to the underlying asset pool and is spread proportionally across every holder of that LRT — whether or not you ever chose that AVS, and whether or not you knew it existed.
This isn't a design flaw so much as the tradeoff baked into the liquid restaking model itself. The entire point of an LRT is to let ordinary holders skip the work of picking operators or evaluating individual AVS risk, in exchange for instant liquidity and a simple experience. Protocols concentrate the operator-selection and capital-allocation decisions at the governance or strategy-contract layer, which makes the product easy to use — but it also compresses the information that reaches the end holder. You can see that yield exists; it's much harder to see what risk was taken on to produce it.
More importantly, EigenLayer's operator safety-scoring system is, as of now, still under active development. Not every AVS publishes standardized, easily readable slashing conditions or historical records. Even a holder who wants to dig in will find the completeness of available data varies significantly from one AVS to another.
Slashing splits into two fundamentally different scenarios. The first is a provable violation by an operator or the AVS it validates — signing conflicting state attestations, double-signing — where slashing is the system working as designed, penalizing malicious or negligent behavior in essentially the same logic as a proof-of-work miner losing a Block reward. The second scenario is different in kind: the AVS's own contract gets hacked or its logic exploited. That's an external attack, not a deliberate governance penalty — but the resulting losses still propagate up the same delegation chain. Holders sit at the very top, absorbing the combined outcome of two structurally different risk sources, while seeing only a single unified drop in net value.
Most mainstream LRT protocols now publish their operator list and delegation weightings, and some (ether.fi, Puffer among them) have begun publishing which AVSs each operator validates — that's the first layer of information actually available to check. Practical steps include periodically checking protocol governance forums or official documentation for operator concentration (a small number of operators controlling most delegated capital means a more concentrated single-point-of-failure risk); watching whether a protocol applies risk tiers or observation periods to newly onboarded AVSs; and, for holders who care specifically about exposure, some protocols let you choose a more conservative vault that only delegates to operators validating fewer AVSs with longer track records, trading some yield for lower tail risk. Redeeming out entirely is the most direct option, but it also means giving up restaking yield altogether — not a necessary move for most holders. The middle ground — choosing a lower-risk vault tier or periodically reviewing the delegation structure — is usually the more practical path.