CARF Covers Just 14% of $457B in Taxable Onchain Crypto Activity

A Chainalysis report published in late August 2026 puts a concrete number on a problem tax professionals have long suspected: the OECD's Crypto-Asset Reporting Framework captures only a sliver of the onchain activity that tax authorities actually need to see. The firm estimates that potentially taxable onchain crypto activity reached at least $457 billion globally in 2025, yet CARF-covered transactions account for just 14% of that total. For accounting firms, CFOs with digital asset exposure, and the compliance teams serving them, this gap is not a footnote. It is the central challenge of crypto tax reporting in 2026.

What the $457 Billion Figure Actually Covers

The Chainalysis estimate draws on activity across six major blockchains and encompasses realized capital gains, income from mining, staking and lending, and crypto-denominated payments. Critically, it excludes trading and other activity that takes place entirely within centralized exchanges, because that activity happens off-chain and is already subject to exchange-level reporting in most jurisdictions.

Regional Breakdown

North America led all regions with an estimated $134.6 billion in potentially taxable onchain activity. The United States alone accounted for $112.6 billion of that total. The European Union followed with $125.1 billion, making these two blocs the clearest focal points for regulators and compliance teams alike.

These figures are estimates based on blockchain data, not audited tax returns, so they should be treated as directional indicators rather than precise assessments. That said, even directional figures of this magnitude carry significant implications for how firms approach digital asset accounting software and onchain transaction monitoring.

Why Onchain Activity Differs from Exchange Activity

The distinction between onchain and exchange activity matters for tax purposes because the reporting pipelines are completely different. When a user trades on a centralized exchange, the platform holds the customer's tax residency data and, under most regulatory frameworks, is already obligated to report. When a user interacts directly with a smart contract on a decentralized protocol, there is often no intermediary collecting that information. The transaction is visible on-chain, but no entity is legally required to aggregate and report it to a tax authority.

CARF's Design and Its Structural Limits

CARF was developed by the OECD in 2022 as the crypto equivalent of the Common Reporting Standard. It requires covered crypto service providers to collect customer and tax residency information and report transaction data to domestic tax authorities, which can then share that data across borders through existing automatic exchange mechanisms. Data collection under CARF began on 1 January 2026 in 48 jurisdictions, including the United Kingdom and the European Union.

The Intermediary Problem

CARF's architecture is built around intermediaries. Colby Mangels, a former OECD adviser who contributed to the framework's development, has explained that CARF was designed to capture transactions facilitated by entities operating as crypto service providers in a business capacity. That design choice was deliberate: it mirrors the approach used in traditional financial reporting, where banks and brokers are the reporting agents.

The consequence, as Chainalysis's data makes plain, is that the 86% of onchain taxable activity sitting outside CARF's perimeter is structurally invisible to the framework. This includes activity on decentralized exchanges, peer-to-peer transfers between wallets, onchain income streams such as liquidity provision and yield farming, and direct crypto-denominated payments between counterparties. None of these have a regulated intermediary in the middle to trigger a reporting obligation.

DeFi Accounting and the Regulatory Horizon

The gap is not expected to remain static. Mangels noted that tax authorities are closely monitoring developments in anti-money laundering regulation, particularly the ongoing policy debate about when decentralized platforms or their operators should be classified as regulated crypto service providers. If regulators conclude that certain DeFi protocol operators do function as businesses facilitating transactions, those operators could be pulled into CARF's scope or an equivalent national framework.

In the EU, the Markets in Crypto-Assets Regulation and its accompanying AML package are already prompting questions about which DeFi activities trigger licensing requirements. In the US, Treasury and the IRS have signaled interest in the broker definition under the Infrastructure Investment and Jobs Act, which includes language potentially applicable to some decentralized protocol participants. Neither jurisdiction has finalized rules that would bring DeFi fully within automated reporting, but the direction of travel is clear.

Implications for Accounting Firms and CFOs

For B2B practitioners, the Chainalysis findings reframe the compliance conversation in two important ways.

Client Exposure Beyond Exchange Reports

Firms whose clients hold or transact in crypto cannot rely solely on exchange-issued reports to reconstruct taxable positions. The data suggests that a significant share of taxable events, staking rewards, DeFi yield, onchain payments, and peer-to-peer disposals, is occurring in environments where no third-party report will arrive automatically. Audit and tax teams need onchain data acquisition workflows, not just a process for ingesting exchange CSVs.

For CFOs at treasury functions that have allocated to digital assets, this is a governance issue as much as a tax one. If a treasury team is earning staking income or using DeFi protocols for yield, those activities generate taxable events that will not be captured by CARF-compliant platforms alone. The internal control environment needs to account for that.

Defi Accounting Positions and Documentation

