Do IFRS or US GAAP say when a native Ethereum staking reward is recognised?

No. No IFRS or US GAAP pronouncement addresses native staking, and the reward accrues every epoch. Candidate dates include accrual, the point the network confirms validation, the point the ETH becomes withdrawable, and receipt. Across the eight of nine SEC registrants that stake there are seven different published positions, six of them in audited annual financial statements and one in an unaudited quarterly report, so there is no market practice to fall back on.

Is a gas fee on a transfer between an entity's own wallets deductible?

Gas that is not an acquisition or disposal cost is unaddressed under both frameworks and, with one exception, by the three tax authorities in the reviewed set. The exception is the US position, and it sits in an IRS FAQ rather than in the regulations: a fee on a transfer between the taxpayer's own wallets is a disposition of the ETH used and is neither basis nor amount realised, a cost that goes nowhere. HMRC comes nearest on the rest, treating a fee satisfied in tokens as a disposal in its own right, but it has not applied that to an own-wallet transfer.

How should a validator penalty or a slashing loss be accounted for?

Nothing located says whether the quantity reduction from a missed attestation or an inactivity leak is an impairment, a derecognition of units or an expense of the period. The workable answer is a documented policy, expense it or net it against the reward income it sits beside, and the two give different revenue figures on identical facts. For slashing, no framework or tax authority in the reviewed set addresses how the loss is measured or where it goes.

Does any standard or tax authority name an ETH price source?

No, and this article treats that as a positive finding rather than a gap: the FASB expressly declined to add guidance because the existing guidance in Topic 820 is sufficient. Venue, minute, timezone and fallback are the entity's to choose, document and defend. Real filers use midnight UTC, hourly spot at receipt, 4:00 p.m. New York, and 11:59 p.m. Eastern.

Ethereum Accounting Guidance Gaps: What Standards Do Not Answer

Q: Is ETH a foreign currency?

No, and this one is settled. Under IFRS the reasoning chain runs from IAS 21's definition of a monetary item through the IFRS Interpretations Committee's conclusion that a cryptocurrency does not give the holder a right to receive a fixed or determinable number of units of currency and is not cash. Under US federal tax the answer is express: virtual currency is not treated as currency that could generate foreign currency gain or loss. A line labelled FX gain on ETH is wrong in both.

Ethereum accounting guidance gaps are real, but Ethereum accounting is not uncertain everywhere. Many protocol facts are settled, the basic IFRS classification analysis is established, ASC 350-60 creates a defined US GAAP fair-value model for in-scope holdings, and tax authorities have answered important pieces of the tax problem.

Ethereum accounting guidance gaps — summary

Ethereum accounting is not uncertain everywhere. The unresolved areas cluster around a smaller set of Ethereum-specific mechanics: native staking rewards, gas, validator quantity losses, movement between the execution and consensus layers, and the evidence needed to support those events. Everything else is either authority that answers the point, a reasonable interpretation of existing authority, or a policy the entity must select and document.

No IFRS or US GAAP pronouncement addresses native staking, and across the eight of nine SEC registrants that stake there are seven different published positions. Gas that is not an acquisition or disposal cost, the burned base fee, failed transactions, deposits to the deposit contract and validator quantity losses are all unaddressed in the reviewed sources.

The unresolved areas cluster instead around a smaller set of Ethereum-specific mechanics: native staking rewards, gas, validator quantity losses, movement between the execution and consensus layers, and the evidence needed to support those events.

This article uses four labels:

Established: authoritative material answers the point.
Reasonable interpretation: existing authority supports a conclusion, but does not state it in Ethereum-specific terms.
Judgement required: the framework supplies principles but the entity must select and document a policy.
Guidance gap: no authoritative answer was identified for the specific question.

For the protocol mechanics behind these questions, see Ethereum Gas Fee Accounting and Ethereum Staking Rewards: Recognition, Measurement, and Revenue.

Review date. Protocol, accounting and tax developments were refreshed through 31 August 2026. A gap means no authoritative answer was identified in the reviewed sources. It does not mean no practitioner has ever expressed a view.

Ethereum accounting: four levels of certainty

Ethereum accounting is not uncertain everywhere. Label each conclusion by the authority behind it.

EstablishedStandard or authority answers the point.
Reasonable interpretationExisting authority supports the conclusion.
Judgement requiredFramework principles require a documented policy.
Guidance gapNo authoritative answer identified for the specific issue.

Protocol precision cannot substitute for accounting, tax, or legal authority.

Native ETH has more open questions than native BTC, and the Ethereum accounting guidance gaps are not evenly spread. Almost all of them sit in three places: native staking rewards, gas, and the movement of ETH between the two ledgers. Those are also the three things an entity running its own validator does every single day.

Ethereum accounting guidance gaps: the judgement areas

Staking rewards

Guidance gap: when is a consensus-layer reward recognised for financial reporting? No IFRS or US GAAP pronouncement addresses native staking. The reward accrues every epoch. Candidate dates include accrual, the point the network confirms validation, the point the ETH becomes withdrawable, and receipt. Across the eight of nine SEC registrants that stake there are seven different published positions, six of them in audited annual financial statements and one in an unaudited quarterly report, including one that recognises ratably over each epoch and one that books its own rewards as other income rather than revenue. There is no market practice to fall back on.
Guidance gap: measurement instant. "Contract inception" and "time of receipt" both appear in audited filings. Under ASC 606 the noncash-consideration date is contract inception, but what "contract inception" means for a protocol reward is undefined. The only filer identified that pins it to a protocol event uses the beginning of each staking epoch.
Judgement required: is a validator a principal? Two registrants on the same network reached opposite conclusions, one presenting gross as principal node operator and the other net on the basis that "it is the validators that control the service".
Judgement required: the aggregation policy. Per-epoch recognition creates roughly 80,000 lots per validator per year. Every framework permits an aggregation convention. None specifies one. The convention chosen changes both the income number and the lot ledger. It must be documented before the period, not chosen after it.
Guidance gap: the accrual-method taxpayer. The only US ruling on staking rewards is expressly written for a cash-method taxpayer: its Issue, its single set of facts and the first sentence of its Holding all say so. Most reporting entities are on the accrual method, and nothing located addresses them.
Guidance gap: priority fees and MEV. The IRS ruling on staking rewards records that its facts "do not address any type of 'gas' or transaction fees other than the validation rewards described herein". CRA has published nothing that characterises or times them: its nearest text describes validator-node operators being "compensated with block rewards (for instance usually transaction fees or newly minted coins)", which records the receipt without characterising or dating it - Ethereum Tax in Canada. The UK manual has no hits for "gas" or "MEV". For an entity whose block rewards arrive as a payment transaction from a builder, this is not an edge case.
Established, in one place only. Canada has decided one question for proof of stake, and it is an indirect-tax one: CRA's GST/HST Notice 324 reads the Excise Tax Act definition of a mining activity so that validating "may be performed by any one of the various methods that cryptoasset networks use such as those that are commonly referred to as proof-of-work or proof-of-stake protocols", and property and services acquired for consumption, use or supply in the course of, or in connection with, the mining activity are deemed to be acquired otherwise than in the course of commercial activity, so input tax credits on those inputs are denied. The deeming attaches to the inputs, not to the person: a registrant that also carries on other activities loses the credits on the validator's inputs, not across the whole enterprise.

Gas

