Educational disclaimer: This article explains how US federal tax law applies to dispositions of staking-reward ETH under current IRS guidance. It is not legal or tax advice. Tax rules are subject to change, several positions described here are subject to ongoing legal and legislative uncertainty, and individual circumstances vary. Consult a qualified tax professional before filing. All statutory references are to the Internal Revenue Code as in effect for tax year 2025 unless otherwise noted.

Your staking rewards produced ordinary income when you received them — that much is settled under IRS Rev. Rul. 2023-14 and Notice 2014-21. But when you eventually sell that ETH, a second tax question arises: how much capital gain or loss do you recognize, and is it short-term or long-term?

The answers turn on three things: your cost basis in each lot of reward ETH, the amount realized from the sale, and how long you held the ETH from the recognition date to the sale date. This article walks through each piece in plain English, cites the governing law, and explains why per-receipt lot tracking — not a wallet-level average — is both the correct approach and the one that holds up under IRS scrutiny.

The two-event structure of staking-reward ETH

Staking-reward ETH is unusual because it generates two separate tax events across its life cycle:

1. Receipt — You earn the ETH. Under Rev. Rul. 2023-14, you recognize ordinary income equal to the fair market value (FMV) of the ETH at the moment of dominion and control. This income appears on Schedule 1, Line 8z (or Schedule C if you're operating as a trade or business — a separate question outside this article's scope).

2. Disposition — You sell, exchange, or otherwise dispose of the ETH. At that point, under IRC §1001, you recognize capital gain or loss equal to the amount realized minus your adjusted basis.

The two events are connected: the income you recognized at receipt becomes the cost basis you use to compute gain or loss at disposition. That connection is the heart of this article.

How FMV-at-receipt becomes cost basis

Under IRS Notice 2014-21, virtual currency received as income has a cost basis equal to its fair market value on the date it was received. Q&A-4 of Notice 2014-21 states that the fair market value of virtual currency received in exchange for services (or, by extension, as staking income) is includible in gross income and establishes the taxpayer's basis in that currency. IRC §1012(a) provides the general rule: basis is cost. For income-recognition events, "cost" equals the amount you included in gross income — which is FMV at receipt.

Rev. Rul. 2019-24, which addressed airdrop and hard-fork income, applies the same principle: ordinary income recognized at FMV on receipt establishes a matching cost basis. That parallel framework applies to staking rewards by analogy.

The practical effect: if you received 0.05 ETH as a staking reward on a day when ETH was worth $3,400, you recognized $170 of ordinary income. Your basis in that 0.05 ETH lot is $170 — exactly $3,400/ETH. When you later sell that lot, you compare your sale proceeds to $170 to determine gain or loss.

This is not double taxation. You paid income tax on the $170 at receipt. The basis credit ensures you don't pay income tax on the same $170 again when you sell. You pay capital-gains tax only on the additional appreciation (or take a loss if the ETH declined in value after you received it).

IRC §1001: the gain and loss calculation

IRC §1001(a) defines gain from the sale or other disposition of property as the excess of the amount realized over the adjusted basis. Loss is the excess of adjusted basis over the amount realized.

For reward ETH:

