Staking & Restaking: Risks and Rewards
DeFi
• ~11 min read
• Updated: 08/08/2025
- Validator: Node that proposes/attests blocks in PoS.
- Delegator: You stake to a validator and share rewards.
- LST (Liquid Staking Token): A tokenized claim on staked assets (e.g., stETH, rETH).
- Slashing: Protocol-level penalty for faults (e.g., double-signing).
- Exit/unbonding: Delay before staked funds are liquid again.
- Restaking: Pledging the same stake (or LST) to secure additional services (AVSs) with their own rules and slashing.
1) How Proof-of-Stake rewards work
In PoS, validators lock coins as collateral and participate in block production and/or attestation. The protocol pays for liveness (showing up on time) and correctness (not equivocating). Rewards are a function of: your effective stake, global total stake (more total stake usually means lower per-validator yield), your node’s uptime, and on some chains, MEV and fee capture. Penalties reduce rewards for downtime; severe faults can burn a slice of your stake.
High level (Ethereum example): - You (solo or via a provider) commit ETH to a validator index. - Epochs/slots schedule proposals & attestations. Perform well → earn. - Miss attesting or go offline → small leak over time. - Double-sign/attest surround → slash (stake is partially burned). - Partial withdrawals (excess rewards) happen automatically; full exits join a queue to protect the network’s churn.
2) Ways to stake (solo, pooled, liquid)
- Solo staking: You run the validator and custody keys. Best sovereignty, requires hardware, client diversity, monitoring, and ops discipline. You capture the full validator margin (minus infra costs).
- Delegated / provider staking: You delegate to an operator. You retain asset ownership but share rewards; subject to operator commission and their operational risk.
- Liquid staking (LSTs): You deposit to a protocol and receive a token (e.g., stETH, rETH) representing your claim on the staked asset. You keep yield and can use the LST in DeFi. Smart-contract/governance risk and potential depeg apply.
| Route | Sovereignty | Ops complexity | Liquidity | Main risks |
|---|---|---|---|---|
| Solo | Highest | High | Low until exit | Slashing from misconfig; uptime |
| Delegated | Medium | Low–Medium | Low until unbond | Operator risk; fee drag |
| Liquid (LST) | Varies | Low | High (LST tradable) | Smart-contract + depeg + oracle risk |
3) APY vs APR, compounding & fees
APR is the simple annual rate. APY includes compounding. Many LSTs automatically compound (rebasing balance up, or increasing exchange rate). To sanity-check numbers:
APY ≈ (1 + APR / n)^n − 1 Example: APR 4%, compounded monthly → APY ≈ (1 + 0.04/12)¹² − 1 ≈ 4.07%
- Fee layers: Protocol fee + operator commission + any SP (service provider) fee (for restaking). These stack.
- Rebase vs rate-accrual: Rebase LSTs increase balance; rate-accrual LSTs keep balance constant while price drifts up. This affects tax/accounting and DeFi integrations.
- MEV & tips: On some chains, validator MEV capture flows into rewards. Policies differ (e.g., smoothing pools vs keepers taking a cut).
4) Core risks to understand
- Slashing & penalties:
- Liveness (being offline) → gradual leaks.
- Safety faults (double-sign, surround) → slash a chunk at once.
- Correlation risk: Running the same client stack across many validators can turn a bug into a mass slash.
- Lockups & exit queues: Unbonding can take days, weeks. Exit queues throttle how fast validators can leave so the chain stays safe. In stress events, expect delays.
- Smart-contract/governance risk (LSTs): Bugs in staking modules, or governance capture that changes redemption rules.
- Liquidity & depeg: LST price can drift below underlying in panics or when exit capacity is scarce. If you use LSTs as collateral, even a small depeg can trigger liquidations.
- Counterparty/operational risk: Custodial or semi-custodial providers, key management practices, and data center concentration all matter.
- Regulatory/jurisdiction risk: Tax treatment and securities analysis differ by country and can change.
5) What is Restaking? Benefits & extra risks
Restaking lets you pledge your staked asset (or its LST) to secure additional services, often called AVSs (Actively Validated Services) such as data availability layers, oracles, keeper networks, or rollup infrastructure. In return, you earn extra rewards (fees, emissions). Think of it as lending your trust to more than one system at once.
- Why it’s attractive: Capital efficiency (one stake, multiple incomes), faster bootstrapping for new networks, potential diversification of reward sources.
- New risk channel: Each AVS defines its own slashing conditions and dispute processes. Misbehavior or bugs in any AVS can slash the same underlying stake or LST.
- Stack complexity: More contracts, oracles, bridges, and governance tokens in the loop → more attack surface.
- Correlated failures: If a popular operator runs the same setup across many AVSs, an ops error or client bug could trigger multi-AVS slashing.
- Slashing spec: What actions are slashable? Who arbitrates? Is there appeal?
- Operator set: Who runs it? Client diversity? Geo spread? Key management?
- Rewards math: Emissions vs fees; vesting/lockups; who bears oracle/bridging costs?
- Unwind path: How do you exit the AVS or restaking layer during stress? Queues? Cooldowns?
6) How to choose a validator / protocol
- Track record: Documented uptime, incident post-mortems, transparency.
- Client diversity: Not just one client stack; reduces correlated slashing.
- Key management: HSMs, remote signers, monitored failover, tested disaster recovery.
- MEV policy: Smoothing pools vs keep; ethical relays; censorship stance.
- Fee transparency: Commission, protocol cut, restaking SP fees; how they change.
- Governance & docs: Clear parameters, emergency runbooks, active community channels.
- Concentration: Avoid piling into the biggest pool; decentralization matters for network health and your tail risk.
7) Taxes & accounting notes
Many jurisdictions treat staking rewards as taxable income at receipt (fair-market value at the time), with capital gains or losses when you later dispose. LST mechanics (rebasing vs exchange-rate drift) affect how and when income is recognized. Keep precise records:
- Reward timestamps, token amounts, and fiat values.
- Fees paid (gas, commissions) for basis tracking.
- Events like slashing, restaking rewards, and any vesting schedules.
Practical playbook (copy/paste)
- Decide route: Solo ↔ Delegate ↔ LST. Start with the simplest that meets your needs.
- Risk budget: Cap exposure per operator/pool; set a depeg/liquidation threshold alert.
- Ops hygiene: If solo, monitor nodes; if delegating, monitor operator health dashboards.
- For LSTs: Understand redemption/exit mechanics and historical peg behavior.
- For restaking: Add only one AVS at a time; read its slashing spec; test exit flow with a small allocation.
- Document: Fees, keys, runbooks, who to page in incidents. Practice an “exit under stress.”
8) Further learning & resources
- Ethereum.org Staking (solo, pooled, LST basics).
- Lido Docs & Rocket Pool Docs liquid staking mechanisms & risks.
- EigenLayer Docs restaking architecture & AVS risk model.
- Cyfrin Updraft advanced smart-contract/security training (great for understanding staking/MEV/validator risks).
- Paradigm Research MEV and validator economics.
Smart Contract Risks: Re-entrancy, Oracles, Upgrades →
