Ethereum staking earns roughly 3 to 4 percent a year for locking up ETH and helping validate the network. Restaking takes the staked ETH and lets it do double duty: still securing Ethereum, but also securing other protocols on top, in exchange for additional yield. The stack grows from one source of return to many. The slashing risk grows the same way. This piece walks through what restaking actually is, how the major systems work, what the layered slashing risk means in practice, and where hardware wallet signing matters most in this stack.
A validator on Ethereum stakes 32 ETH to participate in consensus. Their ETH is locked. If they validate correctly, they earn rewards. If they violate the protocol rules (double-signing, going offline for extended periods), part of the staked ETH is slashed. Restaking adds a second layer on top of this. The staked ETH (or a derivative of it, like a liquid staking token) gets opted in to also secure a separate protocol, called an Actively Validated Service (AVS). The AVS pays additional yield for the security it gets. The restaker takes on additional slashing risk: if the AVS rules are violated, part of their ETH can be slashed even if their Ethereum validation was fine. The pioneer of this model is EigenLayer, which launched on Ethereum mainnet in 2023. By 2026, restaking is a recognized category with multiple competing implementations and tens of billions of dollars of TVL across the ecosystem.
There are several layers, and conflating them is how restakers get into trouble. Layer 1: ETH staking: Hold 32 ETH, run a validator, earn the base staking yield. Slashing risk: standard Ethereum validator misbehavior. Layer 2: Liquid staking tokens (LSTs): Instead of running a validator yourself, deposit ETH with a liquid staking protocol (Lido, Rocket Pool, others) and receive a token (stETH, rETH) representing your staked ETH. You can use that token in DeFi while still earning staking yield. The slashing risk is the same, but the LST issuer takes a cut and you've added the LST contract as a counterparty. Layer 3: Restaking: Deposit your stETH or other LST into a restaking platform like EigenLayer. The platform pools your stake and lets it be used to secure AVSs. You earn additional yield from the AVSs. Your ETH (or LST) is now exposed to slashing on both Ethereum and on every AVS you've opted into. Layer 4: Liquid restaking tokens (LRTs): Instead of managing AVS opt-ins yourself, deposit your stETH with a liquid restaking protocol (Ether.fi, Renzo, Kelp, others) and receive an LRT (eETH, ezETH, rsETH). The LRT manager picks which AVSs to opt into. You earn yields from all layers. Your slashing risk now includes whatever the LRT manager has opted you into. Each layer adds yield. But each layer also adds a counterparty and a category of risk that didn't exist at the layer below.
AVS stands for Actively Validated Service. In practice, an AVS is any application that needs cryptoeconomic security and chooses to rent it from a restaking platform rather than building its own validator set from scratch. The categories of AVS in 2026 include: data availability layers (EigenDA), oracle networks, bridge attestation services, MEV-related services, fast-finality layers, and various rollup services. Each AVS defines its own slashing conditions. Some are narrow (only certain documented misbehaviors are slashable). Some are broader. Some AVSs have undergone audits; some haven't. Some have been live for months; some have launched recently. The risk profile varies wildly across AVSs. When you restake into an AVS, you're trusting that AVS's slashing conditions are well-designed, that its software is bug-free, and that the operator who runs your stake's participation in the AVS won't get slashed by mistake. A bug in the AVS, a misconfiguration by the operator, or a malicious AVS owner can each cost you part of your underlying ETH.
The restaking pitch is layered yield. The restaking risk is layered slashing. If you've restaked 1 ETH and opted into 10 AVSs, your 1 ETH is exposed to slashing under the rules of all 11 systems (Ethereum + 10 AVSs). The slashing parameters vary, but a worst-case combined slashing scenario can erase a meaningful chunk of the underlying stake. Liquid restaking tokens are the most exposed to this, because the LRT manager often opts the pooled stake into many AVSs to maximize yield. A holder of ezETH or eETH or similar is taking on the cumulative slashing exposure of every AVS the protocol opted into, which the holder typically can't easily inspect. The yields can still be net positive after this risk. They can also be net negative if a major AVS slashing event happens. The history is short, so the empirical distribution of outcomes isn't yet clear.
The operational risk of restaking, beyond slashing, is the same operational risk that affects every DeFi position: phishing transactions, malicious approvals, address-substitution attacks, and hacks. When you opt into an AVS, you sign a transaction that delegates your stake to that AVS. If a phishing site presents a transaction that looks like a normal AVS opt-in but actually delegates to a malicious AVS that immediately slashes the stake, you've lost the underlying ETH. The transaction was valid. You signed it. This is the attack surface a hardware wallet defends against. The device shows you the transaction details on its own screen before signing. The contract address, the function being called, the parameters being passed: all visible on the hardware wallet's screen, where laptop malware can't modify them. You see what you're signing and reject the transaction if anything looks off. Ryder One does this by default. The 1.6-inch AMOLED touchscreen shows every transaction in full readable detail before signing. The physical button is wired directly to the EAL6+ secure element, so no software path can sign without your physical confirmation. The firmware is independently audited by Halborn.
A reasonable framework for any restaker: Yield expectation: What's the base ETH staking yield, plus the LRT or restaking premium? Is the premium meaningful (more than 1 to 2 percent) or marginal? Marginal premium for substantial additional risk usually isn't worth it. Counterparty inventory: How many parties are in the path between your ETH and the network you think you're securing? If your ETH is staked via Lido, restaked via EigenLayer, into 10 AVSs, with the position represented as an LRT held in a smart wallet on a laptop, you've added five distinct counterparties beyond Ethereum itself. Each one has a failure mode. Operational discipline: Will you actually monitor the LRT's AVS opt-ins, the AVS slashing histories, and the relevant audit reports? If not, you're trusting the LRT manager to do that work, which is a counterparty risk in itself. For holders who want ETH staking yield without these layers, plain staking (or non-restaked LSTs) keeps the risk profile cleaner. For holders who want the maximum yield and are willing to monitor the position actively, restaking is a real opportunity. The middle ground (restaking passively without monitoring) is the worst combination: full risk exposure with no active risk management.
Stake what you meant to stake. While Ryder One cannot help with restaking, we are launching our staking feature soon. In addition, Ryder One verifies every transaction on its own screen, so the delegation you sign is the delegation you reviewed. See how it works.
The only crypto wallet you can install on a crowded subway.
Set it up in less than 60 seconds and just tap your phone to send, swap, and recover.
Share: