Eigenlayer and restaking ops for serious airdrop farmers

Restaking is one of those mechanics that sounds simple until you’re three layers deep in a liquid restaking wrapper, holding a receipt token that represents a claim on a claim on staked ETH, wondering exactly how many smart contract failures stand between you and your principal. I’ve been running EigenLayer positions since the early LST deposit windows in 2023, and the delta between what people think they’re doing and what they’re actually doing is wide enough to drive a liquidation through.

This post is for operators who already understand what a validator is, who have restaked at least once, and who want to think more carefully about the tradeoffs, the failure modes, and the actual mechanics of squeezing airdrop value out of restaking infrastructure. I’m not going to explain proof-of-stake from scratch. what I will do is walk through the real decisions, the real numbers where I have them, and the real ways this goes wrong.

The stakes are meaningful. EigenLayer’s EIGEN token Season 1 snapshot and distribution in 2024 rewarded early depositors substantially, and the protocol has continued to build out its AVS ecosystem since. If you’re thinking about restaking positions purely as a yield play, you’re probably leaving points and future airdrop surface area on the table. if you’re running positions without understanding the slashing architecture, you may be taking on tail risks you haven’t priced.

background and prior art

EigenLayer was conceived by Sreeram Kannan, a professor at the University of Washington, as a way to extend Ethereum’s cryptoeconomic security to new protocols without requiring them to bootstrap their own validator sets. The core insight is that ETH already has a massive base of staked capital with strong security guarantees, and new protocols (called Actively Validated Services, or AVSs) can rent that security by having restakers opt in to additional slashing conditions. The EigenLayer whitepaper is worth reading in full if you haven’t, because understanding the trust model matters for assessing risk.

The protocol opened mainnet LST restaking in mid-2023, initially with deposit caps that created a recurring meta: monitor the caps, queue a deposit transaction before the window fills, hope your gas estimate was right. Those caps have since been lifted for most assets, but the pattern established a community of active depositors who were paying close attention to the protocol mechanics, and those depositors were well-positioned for the Season 1 airdrop. The liquid restaking space grew up around EigenLayer, with protocols like Renzo, Kelp DAO, and Puffer Finance building wrapper products that gave users receipt tokens (ezETH, rsETH, pufETH) in exchange for depositing into EigenLayer on their behalf. each of these added their own points programs and their own token launches on top, creating a stacked airdrop surface that I’ll cover in the worked examples section.

the core mechanism

At the base layer, restaking means taking ETH that is already securing Ethereum consensus and making it available to also secure one or more AVSs. There are two paths: native restaking and LST restaking.

Native restaking requires you to run an Ethereum validator (32 ETH minimum) and set your withdrawal credentials to an EigenLayer EigenPod contract instead of a standard withdrawal address. this gives EigenLayer the ability to slash your stake if you misbehave on an AVS. the operational overhead is real: you’re running validator infrastructure, monitoring for slashing conditions on whatever AVSs you’ve opted into, and your ETH is illiquid in a way that LST positions are not.

LST restaking is what most retail-scale operators are doing. you deposit a liquid staking token (stETH, rETH, cbETH, ankrETH, or others depending on what’s currently whitelisted) into EigenLayer’s strategy contracts. the protocol records your deposit and begins accruing points. your ETH remains in the LST, which itself is exposed to validator slashing at the Lido/Rocket Pool/etc. layer, and now also to EigenLayer-level slashing if the operators managing those deposits misbehave on AVSs.

The points system that drove Season 1 farming was simple: 1 EigenLayer point per ETH restaked per hour. so 10 stETH restaked for 30 days accumulates 10 * 24 * 30 = 7,200 points. this is the number that determined your EIGEN allocation in Season 1, weighted against total points outstanding. the total supply of EIGEN was set at 1.67 billion tokens, with a significant portion allocated to stakers and community. specific allocation percentages are detailed in the EigenLayer blog’s Season 1 distribution announcement.

The AVS layer is where it gets more interesting for operators who want to maximize the security premium they’re capturing. each AVS that goes live on EigenLayer can offer additional rewards to operators and stakers who opt in to securing it. EigenDA, the first major AVS (a data availability service for rollups), has been the primary AVS by TVL for most of the protocol’s history. Operators run the validation software, stakers delegate to operators, and rewards flow from AVS protocol fees back through that chain. the EigenLayer docs on AVS architecture lay out the delegation and reward model clearly.

For airdrop farming purposes, the decision tree looks like this:

ETH available
├── >32 ETH, can run infrastructure
│   └── Native restaking via EigenPod
│       ├── Opt into AVSs directly
│       └── Maximize points, AVS rewards
└── <32 ETH, or no validator ops
    ├── Direct LST deposit to EigenLayer
    │   └── Earns EigenLayer points only
    └── Liquid restaking protocol (Renzo, Kelp, Puffer)
        └── Earns EigenLayer points + LRT protocol points
            └── Stack: ETH staking yield + EL points + LRT points + AVS rewards

The liquid restaking route is what most airdrop farmers have been running because it maximizes the number of simultaneous point streams. when Renzo launched REZ and Kelp launched KELP/KEP tokens, holders of ezETH and rsETH respectively received allocations. the stacking worked: you got ETH staking yield, EigenLayer points toward EIGEN, and LRT protocol points toward the LRT’s own token, all from one deposit.

worked examples

Example 1: direct LST restaking, Season 1 baseline

In early 2023, a position of 10 stETH restaked directly on EigenLayer from day one of the LST deposit window through the Season 1 snapshot would have accumulated approximately 7,000-8,000 EigenLayer points depending on exact timing. based on community data aggregated from on-chain records, the marginal value per point in the Season 1 distribution landed somewhere in the low cents range. this is not a number I’ll nail down precisely because allocations varied by tier and the token has traded across a wide range since launch. the directional point is that early depositors with meaningful ETH amounts received allocations worth several thousand to tens of thousands of dollars at launch prices. the opportunity cost was: ETH locked in EigenLayer strategy contracts for 6-12 months, plus standard stETH staking yield still accruing.

Example 2: liquid restaking stacking via Renzo

Renzo launched in late 2023 and offered a points multiplier relative to direct EigenLayer deposits, as a user acquisition mechanism. depositing 10 stETH into Renzo gave you 10 ezETH, which was accruing EigenLayer points (passed through by Renzo) plus Renzo-specific ezPoints. when REZ launched in April 2024, ezPoints holders received REZ allocations. the same 10 ETH position that would have earned one stream of EigenLayer points was now earning two. the gas cost to route through Renzo rather than depositing directly to EigenLayer was minimal. the incremental risk was Renzo’s smart contract layer. that tradeoff was, for most operators I know, clearly worth it.

the ezETH depeg event in April 2024 is directly relevant here. around the REZ TGE, ezETH briefly traded at a discount to ETH on secondary markets as liquidity fragmented. operators who had borrowed against ezETH or who needed to unwind positions in that window faced worse execution than expected. this is not a criticism of Renzo specifically, it is a structural property of all LRT receipt tokens during high-volatility events around their own token launches, and you should expect to see it again with any LRT that hasn’t yet launched its token.

Example 3: native restaking at scale

For operators running 5+ validators (160+ ETH), native restaking via EigenPods becomes the calculus. the advantages: full control over operator delegation, no LRT smart contract risk, ability to directly opt into AVSs and capture AVS rewards without sharing with an LRT protocol. the disadvantages: you’re running validator infrastructure 24/7, your withdrawal process involves the EigenPod contract which adds complexity to exits, and you need to actively monitor whatever AVSs you’ve opted into for slashing conditions.

a Singapore-based operator I know running 10 validators opted into EigenDA as their primary AVS. the operational overhead for EigenDA specifically is relatively low, the slashing conditions are well-defined, and the AVS had a track record by the time they opted in. their EIGEN allocation from Season 1 was proportionally larger than equivalent LST depositors because native restakers received a different point multiplier. the exact multipliers changed over time, so you need to check current docs rather than assuming any specific figure is still accurate.

edge cases and failure modes

1. withdrawal queue timing risk

EigenLayer enforces a withdrawal delay. as of the current protocol parameters, unstaking involves a waiting period measured in days. if you need liquidity urgently, you either sell your LST position (taking market price for stETH/rETH) or you wait out the queue. this matters because airdrop windows, TGE events, and market conditions do not wait for your withdrawal queue. i’ve seen operators get trapped: they wanted to rotate out of a restaking position to capture a different opportunity, the queue delay meant they missed the window. plan your position sizing with the assumption that this capital is effectively illiquid for the duration of the withdrawal period.

2. slashing contagion

each AVS you opt into adds an independent slashing vector. if an operator you’ve delegated to misbehaves on AVS A, you can be slashed on your restaked ETH even if you’ve never interacted with AVS A’s application layer. the risk is correlated with operator quality, not just your own behavior. before delegating to any operator, check their track record, their AVS selection, and whether they publish their slashing conditions clearly. the Ethereum staking documentation on slashing provides baseline context on how underlying validator slashing works, which compounds with EigenLayer-level slashing.