The Chainalysis estimate includes income from staking and lending within its $457 billion figure. Both categories present specific accounting challenges. Staking rewards require a determination of fair value at the point of receipt, which may occur multiple times per epoch depending on the protocol. Lending income accrues continuously on some platforms. In jurisdictions following IFRS, the applicable guidance under IAS 38 and the emerging IASB work on crypto assets will inform recognition and measurement. Under US GAAP, FASB's ASC 350-60, which mandates fair value measurement for certain digital assets, is now in effect and shapes how staking income and DeFi returns appear on financial statements.

Robust defi accounting records, capturing entry timestamps, token quantities, and fair values at each taxable event, are no longer optional for any entity with material onchain activity. Digital asset accounting software that can pull directly from blockchain nodes or indexers, rather than relying solely on exchange data feeds, becomes a practical necessity for completeness.

Transfer Pricing and Cross-Border Considerations

For multinationals or funds operating across OECD jurisdictions, the interaction between CARF and the remaining 86% of onchain activity creates a transfer pricing and substance risk. Where a group entity in a CARF-participating jurisdiction is earning onchain income that will not be automatically reported to the local tax authority, there is no compliance safety net. The entity needs to self-report accurately, and the documentation supporting that position needs to be audit-ready.

What Tax Authorities Are Likely to Do Next

Tax authorities in the US, UK, and EU have all demonstrated increasing capability and willingness to use blockchain analytics in their enforcement work. HMRC has published explicit guidance on DeFi lending and staking. The IRS has included digital asset questions on Form 1040 since 2019 and has pursued John Doe summonses against exchanges to identify unreporting taxpayers. The European Commission's DAC8 directive, which overlaps with CARF in EU member states, extends reporting to crypto-asset service providers regulated under MiCA.

The 86% figure identified by Chainalysis is not a safe harbor. It reflects a current gap in automated third-party reporting, not an absence of legal obligation. Taxpayers with onchain activity remain liable regardless of whether a platform files a report on their behalf. Enforcement actions targeting unreported DeFi income and staking rewards are a logical next step for revenue authorities seeking to close the gap between what CARF captures and what blockchain analytics can see.

Practical Steps for Firms and Their Clients

Audit the Onchain Footprint

The starting point for any firm advising clients with crypto exposure is a complete wallet and protocol inventory. This means identifying every address the client controls, every DeFi protocol they have interacted with, and every onchain income stream they have earned. Without this inventory, it is impossible to assess CARF coverage gaps on a client-specific basis.

Build Onchain Data Pipelines

Exchange reports and CARF submissions from platforms will cover the 14% that falls within scope. The remaining exposure requires a separate data acquisition process: pulling transaction histories directly from blockchain explorers or via API, classifying each event by type (disposal, income, payment), and applying consistent fair value measurements. This is where crypto bookkeeping software capable of onchain data ingestion, rather than exchange-only integration, becomes critical to completeness.

Document the Tax Position for Each Event Type

Different income types carry different tax treatments across jurisdictions. Staking rewards may be income at receipt in the UK and US but treated differently in some EU member states. DeFi lending interest may be subject to withholding in certain structures. Crypto-denominated payments trigger disposal events in most OECD jurisdictions. Each category needs a documented position supported by the applicable authority, not a generic assumption that exchange-level reporting covers everything.

Monitor the Regulatory Pipeline

Given the explicit signal from former OECD advisers that CARF's DeFi gap is on regulators' radar, firms should track AML rulemaking in their key jurisdictions for any moves that would reclassify DeFi operators as reporting entities. A regulatory change bringing even a subset of DeFi protocols into scope could create new client obligations within a single filing year, requiring rapid adaptation of data workflows.

Source: Cointelegraph

Frequently Asked Questions

What does the $457 billion figure include?

It covers potentially taxable onchain crypto activity across six major blockchains in 2025, including realized capital gains, income from mining, staking and lending, and crypto-denominated payments. It excludes trading activity conducted within centralized exchanges.

Why does CARF only cover 14% of this activity?

CARF is designed around regulated crypto service providers acting as intermediaries. Decentralized exchanges, peer-to-peer transfers, and onchain income streams often have no centralized operator obligated to collect and report customer data, so they fall outside the framework's current scope.

Does the CARF gap mean onchain income is not taxable?

No. The absence of automatic third-party reporting does not affect the underlying tax liability. Taxpayers in OECD jurisdictions remain legally obligated to declare onchain income and gains regardless of whether a platform files a CARF report on their behalf.

How should accounting firms handle DeFi income that is not covered by CARF?

Firms need to build onchain data acquisition workflows that pull transaction histories directly from blockchains, classify each event by type, apply appropriate fair values at the point of each taxable event, and document the tax treatment based on applicable authority in the relevant jurisdiction. Relying solely on exchange-issued reports will leave material gaps.

Could DeFi protocols eventually be brought within CARF's scope?

Potentially, yes. Former OECD advisers have indicated that tax authorities are monitoring AML rulemaking to determine when DeFi operators should be treated as regulated service providers. Any such reclassification could extend reporting obligations to protocol operators, though no finalised rules have been published in any major jurisdiction as of the date of this article.