EigenLayer Restaking Accounting: AVS Rewards, LRTs & Tax Treatment

EigenLayer made restaking a real category. Two years in, the protocol secures over $15B of TVL across native restaking, liquid staking token (LST) restaking, and a growing layer of liquid restaking tokens (LRTs) like ezETH, pufETH, and weETH. The accounting and tax implications are genuinely new — restaking introduces a second simultaneous income stream on top of base ETH staking, with different vesting characteristics, custody flows, and slashing exposures. Most national tax authorities haven't issued specific guidance on restaking, which leaves filers and accountants stitching together precedent from earlier staking, lending, and liquidity-pool rulings.

This guide covers what EigenLayer restaking actually does, how to model the cash flows for accounting, the tax treatment in the major Web3-active jurisdictions (US, UK, AU, CA, EU), and how IFRS and US GAAP teams should think about LRT positions. It's written for crypto-native finance teams, DAO contributors with restaked treasuries, and individual filers with material restaking exposure.

The short version: every restaking action is potentially a discrete tax event, rewards are typically ordinary income at receipt, slashing is a capital loss when it crystallizes, and LRT positions need to be modeled as both an underlying-asset position and an ongoing yield stream. Without specialist software, the volume of events makes accurate accounting infeasible.

What EigenLayer is, in five sentences

EigenLayer is an Ethereum protocol that lets staked ETH (or LSTs that represent staked ETH, like stETH, rETH, cbETH) be restaked — pledged again as security for additional services called Actively Validated Services (AVSs). AVSs include data-availability layers (EigenDA), oracle networks, and sidechain bridges. In exchange for accepting AVS slashing risk, restakers earn protocol-specific rewards: AVS fees, EIGEN token incentives, and (separately) ongoing ETH staking rewards. Liquid restaking tokens (LRTs) abstract the restaker's position into a fungible token — ezETH, pufETH, weETH — that itself trades and earns rewards. The financial result is a stack: ETH yield + LST yield + AVS fees + EIGEN rewards, all running concurrently, with multi-step exposure to slashing.

The three restaking modes — and why they matter for accounting

EigenLayer supports three deposit shapes, each producing a different chart-of-accounts treatment.

1. Native restaking (full validator)

A holder runs (or pays an operator to run) an Ethereum validator and points the withdrawal credentials at an EigenPod. The 32 ETH stake earns standard consensus rewards, and the EigenPod position can be delegated to AVS operators for additional rewards.

Accounting characteristics:

• Underlying asset: 32 ETH (per validator) plus accrued ETH rewards.
• Income streams: Consensus rewards (ETH), AVS rewards (often non-ETH tokens), EIGEN incentives.
• Slashing exposure: Both the consensus layer (1+ ETH penalties for inactivity, larger for double-signs) and AVS-specific slashing conditions.

2. LST restaking

A holder deposits stETH, rETH, cbETH, or another supported LST directly into EigenLayer's strategy contracts. The LST continues to accrue base staking yield (rebased into stETH or wrapped into wstETH, depending on which LST). AVS rewards accrue on top.

Accounting characteristics:

• Underlying asset: The LST. Its rebasing or appreciation behavior continues independently.
• Income streams: LST-internal yield (already taxable at LST level) plus AVS rewards.
• Slashing exposure: AVS-specific only (the LST custodian handles consensus-layer risk).

3. LRT positions (the most common retail mode)

A holder deposits ETH, stETH, or another LST into an LRT protocol (Renzo for ezETH, Puffer for pufETH, EtherFi for weETH, Kelp for rsETH). The protocol manages the EigenLayer deposit and returns a single LRT to the user.

Accounting characteristics:

• Underlying asset: The LRT. Either rebases (gains balance over time) or appreciates against ETH.
• Income streams: Bundled into LRT yield. Many LRTs also distribute "points" that convert to AVS or EIGEN rewards retroactively.
• Slashing exposure: Pooled across the LRT protocol's strategies.

For most retail and many institutional users, LRTs are the only practical way to access restaking. They are also the most accounting-complex because the income stream is bundled and may include retroactive token distributions.

The income-recognition problem — when do rewards become "received"?

This is where most filing errors happen. The standard tests in major jurisdictions:

• US (IRS Notice 2014-21, Rev. Rul. 2023-14): Income is recognized when the taxpayer has dominion and control over the rewards.
• UK (HMRC CRYPTO21000+): Income at the date the rewards are received and have a market value.
• AU (ATO): Ordinary income when the reward is received and has a fair market value.
• CA (CRA): Income at fair market value when received, with the FMV becoming the cost base.

For native restaking, "received" typically means when consensus rewards are credited and AVS rewards are claimable to a withdrawal address. For LRTs, the question is harder — rebases can happen continuously, and "points" are not always tokens at the point of accrual.

A defensible position for LRTs:

• Rebased balance increases: Treat each rebase as taxable income at the rebase event. (Same approach as stETH.)
• Non-rebasing appreciation: No income event; the appreciation is realized as a capital gain on disposal.
• Points-based distributions: Recognize income when the points are converted to a transferable asset, not at the point of accrual — unless the points themselves are transferable (in which case at receipt).
• Retroactive AVS or EIGEN drops: Income at the date of the airdrop snapshot or the claim transaction, depending on whether the protocol guarantees the drop in advance.

This is an area where reasonable practitioners differ. The conservative position is to recognize at the earliest defensible date; the aggressive position is to defer until points are converted to transferable tokens. Document your method consistently.

Slashing — the underrated downside risk