3. receipt token liquidity and depeg

LRT tokens (ezETH, rsETH, pufETH, weETH) have secondary market liquidity that is thin relative to their TVL. in normal conditions this doesn’t matter, the peg holds because arbitrageurs can redeem and remint. in stress conditions, particularly around the LRT’s own token launch or during broad market selloffs, the secondary price can gap below NAV. if you have DeFi positions built on top of your LRT holdings (lending, LP positions), a temporary depeg can trigger liquidations even though your underlying ETH is fine. i keep 0 borrowing against LRT collateral precisely because of this.

4. smart contract risk stacking

a direct stETH deposit on EigenLayer exposes you to: Lido’s smart contracts, EigenLayer’s strategy contracts, and the EigenLayer withdrawal infrastructure. routing through an LRT like Renzo or Kelp adds: the LRT’s deposit contracts, the LRT’s delegation logic, and any additional integrations they’ve built. each layer is audited, but audits are not guarantees. the EigenLayer security documentation describes their security model. read it. understand what assumptions you’re trusting.

5. points program rule changes

EigenLayer has changed points multipliers, whitelisted and delisted assets, and modified program terms over time. any future airdrop campaign may use different criteria. operators who optimized for Season 1 mechanics and held those positions unchanged through Season 2 windows may find that the optimal strategy shifted. treat points programs as dynamic, re-check allocation methodologies at least monthly, and don’t assume that what worked last season is optimal now.

what we learned in production

the most consistent edge I’ve seen from serious operators isn’t from finding alpha in obscure AVSs or running exotic LRT strategies. it’s from operational discipline around three things: timing deposits before deposit cap fills (when caps were active), monitoring the points multiplier changes and rotating between LRTs when multipliers shifted, and managing gas costs on deposit and withdrawal transactions by batching during low-fee periods.

on the multi-account question: EigenLayer’s points system was tied to wallet addresses and on-chain ETH positions, not to human identity. distributing positions across multiple wallets is a normal gas optimization and position management practice. it is not a KYC workaround and does not involve any identity fraud. operators running institutional-scale capital routinely manage multiple wallets for operational reasons. if you’re interested in the infrastructure tooling side of multi-wallet operations, multiaccountops.com/blog/ covers wallet management tooling in detail. separately, proxy infrastructure for monitoring on-chain data across multiple positions is covered at proxyscraping.org/blog/.

the thing that bit me once and will not again: exiting an LRT position at market rather than through the withdrawal queue in the week before a major TGE. the secondary market discount on the LRT was small but real, and the gas cost of the withdrawal queue route would have been lower. i took the market exit because i was impatient and it cost me. now i default to the withdrawal queue unless the position is small enough that the discount doesn’t matter or i genuinely need the liquidity that day.

for operators coming to EigenLayer from other airdrop strategies, the main mental model shift is that this is infrastructure-layer farming, not application-layer farming. you’re not using an app that might give you a retroactive airdrop. you’re providing cryptoeconomic security to an infrastructure protocol that has explicit token allocation programs. the runway for these programs is longer, the capital requirements are higher, and the upside is tied to Ethereum’s continued growth as a security provider, not to a single app’s user acquisition budget. that’s a different risk profile, and it suits some operators more than others.

for more context on layering ETH-based airdrop strategies, see our guide to LST and liquid staking airdrop farming and the overview of how to stack DeFi protocol points programs. the airdropfarming.org blog index has additional deep-dives on adjacent protocols in the restaking ecosystem.

references and further reading

1. EigenLayer Protocol Documentation - the canonical reference for restaking mechanics, withdrawal parameters, and AVS architecture. check the changelog when you revisit, parameters have shifted over time.

2. EigenLayer Official Blog - primary source for airdrop announcements, Season distributions, and AVS launch updates. this is where Season 1 and Season 2 allocation details were published.

3. Ethereum.org: Staking - foundational reference for understanding validator mechanics, slashing, and withdrawal infrastructure that underpins everything EigenLayer does.

4. EigenLayer Whitepaper - Sreeram Kannan’s original paper on pooled security and restaking. the trust model section is directly relevant to evaluating AVS slashing risk.

5. The Block: EigenLayer Coverage - The Block’s ongoing reporting on EigenLayer TVL, token launches, and ecosystem developments. useful for tracking protocol milestones and competitive dynamics in the restaking space.

Written by Xavier Fok

disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-05-19.