Restaking in 2026: Slashing Activation & Market Reality
Restaking has moved past early point schemes. Penalties are active, institutional capital is selective, and yields reflect real service demand.
Slashing is active
Early restaking ran with penalties disabled or gated behind emergency pause switches. Depositors earned reward points without facing real capital losses.
Slashing went live on EigenLayer mainnet in April 2025, and by EigenLayer's own description it is opt-in: it reaches an operator, and the stakers delegated to that operator, only where the operator has joined a slashable operator set created by a service. Inside such a set the standard is mechanical rather than moral. A misconfigured node, contradictory signatures or buggy client code breach the rules as effectively as malice would, and an operator's staked funds can be burned for it. Burning is the stated default; EigenLayer listed redistribution of slashed funds as a later addition, without a date.
Restaking is a separate decision
Staking a token and restaking it are two choices, not one. Staked capital does not become restaked capital by default: an operator has to join a service's operator set, and a depositor has to delegate to an operator who has. Nothing about holding a staked asset, or a receipt for one, commits it to a second rulebook.
That changes how the extra reward should be read. It is not a yield that staking was already producing and restaking merely revealed. It is payment for accepting slashing conditions the base asset does not carry, taken on deliberately. Whether the payment is adequate is the subject of the next section.
The reality of net yield
Headline APY figures often ignore operational frictions. In practice, net payouts reflect a strict deduction waterfall:
Net Yield = Base Staking + (Gross AVS Fees − Operator Commission − Protocol Fees − Gas Drag)
Without substantial fee-paying user volume on secondary services, gross yields remain thin, while downside slashing exposure remains constant.
Sources
- Slashing Goes Live on Mainnet — Eigen Labs, 17 April 2025. Source for the activation date, for slashing being opt-in per operator set, and for burning being the default with redistribution listed as a later addition. The protocol's own announcement. It states both that slashing is live and that it was expected to go live later the same day, so it supports the month rather than an exact moment.