When you hear the term Restaking is a DeFi mechanism that lets validators lock up the same assets on multiple services at once, earning extra income while taking on more risk. If you’re a validator, delegator, or anyone holding staked crypto, you need to know exactly how the reward side‑flows work and why the penalty side can be far harsher than traditional staking.
Traditional proof‑of‑stake (PoS) staking locks your crypto to secure a single blockchain. Restaking expands that concept by letting the same locked stake “rent” security to other protocols, often called modules or AVSs. In practice, a validator on Ethereum can keep their ETH staked for block rewards while simultaneously allocating a portion of the same ETH to secure an oracle service, a liquidity‑layer, or a new roll‑up.
This “shared security model” is the engine behind the rapid TVL jump from $1billion to roughly $8billion in 2024, as more validators chase the added yield.
The reward flow splits into two buckets:
Because most extra payouts are point‑based, you can’t directly compare APYs across services without a conversion model. Experts usually estimate a “point‑to‑token multiplier” based on past TGEs, but that’s a moving target.
In classic PoS, slashing is the penalty for downtime, double‑signing, or other misbehavior, and it costs a portion of the validator’s stake.
Restaking adds a second slashing layer. Each AVS defines its own slashing triggers - for example, failing to meet a latency SLA for an oracle or providing false data to a bridge. If either the base chain or any supporting AVS flags a violation, the validator can lose a slice of the same locked assets.
That compounded risk means a validator could be penalized twice for a single fault, dramatically raising the capital at stake.
Not every holder runs a full validator node. Two main pathways exist:
Both models can be combined: a delegator may spread their stake across multiple operators, each supporting different AVSs, to diversify risk.
Protocol | TVL (USD) | Reward Model | Slashing Scope | Delegation Support |
---|---|---|---|---|
EigenLayer | $4.2B | Points converted via scheduled TGEs; APY 5‑12% | Base‑chain slashing + module‑specific slashing (up to 20% of stake) | Yes - native operator registry |
Symbiotic | $1.6B | Vault‑based token rewards; APY 4‑15% | Base‑chain slashing only; optional AVS slashing via vault rules | Limited - only vetted custodial vaults |
Lido Restake | $1.2B | Liquid staked token (stETH) earns native LDO rewards; APY 3‑9% | Base‑chain slashing only; no extra AVS penalties | Yes - fully custodial, fee 10% |
When picking a platform, look at the slashing scope first. More aggressive AVS penalties can boost yields but also raise the chance of double‑dip losses.
Because the reward upside is tied to extra risk, a solid assessment framework is essential. Here are the steps most seasoned validators follow:
Many validators also set a personal “max‑risk” cap - for example, never allocating more than 15% of total stake to any single high‑reward AVS.
Restaking has become the go‑to strategy for validators looking to out‑perform the ~5‑7% baseline ETH staking yield. The market now features three clear segments:
Regulators in the EU and US are beginning to examine whether restaking counts as “securitization” of assets, which could affect future compliance requirements.
Industry roadmaps point to two game‑changing developments:
Until those tools become mainstream, the best defense remains diligent research, diversification, and a clear understanding of the dual‑reward, dual‑penalty nature of restaking.
Restaking lets you earn a second stream of income from the same locked assets, turning a single‑network reward into layered yields across multiple services.
No, losses are capped at the amount you originally locked. However, multiple slashing events can erode the stake quickly, so the effective risk is higher than standard staking.
Yes. Even if you delegate, the underlying stake is still subject to any slash that hits the validator you chose. Operator fees do not protect the principal.
Most protocols schedule a Token Generation Event where accumulated points are swapped for the native token at a predefined ratio. The exact timing and ratio are announced weeks in advance.
A few emerging projects are testing decentralized insurance pools that reimburse a portion of slash losses, but coverage is optional and still experimental.
Write a comment
Your email address will not be published