Restaking Protocol Development
Restaking — reusing staked ETH to secure additional protocols beyond Ethereum. EigenLayer invented this concept and collected $15B+ TVL. Idea: Ethereum's economic security (32M+ ETH in staking) can be "rented" by other applications — oracle networks, DA layers, cross-chain bridges — without needing to build their own validator set.
Conceptual Architecture of EigenLayer
AVS (Actively Validated Service): a service that uses restaking for its security. Examples: EigenDA (data availability), Espresso Systems (shared sequencer), Lagrange (ZK coprocessor).
Operator: an operator who manages validators and registers in one or more AVS. Takes on additional slashing conditions of AVS.
Staker → Restaker: regular ETH staker or liquid staking token holder deposits in EigenLayer. Delegates their stake to operators.
Slashing conditions: each AVS defines slashing conditions for its operators. Double signing in AVS protocol = loss of part of restaked ETH. This is the "price" for participating in AVS security.
ETH Staker
↓ restakes via EigenLayer
Restaking Contract (EigenPod)
↓ delegates to
Operator
├── validates Ethereum (required)
├── validates AVS_1 (optional)
├── validates AVS_2 (optional)
└── validates AVS_N (optional)
Technical Components of Restaking Protocol
EigenPod
EigenPod — smart contract that "sees" that a user has ETH staked on the Beacon Chain. Verification happens via EIP-4788 (Beacon Chain root available on-chain) + Merkle proofs.
// Simplified: verification of validator credentials
function verifyWithdrawalCredentials(
uint64[] calldata oracleTimestamps,
BeaconChainProofs.StateRootProof calldata stateRootProof,
uint40[] calldata validatorIndices,
bytes[] calldata validatorFieldsProofs,
bytes32[][] calldata validatorFields
) external {
// Check via Beacon Chain state root
// Accrue restaking shares
}
Delegation Manager
Manages delegation from stakers to operators. Staker selects operator, delegates their shares. Operator now responds for this stake when interacting with AVS.
Withdrawal delay: when canceling delegation — withdrawal delay (currently 7 days in EigenLayer). AVS protection from sudden stake outflow.
AVS Registration and Slasher
Each AVS deploys its own slasher contract, registers slashing conditions in EigenLayer Registry. Operator when registering in AVS gives opt-in to these conditions.
Upon discovering a violation — AVS slashing mechanism calls slash() in EigenLayer, which reduces the shares of the violating operator.
Liquid Restaking Tokens (LRT)
If regular restaking via EigenLayer is illiquid (funds are frozen), liquid restaking tokens (EtherFi's eETH, Renzo's ezETH, Puffer's pufETH) provide liquidity on top of restaking.
User: deposits ETH → receives LRT → uses in DeFi. Protocol: deposits ETH in EigenLayer → delegates to operators → receives AVS rewards → distributes to LRT holders.
Automatic restaking distribution: protocol strategically distributes ETH between AVS for optimal yield at acceptable risk. Implemented via Strategy Manager.
LRT Architecture
User deposits ETH
↓ EtherFi/Renzo/Puffer contract
↓ deposits in EigenLayer
↓ delegates to operators (multiple)
↓ operators register in AVS_1, AVS_2, ...
↓ AVS rewards arrive
↓ yield distributed to stakers
User receives LRT (eETH/ezETH/pufETH)
→ liquid, used in DeFi
→ exchange rate grows from rewards
Restaking Risks and Management
Slashing correlated risk: if operator registers in 5 AVS and receives slashing in one — loses part of stake that secured all 5. Cascading slashing risk.
AVS quality risk: not all AVS are equally safe. Low-quality AVS with bug in slasher can accidentally slash validators without real violation. Operators and LRT protocols must carefully choose AVS.
Concentration risk: if majority of restake concentrated with few operators — attack on them undermines many AVS simultaneously.
Leverage risk: restaking — is in some sense leverage on ETH stake. The "same" 32 ETH secures Ethereum + N other protocols. If total slashing liability exceeds stake value — system loses coherence.
Programming Your Own AVS
If you're building an AVS on top of EigenLayer:
Middleware contracts: contracts on Ethereum for registering operators and managing conditions.
Off-chain node software: program that operators run. Executes actual validation work of AVS.
Task Manager: contract that assigns tasks to operators and aggregates their responses. Quorum-based: task is considered complete upon signing by N-of-M operators.
Slashing conditions: clearly defined and limited conditions. Must be objectively verifiable — can't slash for subjective reasons.
Developing your own restaking protocol or AVS — highly complex task requiring deep understanding of Ethereum consensus, smart contract security and EigenLayer internals. Timeline — 6-12 months.