• Amount realized = the sale price in USD (or the USD fair market value of whatever you receive in exchange, if you're trading ETH for another asset)
• Adjusted basis = the FMV of the ETH at the time of income recognition (per Notice 2014-21 Q&A-4 and §1012)
• Gain or loss = amount realized minus adjusted basis

IRC §1011(a) confirms that adjusted basis is determined under §1012 and §1016. For reward ETH held as an investment by an individual, §1016 adjustments (depreciation recapture, etc.) are not relevant — ETH is not a depreciable asset.

Example:

You received 0.05 ETH as a staking reward when ETH was $3,400. Basis = $170.

• Scenario A: You sell when ETH is $4,000. Amount realized = $200. Gain = $200 − $170 = $30.
• Scenario B: You sell when ETH is $2,800. Amount realized = $140. Loss = $170 − $140 = $30 loss.

Both amounts are capital gain or loss, reported on Form 8949 and summarized on Schedule D.

Holding period: short-term vs. long-term

Under IRC §1222, the character of your capital gain or loss depends on how long you held the asset from the date of acquisition:

• Short-term: held one year or less from the recognition date — taxed at ordinary income rates (same as your wage income bracket)
• Long-term: held more than one year from the recognition date — taxed at preferential rates (0%, 15%, or 20% depending on income, plus 3.8% NIIT for higher earners)

The recognition date — the date your staking reward was included in income — is the start of the holding period. For 0x01 validators under the withdrawal-time policy, that is the date the sweep transaction credited your execution-layer withdrawal address. For validators with earlier recognition (per-epoch or per-event policies), it is the applicable event date recorded in your system.

The difference between short-term and long-term can be substantial. At a 37% marginal rate, a $10,000 short-term gain costs $3,700 in federal income tax. The same gain held more than one year costs at most $2,380 (20% + 3.8% NIIT) — a saving of over $1,300 on a single lot. For validators holding significant reward ETH, the lot-level holding-period detail is not a formality.

Why each reward receipt is its own tax lot

Here is where lot accounting becomes operational rather than theoretical.

Every staking reward you receive is a separate tax lot — a distinct unit of ETH with its own:

• Basis: the FMV of ETH at that specific recognition event
• Holding-period start date: the specific recognition date for that event
• Character at sale: short-term or long-term depending on how long that lot was held

A single validator running for a year generates hundreds or thousands of individual lots: per-epoch attestation rewards accumulating inside the beacon chain, sweep transactions arriving every few days or weeks post-Capella, MEV tips credited at block-proposal time, and sync-committee rewards for the occasional lucky assignment.

Why this matters for capital gains:

Suppose you received ETH rewards throughout 2024 and sell some ETH in late 2025. Some lots have a basis of $2,000 (received when ETH was lower), others have a basis of $4,500 (received when ETH was higher). Some lots have crossed the one-year mark into long-term territory; others haven't. Which lot you sell determines your gain and its character.

A wallet-level average smears all of these together, producing an approximation that likely understates some gains and overstates others. Worse, an averaged basis doesn't map to any recognized tax-accounting method — the IRS requires either FIFO (first-in, first-out), or specific identification with contemporaneous documentation, for digital-asset dispositions.

FIFO, specific identification, and the 2025 rule

For tax year 2025 dispositions, the IRS requires per-wallet FIFO as the default lot-relief method for digital assets. Under FIFO, when you sell ETH, the oldest lots in that wallet are treated as sold first.

Specific identification — selecting which lots to sell (for example, preferring lots with a higher basis to minimize gain, or lots held more than a year to get long-term treatment) — is available, but requires contemporaneous documentation. That means you must identify the specific lot at the time of the sale, before the disposition, with records sufficient to establish which lot you selected. Assembling this documentation retroactively is not sufficient.

Per the research library's open questions (sourced from docs/research/tax/us/us-07-cost-basis-irc-1001.md): the specific documentation format the IRS treats as sufficient for a specific-identification audit defense — a signed attestation, a third-party report, a blockchain transaction hash paired with a dated export — is not yet definitively settled by Treasury regulations or revenue procedures. Counsel review is recommended when a Phase 1+ disposition engine ships and specific-identification elections are made.

Starting with acquisitions on or after January 1, 2026, those ETH lots will be "covered" property for Form 1099-DA basis-reporting purposes. Brokers subject to the 1099-DA rules must report your basis in covered-lot dispositions. For solo validators self-managing their own keys, the 1099-DA broker rules do not apply to your validator operations — you are responsible for your own basis records.

How lot accounting works in practice

For a reconciled staking-tax system, the per-lot structure looks like this:

Each reward receipt in the system produces a record with:

• Amount (ETH): the precise wei amount of the reward, converted to ETH
• FMV at recognition: the USD/ETH price at the recognition timestamp
• Basis (USD): amount × FMV = the cost basis of this lot
• Recognition date: the date that starts the holding period
• Source event: attestation reward, MEV tip, sync-committee reward, sweep withdrawal — each categorized separately

When you eventually sell ETH, the disposition engine matches the sold ETH against these lots (FIFO by default; specific identification if elected with contemporaneous documentation), computes gain or loss per lot, and classifies each as short-term or long-term based on the holding period.

Form 8949 requires one row per lot disposed. For digital-asset dispositions without a Form 1099-DA — the situation for most solo validators for 2025 transactions — you report in Box B (short-term, no 1099-DA) or Box L (long-term, no 1099-DA) per the 2024+ Form 8949 instructions. This is a mechanical IRS-instructions question, resolved per the research file's closed open question #11.

Why per-receipt lots beat a wallet-level average

Wallet-level averaging is not an IRS-recognized method for digital assets. But even if it were, it produces worse outcomes than careful lot accounting in most realistic scenarios:

The average overstates gain when markets rise. If ETH rose significantly after you received most of your rewards, your high-basis lots from recent receipt dates would be averaged down by older low-basis lots — resulting in a higher reported gain than you'd have under specific identification of the high-basis lots.

The average doesn't track the holding period correctly. An average tells you nothing about which ETH is short-term vs. long-term. The same ETH-per-average-cost calculation could classify as short-term lots that, individually, crossed the one-year mark months ago — costing you the preferential long-term rate.

The average doesn't survive an audit. If the IRS asks how you arrived at a basis number for a specific sale, "weighted average of all ETH I've ever received" is not a traceable answer. "This lot was received on epoch 305,000, at FMV $3,412.50, per the Lighthouse rewards API response stored in our reconciliation system" is.

The validator-pubkey-level data that makes a reconciliation gate possible — per-epoch receipts, stored with raw payloads and FMV at each event — is exactly the data you need for per-lot basis tracking. The two aren't separate concerns; they're the same data layer used for two different computations.

The architectural connection: stored facts, computed tax

The reason TrueStake stores receipts as immutable facts rather than computed tax records is precisely this: if the recognition policy changes — pending legislation like S.2207 could shift recognition to the time of sale, changing basis from FMV-at-receipt to $0 — the stored receipt data doesn't change. Only the adapter's interpretation of it changes.

The same principle applies to basis. Every receipt record carries the fields a disposition engine needs: the ETH amount, the FMV at recognition, the price source timestamp, and the recognition date. A Phase 1+ disposition engine will consume those fields directly. No re-ingestion, no approximation, no retroactive assembly of records.

This is what makes the income-recognition records not just a tax filing artifact, but the foundation for every future capital-gains computation. The receipt data you build now, reconciled to wei, is the basis data you'll use when you sell.

The pending legislation caveat

Two pending proposals would substantially change this analysis:

• S.2207 (Sen. Lummis) would defer recognition to the time of disposition, shifting basis from FMV-at-receipt to $0. Under that regime, the full sale price would be ordinary income at disposition, not capital gain.
• The PARITY Act discussion draft would provide an elective deferral option.

Neither had advanced to committee markup as of the publication of this article. Rev. Rul. 2023-14 and Notice 2014-21 remain the controlling authorities under current law. Tracking these proposals is part of routine quarterly review of the research library; we will update this article if either advances materially.

What to do now

Track by receipt, not by wallet. Each staking reward is its own lot. Record the amount, date, FMV, and source event for every receipt.

Reconcile to on-chain facts. Basis is only as reliable as the income-recognition records underlying it. A reconciliation gate — confirming that derived rewards match on-chain receipts within tolerance — is the foundation that makes basis defensible.

Know your holding periods. For lots approaching the one-year mark, the difference between short-term and long-term rates can be worth thousands of dollars. Calendar the anniversary dates of your larger lots.

Document lot elections contemporaneously. If you intend to use specific identification rather than FIFO, document which lots you're selling at the time of the sale. Retroactive documentation is not sufficient.

Consult a tax professional for your specific disposition strategy. The lot-accounting framework described here reflects current IRS guidance. The specific-identification documentation standard and the impact of 2025 FIFO rules on your holdings are fact-specific questions worth a professional review before you execute significant sales.

Sources and further reading: IRS Notice 2014-21 (Mar. 2014), Rev. Rul. 2023-14 (Aug. 2023), Rev. Rul. 2019-24 (Oct. 2019), IRC §§1001, 1011, 1012, 1016, 1222, IRS Form 8949 instructions (2025). For FMV methodology at the recognition event, see our companion article on FMV determination. For how recognition timing affects which date starts your holding period, see our article on Rev. Rul. 2023-14 and the dominion-and-control standard. Research library source: docs/research/tax/us/us-07-cost-basis-irc-1001.md (status: settled, last reviewed 2026-05-15, next review 2026-08-01). This article is for educational purposes only and is not legal or tax advice.