Guidance gap: gas that is not an acquisition or disposal cost. Own-wallet transfers, native staking deposits, contract approvals and failed transactions are unaddressed under both frameworks and, with one exception, by the three tax authorities in the reviewed set. The exception is the US position, and it sits in an IRS FAQ rather than in the regulations: a fee on a transfer between the taxpayer's own wallets is a disposition of the ETH used and is neither basis nor amount realised, a cost that goes nowhere. HMRC comes nearest on the rest, treating a fee satisfied in tokens as "a disposal in its own right" - but that is its individuals Capital Gains Tax page, the only page in the manual that says so, and it is written around a fee paid on a disposal, saying the fee "is given for a service that is used for the acquisition or disposal of tokens", and HMRC has not applied it to an own-wallet transfer.
Guidance gap: the burned base fee. It reaches no person. Ethereum for Accountants. US Treasury Regulation §1.1001-7(b)(1)(ii) characterises the use of digital assets to pay a fee as "a disposition of the digital assets for services", which presupposes a service provider, and the burn has none - but the definition at §1.1001-7(b)(2)(i) reaches "the amounts paid in cash or property (including digital assets) to effect the sale, disposition or acquisition of a digital asset", with no services qualifier at all, and the burn is paid to effect the transaction. The burn plausibly satisfies one and plausibly fails the other, and no authority located resolves it. Treasury was asked to address burning in T.D. 10000 and declined, saying the regulations "are not the proper forum to address those issues" - a declination rather than an answer. (The only official body identified as having reasoned about it at all did so in a non-binding EU VAT working paper, suggesting the base fee "is destroyed rather than paid to the network validators" and so is not consideration. That paper settles nothing even at EU level - it is a question put to Member State delegations - and it is outside this article's jurisdictions.)
Guidance gap: failed transactions. ETH is spent, nothing is received, and no framework or tax authority says whether that is an expense, a loss, or nothing.
Judgement required: materiality versus mechanics. The amounts are usually trivial. The reconciliation consequence is not, and neither is the count: each payment is technically a separate disposal event.

Moving between the two ledgers

Guidance gap: is depositing to the deposit contract a disposal? No US or Canadian guidance located, and no HMRC page addresses the deposit contract as such. The nearest UK material is a pair of pages on transferring tokens between distributed ledgers, verbatim identical on the point - one in the individuals series and one in the business and Corporation Tax series, CRYPTO41260, which is the one a company reader needs - and the reasoning on both rests on the statement that transfers out of the beacon chain are impossible, which has been untrue since April 2023.
Guidance gap: withdrawals. Neither the automatic sweep nor a requested partial withdrawal is addressed in Canada, the United States or the United Kingdom.
Reasonable interpretation: a withdrawal is not a second income event. Where rewards are already recognised as they accrue, the withdrawal is a movement of the entity's own ETH rather than income. No pronouncement says that of Ethereum; it follows from having recognised the reward already, and booking the execution-layer receipt again would count the same reward twice - Ethereum Staking Rewards: Recognition, Measurement, and Revenue.
Guidance gap: which lot leaves. The protocol has one balance and expresses no view. A withdrawal can carry the oldest lot, the newest where the reporting framework permits it, or an average, and the answer changes the gain on the eventual disposal.
Guidance gap: is a validator balance a "wallet or account"? US basis rules operate per wallet or account, and the term is defined by key custody alone: a digital asset is held in a wallet or account, per §1.6045-1(a)(25)(iv), "if the wallet, whether hosted or unhosted, or account stores the private keys necessary to transfer control of the digital asset". Nothing located applies that definition to a validator balance, so an entity's largest natively staked position may sit in something those rules do not describe.

Validator losses

Guidance gap: ordinary penalties and the inactivity leak. A missed or late attestation reduces the validator's ETH quantity with no transaction and no counterparty, and so does an inactivity leak, which drains the balances of validators that are not participating once the chain has failed to finalise for more than four epochs. Nothing located says whether that reduction is an impairment, a derecognition of units or an expense of the period. The workable answer is a documented policy - expense it, or net it against the reward income it sits beside - and the two give different revenue figures on identical facts. How to Account for Ethereum Transactions.
Guidance gap: slashing. No framework or tax authority in the reviewed set addresses how a slashing loss is measured or where it goes. It is not an impairment of value. The quantity of the asset falls. And it arrives in two instalments about eighteen days apart, which a close file built around a single event will miss. The gap is narrower than it was, in one corner only, and what fills it is a condition rather than a rule: Revenue Procedure 2025-31 §6.02(13) conditions a trust's staking safe harbour on the trust's digital assets being "indemnified from slashing due to the activities of staking providers" - provider activity, not protocol-wide events or client-software failures - and registrants disclose that indemnity inconsistently, the first mover to stake recording that "certain aspects of the 2025 Revenue Procedure are unclear, and therefore the Trust may not currently satisfy all conditions of the safe harbor", another that its provider-level cover "may not apply to protocol-wide events or software failures", and a custodian disclaiming any obligation to indemnify for slashing outside its own control. The safe harbour is also now effectively the only route: Revenue Procedure 2026-3 §4.01(42) put the classification of a staking trust on the list of areas in which rulings "will not ordinarily be issued", and the nine-month window §6.03 opened for amending trust agreements closed on or about 10 August 2026. None of it says what a slashing loss is for tax.

Measurement, control and evidence

Judgement required: the impairment unit of account under IAS 38 and IAS 36. The complete Ethereum journal-entry example shows $410.84 of impairment on a lot-level test and none on a holding-level test, on identical facts. Both are defensible and neither is prescribed, though the individual asset is IAS 36's stated default.
Guidance gap: the instant at which a departing unit is measured under ASC 350-60. The Subtopic says it "does not address the initial measurement, recognition, and derecognition of crypto assets", but ASC 350-60-05-2 does not stop there. Its second sentence directs the entity elsewhere: "Reporting entities shall account for the initial measurement, recognition, and derecognition of crypto assets in accordance with other generally accepted accounting principles (GAAP)." That other GAAP is codified and specific - ASC 350-10-40-1 through 40-3 and ASC 610-20 - and ASU 2023-08 itself amended ASC 350-10-40-3 to add subparagraph (d), "For crypto assets accounted for in accordance with Subtopic 350-60, recognize gains and losses from remeasurement" - a subparagraph that governs the transfer whose contract fails and whose asset is therefore not yet derecognised, rather than an ordinary disposal. What is not codified is the narrower step the practice depends on: remeasuring the departing units to fair value immediately before derecognition. That step is firm interpretation, and this article follows it as such.
Guidance gap: is a protocol restriction a "contractual" sale restriction? ASC 350-60-50-6 requires disclosure of contractual sale restrictions. A validator exit queue is a protocol restriction, not a contractual one. No source located addresses whether it is disclosable. The FASB's separate Fair Value-Contractual Sale Restrictions project is in board deliberations.
Judgement required: the price convention. No accounting or tax authority names a price source, which is a positive finding: the FASB expressly declined to add guidance because "the existing guidance in Topic 820 is sufficient". Venue, minute, timezone and fallback are the entity's to choose, document and defend. Real filers use midnight UTC, hourly spot at receipt, 4:00 p.m. New York, and 11:59 p.m. Eastern.
Judgement required: does the holder still own ETH held through an intermediary? The contract decides, and contracts differ within the same market: one platform's terms transferred title to the platform, another's provide that "Title to Supported Digital Assets shall at all times remain with you".
Judgement required: control of a delegated address. After EIP-7702 an ordinary address can have code attached by its own key and keep it until revoked, including after a failed transaction. A control conclusion reached at onboarding may not hold at the reporting date.
Established: the reward record disappears. Per-epoch reward detail is not retained indefinitely by an ordinary node. A query six epochs old returned "NOT_FOUND". An annual analysis of native staking income by component requires contemporaneous capture, an archive node, or a vendor whose decomposition is its own work product.
Established: internal transfers have no standard format. That is by design: "Defining the output schemas of named tracers is outside the scope of this specification." Two providers can hand an accountant different answers to the same question and both be right.

Tax accounting

Judgement required: deferred tax. IAS 12 and ASC 740 supply the model, but the answer cannot be computed from the chain. It needs a jurisdiction-specific tax basis, and under ASC 350-60 fair value it produces deferred tax on gains the entity has not realised, subject to a valuation-allowance analysis that, for a loss-making holder, can eliminate the asset entirely.

Developments that could change the analysis

Ethereum accounting guidance gaps also have a time dimension. A correct answer today can become stale because a standard setter, tax authority, legislature or the Ethereum protocol changes the underlying rule.

FASB

The FASB's Accounting for Transfers of Crypto Assets project remains active. The Board has tentatively decided to expand the scope of ASC 350-60 for certain crypto assets that give the holder a right to receive another in-scope crypto asset, and its stated next step includes further consideration of derecognition guidance for crypto transfer arrangements.

That project is relevant to wrapped and receipt tokens and to transfer-control questions. It does not create a staking-reward standard for native ETH.

IFRS

IFRS 18 Presentation and Disclosure in Financial Statements is effective for annual reporting periods beginning on or after 1 January 2027, with earlier application permitted, and replaces IAS 1. Presentation conclusions for periods before and after that effective date must therefore be dated.

The IASB is also conducting a broader Intangible Assets project examining IAS 38. Separately, cryptoassets remain one of the topics from which the IASB may select a future project as capacity becomes available. As at this review date, that does not amount to a standalone Ethereum or staking accounting standard.

Canada, the United States, the United Kingdom and the European Union

Canada's Bill C-31 contains proposed Crypto-Asset Reporting Framework provisions. Parliament's current LEGISinfo page shows the bill at consideration in committee in the House of Commons. The proposed rules must therefore remain labelled as draft rather than enacted law.

In the United States, proposed legislation can address network fees or other digital-asset questions without becoming current law. On the point that matters most for gas, no de minimis exclusion for spending ETH has been enacted, so every spend remains a disposition however small - Ethereum Tax in the United States.

The United Kingdom also has draft cryptoasset legislation with future commencement proposals. Draft text belongs in a "what may change" section, not in the current-law rule.

At EU level DAC8 remains the operative crypto-reporting instrument, and a DAC Recast proposal of 24 June 2026 would consolidate it, but that proposal is not law and its application dates are still written in square brackets - Ethereum Tax in the European Union.

Ethereum protocol

Ethereum.org currently describes Glamsterdam as an upcoming upgrade planned for Q4 2026. That is a planning statement, not an exact activation date. The Glamsterdam Meta EIP, EIP-7773, still shows the Mainnet activation epoch and timestamp as blank and says they will be filled when client teams decide them.

That distinction is important for accounting documentation. Do not date a protocol rule from a roadmap estimate. A changing mechanic becomes an operative protocol fact only when the relevant upgrade and activation are actually established.

The safe documentation rule is therefore:

State current Ethereum mechanics as at a date, identify the upgrade under which they operate, and treat future EIPs as proposals until activated.

And one thing that is settled

ETH is not a foreign currency. Under IFRS the reasoning chain runs from IAS 21's definition of a monetary item through the IFRS Interpretations Committee's conclusion that a cryptocurrency "does not give the holder a right to receive a fixed or determinable number of units of currency" and "is not cash". Under US federal tax the answer is express: virtual currency "is not treated as currency that could generate foreign currency gain or loss". A line labelled "FX gain on ETH" is wrong in both.

Close on what is settled

An article about Ethereum accounting guidance gaps should not leave the reader with the impression that nothing can be accounted for reliably.

Several foundations are settled. Native ETH is a protocol asset rather than a claim on an issuer. Ethereum's execution-layer balance contains no accounting-lot identity. Gas is a real ETH quantity outflow. Consensus rewards and execution-layer validator economics arise in different records. A validator withdrawal is a protocol movement that must not be mistaken for a second recognition of a reward already recorded. IFRS and US GAAP each provide existing frameworks that answer large parts of the holdings analysis, even though they do not answer every staking event. Jurisdictional rules are settled in places too: for US federal tax ETH is property rather than currency and generates no foreign-currency gain or loss, and basis is tracked per wallet or account; HMRC's individuals Capital Gains Tax guidance treats a fee satisfied in tokens as a disposal in its own right; and Canada has fixed the GST/HST character of proof-of-stake validation.

The remaining work is to label the boundary correctly.

Where authority exists, apply it. Where a framework requires a policy, document the policy. Where an Ethereum-specific conclusion is an interpretation, say that it is an interpretation. Where no authority was identified, preserve the gap rather than filling it with a confident sentence. Our crypto accounting guide covers the wider close workflow those policies sit in.

That is not weakness in the accounting analysis. It is what makes the analysis auditable.

How Tokenbooks helps with the judgment the standards leave open

The standards leave these questions to the preparer, and the useful thing a system can do is hold the answer the preparer reached. That is what Tokenbooks does. Gas treatment, the protocol-deposit reading between a taxable exchange and a non-taxable reservation, and whether a stablecoin is the base currency or a separate asset are per-portfolio toggles, so a policy is a value someone chose rather than a default nobody examined. A rules engine re-maps postings on stated conditions and actions, which means a posting can be traced back to the rule that produced it. Period close then locks the range and stores a hash of the source transactions and a hash of the booked journals, so the policy in force is fixed alongside the numbers it produced.

The ingestion underneath those policies is described on the Ethereum integration page.

Sources and authority map

EIP-7708, "ETH transfers emit a log". eips.ethereum.org
EIP-2780, "Resource-based intrinsic transaction gas". eips.ethereum.org
IASB agenda paper AP8B, November 2025, and IASB Update, November 2025. AP8B
IFRS 18. ifrs.org
KPMG IFRG, "Staking activities", questions and answers, June 2026. kpmg.com
FASB technical agenda and the crypto-transfers project page. agenda
KPMG, "Crypto assets" handbook, April 2026, and "Accounting for staking activities", April 2026. handbook
PwC, "Crypto assets guide", August 2025, and EY Technical Line, updated 28 March 2025. PwC
CRA, "Reporting income from crypto-asset mining and staking activities". canada.ca
Revenue Ruling 2023-14. irs.gov
26 CFR §1.1001-7, §1.1012-1 and §1.6045-1. §1.1001-7
HMRC Cryptoassets Manual, staking, costs and pooling. CRYPTO21200
FASB, Accounting for Transfers of Crypto Assets - project status last updated 8 July 2026.
IFRS Foundation, IFRS 18 - effective 1 January 2027 and replaces IAS 1.
IFRS Foundation, Intangible Assets project - current IAS 38 review.
IFRS Foundation, IASB pipeline projects - cryptoassets remains a potential future project topic.
ethereum.org, Glamsterdam - planned for Q4 2026.
EIP-7773, Glamsterdam Meta EIP - Mainnet activation epoch and timestamp not yet specified at review date.

Research status. Protocol mechanics and published guidance were refreshed through 31 August 2026. Where a source is interpretive rather than authoritative, the text says so. This article is educational research, not accounting, tax, legal, valuation, or investment advice.