Liquid Restaking Token Accounting: An LRT Is a Position, Not a Coin

In a wallet, a liquid restaking token looks like any other ERC-20 balance. Underneath, it is a claim on restaked ETH that is securing third-party services, earning more than one layer of yield, and carrying a real chance of being slashed. Book it as a plain coin held at cost and three things vanish from the books at once: the underlying ETH exposure, the layered rewards, and the downside. This article is narrower than general staking — it deals specifically with how an LRT from a protocol like ether.fi, Renzo, or Kelp behaves as an accounting object, and the position-tracking discipline that keeps it honest. It builds on the recognition rules in staking rewards accounting and the underlying-token logic in liquid staking token accounting; restaking simply stacks another layer of reward and risk on top.

The position in brief

• An LRT — ether.fi eETH/weETH, Renzo ezETH, Kelp rsETH — is a claim on a restaked ETH position securing EigenLayer services, not a standalone coin.
• It is a position, so the books need the underlying exposure, the layered reward stream, and the slashing-loss risk, not just the LRT balance.
• Slashing is a loss event. A rewards-only model is incomplete because it carries the upside and drops the downside.
• Restaking rewards are separate income events at control (the same recognition as in staking rewards accounting), and layered sources should be decomposed rather than netted.
• Exiting restaking involves a lock-up on top of Ethereum's unbonding, which is a liquidity and disclosure point: the tradable LRT price is not the same as the locked underlying.

What an LRT actually represents

Restaking on EigenLayer reuses staked ETH or LSTs to secure Actively Validated Services (AVSs) for additional rewards, with slashing if the securing operator misbehaves or fails its AVS obligations. An LRT — issued by protocols such as ether.fi (eETH/weETH), Renzo (ezETH), or Kelp (rsETH) — is a composable token that represents that restaked position. The LRT is the wrapper; the substance is the combination of underlying ETH exposure, layered rewards, slashing risk, and a lock-up on exit.

Why "plain holding" is wrong

Booking the LRT as a flat coin balance loses three things:

This is the same error as treating an LP token as a coin: the receipt token is not the economics. The LRT has to be tracked to the position it represents.

Slashing is a loss event

A rewards-only model is incomplete. Slashing can reduce the staked capital if the operator securing an AVS is penalised, and the accounting has to reflect that reduction in the recoverable underlying when it occurs or becomes probable — not ignore it because the LRT still trades. An LRT position carries both an upside (rewards) and a downside (slashing), and the downside is precisely the part naive models drop.

Rewards: decompose the layers

Restaking layers its reward sources: base staking yield, AVS rewards, and sometimes protocol incentives. Each is an income event, generally recognised at fair value when control is obtained, separate from the principal position (the recognition rule from staking rewards accounting). Netting them all into a single LRT value change loses the composition and the basis of each stream, so the right move is to decompose rather than net.

Lock-up and liquidity

Exiting EigenLayer restaking involves a lock-up on top of Ethereum's own unbonding period. So even when the LRT trades freely, the underlying position is not immediately liquid. That constraint, together with the slashing exposure and the layered reward structure, is relevant to both disclosure and measurement: the tradable LRT price on its own does not capture a locked, slashing-exposed underlying.

Journal entry structure: what an LRT position looks like in the books

To make the position-tracking discipline concrete, consider the following illustrative journal structure for an entity that deposits ETH into ether.fi and receives eETH:

On deposit (ETH → eETH):

• Debit: eETH (restaked position asset) at fair value of ETH deposited
• Credit: ETH (asset) at carrying amount
• Note: if fair value of eETH differs from ETH deposited at the point of exchange, recognise the difference as a gain or loss depending on framework

On receipt of AVS rewards (denominated in a reward token):

• Debit: Reward token (asset) at fair value at date of control
• Credit: Restaking reward income (P&L) at same value
• Note: this is an income event separate from the principal eETH position — do not net into the eETH balance

On slashing event (operator penalised, underlying reduced):

• Debit: Restaking loss (P&L) at the fair value of the reduction in recoverable underlying
• Credit: eETH position (asset) for the same amount
• Note: the loss is recognised when the slashing event occurs or when loss is probable, whichever is earlier under the applicable standard

On exit (eETH → ETH, after lock-up):

• Debit: ETH (asset) at redemption amount
• Credit: eETH (restaked position asset) at carrying amount
• Recognise any difference as gain or loss

This structure is illustrative and framework-specific. The point is that each leg — deposit, reward accrual, slashing, exit — has its own journal treatment, none of which is captured by simply holding an eETH balance in the books at cost.

Practical guidance

1. Model the LRT as a position linked to the underlying restaked ETH, not as a flat coin.
2. Decompose the layered rewards (base, AVS, and incentives) into separate income events at control.
3. Carry slashing as a loss when it occurs or becomes probable, rather than running a rewards-only model.
4. Reflect the exit lock-up in liquidity disclosure and measurement, since the LRT price is not the locked underlying.
5. Treat the characterisation as provisional: restaking accounting and tax are framework- and protocol-specific, and still evolving.
6. Reconcile the position back to the protocol (ether.fi, Renzo, Kelp) and the chain, keeping an audit trail.

Choosing and configuring a tool

An LRT stresses an accounting tool in ways a plain token never does, so the question is less which vendor than whether the platform can hold the position together. Cryptio and Bitwave both model restaking positions, decompose reward streams, and track the underlying behind an LRT. Before you trust the balance sheet, confirm the tool:

• treats the LRT as a position with an underlying rather than a flat holding, so the eETH or ezETH line is linked to the restaked ETH it represents;
• decomposes the layered rewards into separate income events at control instead of folding everything into a single LRT value change;
• can recognise a slashing loss against the recoverable underlying — a rewards-only model will overstate the position the moment an operator is penalised;
• captures the exit lock-up as a liquidity attribute, so the position is not implicitly treated as immediately realisable at the traded LRT price.

A tool that books the LRT as one coin at cost gives you a tidy balance that is missing the reward composition, the slashing downside, and the liquidity constraint all at once.

Where Wag3s fits

Wag3s Ledger models each LRT as a restaked position linked to its underlying, decomposes the layered reward streams into separate income events, carries slashing as a loss event, and reflects the exit lock-up in measurement and disclosure, reconciled to the protocol and the chain. Restaking characterisation is unsettled and protocol-specific, so Wag3s is built to produce the position data and audit trail that support the accountant's or auditor's classification judgement, not to make that call for them. See the Ledger product page and the Wag3s for accountants page.

Further reading

• EigenLayer Restaking Accounting
• Liquid Staking Token Accounting
• Staking Rewards Accounting
• DeFi Position Reconciliation
• Yield Farming Tracking
• IAS 38: Crypto as an Intangible Asset
• Crypto Bank Reconciliation: Subledger to General Ledger

Sources

• EigenLayer — Restaking overview: restaking reuses staked ETH and LSTs to secure Actively Validated Services, operators are subject to slashing for misbehaviour or failed AVS obligations, and exiting involves a lock-up in addition to Ethereum's unbonding. This is the mechanism the LRT-as-position model is built on.
• IFRS — IFRS 9 Financial Instruments: the classification reference for an LRT that represents a claim on an underlying financial position, where the business-model and cash-flow tests drive measurement.
• FASB — ASU 2023-08: the US GAAP fair-value-through-net-income model for in-scope crypto assets, relevant where an LRT layer falls within that scope rather than being treated as a financial asset.
• Position-tracking and reward-decomposition discipline (analogous to LP and DeFi position reconciliation), slashing treated as a loss event, and a characterisation that remains framework- and protocol-specific and is still evolving.