EigenLayer added slashing conditions in mid-2025. AVSs can now penalize restakers for misbehavior. The amount and trigger vary by AVS, but the accounting question is the same: when is a slash recognized as a loss?

The defensible treatment:

• Recognition trigger: The slash transaction is finalized on chain (i.e. when the deposit balance is reduced).
• Loss type: Capital loss, computed against cost base of the slashed portion.
• Cost-base allocation: If the slash is partial, the slashed units are deemed to come out of the pool using the same cost-base method used for dispositions (FIFO in the US default, ACB-pooled in Canada, single-pool average in the UK and France).
• Income offset: The slash cannot offset the prior recognition of staking income. You took income at receipt; the slash is a separate capital event.

For LRT holders, slashing manifests as a reduction in the LRT's underlying-asset coverage rather than a transaction in the user's wallet. The pooled effect socializes slashing across all LRT holders. The accounting consequence is similar — a reduction in the implied value of the LRT — but the timing of recognition is murkier. A reasonable approach is to mark-to-market the LRT regularly and recognize the impairment as a capital loss when the LRT is finally disposed.

EIGEN token treatment

EIGEN distributed via the multi-season airdrop is the largest single source of confusion. The relevant questions:

• When is the airdrop "received"? When the holder has the present ability to claim, not when the snapshot was taken. Most jurisdictions accept this.
• What is the FMV at receipt? The first liquid market price after the holder gains the right to claim. Pre-token claim values are typically zero.
• Is the airdrop ordinary income or capital? Most jurisdictions: ordinary income at FMV. UK is the most contested, with HMRC's position depending on whether the recipient provided a service in exchange.
• What's the cost base going forward? The FMV at receipt becomes the cost base. Subsequent disposition triggers a capital gain/loss.

For DAOs and crypto-native businesses receiving EIGEN as restaking incentives, the same principles apply with corporate income-tax recognition rather than personal income-tax.

IFRS and US GAAP — the financial-reporting view

Both frameworks now have crypto-specific guidance, though neither addresses LRTs explicitly.

Under FASB ASU 2023-08 (US GAAP, effective fiscal years from 15 December 2024)

Crypto assets that meet the scope criteria — fungible, secured by cryptography, not tied to enforceable rights to underlying goods/services — are reported at fair value with changes flowing through net income. LRTs typically meet the scope criteria.

For restaking specifically:

• LRT position: Asset on the balance sheet at fair value.
• AVS rewards in non-LRT tokens: Recognize as income when received, at FMV. Hold subsequently as separate digital-asset positions.
• Slashing: Recognized through the fair-value adjustment of the LRT (mark-to-market reduction).
• Disclosure requirements: Separate balance-sheet line for crypto assets, with detailed disclosure of the major holdings, fair-value sources, and reconciliation of opening-to-closing balances.

Under IFRS (IAS 38 amendments + IFRS 9 considerations)

IFRS treatment depends on whether the entity holds the LRT for sale in the ordinary course of business (inventory under IAS 2), as an investment (intangible asset under IAS 38, with revaluation model available), or as part of a financial instrument arrangement (IFRS 9).

For most non-trading entities, IAS 38 with the revaluation model produces results that approximate the FASB approach: fair-value remeasurement with the gain/loss split between OCI (for upward revaluations not reversing prior P&L losses) and P&L (for downward revaluations or reversals).

The look-through approach — treating an LRT as a claim on underlying ETH or LSTs — is not authoritative under either framework. Some auditors accept it for disclosure purposes; the on-balance-sheet position is the LRT itself.

Practical reporting workflow

For a crypto-native finance team holding LRT positions:

1. Classify: LRT as digital asset under FASB ASU 2023-08 / IAS 38 revaluation model.
2. Initial measurement: Cost on acquisition date.
3. Subsequent measurement: Mark-to-market at every reporting date using a reliable price source (the LRT's primary venue, or a TWAP across major venues).
4. Income recognition: Rebase events as income at receipt; accumulated rewards (AVS, EIGEN) as separate income events.
5. Disclosure: Schedule of holdings, fair-value methodology, reconciliation, and material AVS exposure summary.

How Wag3s Ledger handles restaking workflows

Wag3s Ledger is built for the multi-stream, high-event-volume reality of restaking:

• Per-position tracking across native EigenPods, direct LST deposits, and LRTs.
• Automatic detection of rebase events, AVS reward distributions, and EIGEN airdrops.
• Income recognition at fair market value with configurable timing rules per jurisdiction.
• Cost-base maintenance with FIFO, LIFO, ACB-pooled, or specific identification.
• Slashing event detection and capital-loss recognition.
• Mark-to-market reporting for IFRS / FASB compliance.
• Multi-jurisdictional output supporting US Form 8949, UK SA108, Australian capital-gains schedule, Canadian Schedule 3, French Form 2086.

For DAO treasuries with restaked positions, see DAO Treasury Management for the multi-sig and governance-linked workflows.

Useful EigenLayer resources

• EigenLayer documentation — the protocol's official docs.
• EigenLayer slashing — the slashing condition framework.
• EIGEN tokenomics — supply schedule and airdrop seasons.
• Renzo / ezETH, Puffer / pufETH, EtherFi / weETH — the major LRT protocols.

Related guides

• Liquidity pool accounting — adjacent DeFi accounting territory.
• Staking rewards tax — base-layer staking treatment that LRTs inherit.
• Yield farming tracking — multi-protocol position management.
• IFRS vs GAAP for crypto assets — financial-reporting framework comparison.
• Bridges & wrapped tokens accounting — wrapping events that often appear in LRT mint flows.