How to Classify DeFi Transactions for Form 8949: A CPA's Guide

One of the most technically demanding areas in cryptocurrency tax compliance today is the classification of decentralized finance (DeFi) transactions for Form 8949.

If you are actively trading, providing liquidity, staking, or borrowing across DeFi protocols — and you are not working with a CPA who understands on-chain transaction mechanics — there is a strong likelihood that your returns contain classification errors. Those errors cut both ways: they can result in overpayment or, more consequentially, underreporting exposure in an IRS examination.

This article outlines how we approach DeFi classification at CFO Associates, the taxonomy of taxable events that practitioners need to understand, and the documentation standards that hold up under scrutiny.

Why DeFi Classification Is More Complex Than Centralized Exchange Activity

Centralized exchanges (CEX) like Coinbase or Kraken produce trade history exports with clearly labeled buy/sell pairs, timestamps, and USD cost basis approximations. DeFi operates on an entirely different set of mechanics.

A single wallet interaction with a protocol like Uniswap or Aave can generate multiple token transfers across several smart contract calls — none of which arrive with pre-computed cost basis or a clean classification label.

The core challenges our team navigates when working with DeFi-active clients include:

1. No 1099 Reporting. DeFi protocols do not issue Form 1099-B or 1099-MISC. The full transaction history must be reconstructed from on-chain data.
   
   
2. Multi-Step Atomic Transactions. A single blockchain transaction can simultaneously contain a token swap, a fee collection, and a token approval. Each sub-event may carry distinct tax treatment.
   
   
3. Protocol-Specific Mechanics. Depositing into a Curve stablecoin pool behaves differently from depositing into an Aave lending market, even though both involve sending tokens to a smart contract address. The classification cannot be assumed — it must be analyzed per protocol.
   
   
4. Limited IRS Guidance. Existing guidance covers cryptocurrency as property (IRS Notice 2014-21) and staking rewards (Rev. Rul. 2023-14), but does not directly address the majority of DeFi-specific events. Practitioners are largely working by analogy and professional judgment.
   
   

DeFi Taxable Events: A Working Taxonomy

Before examining individual protocols, it is useful to establish a taxonomy of DeFi taxable events and their likely Form 8949 treatment under current guidance.

A note on authority: IRS Notice 2014-21 established that virtual currency is treated as property for federal tax purposes, meaning general property disposition rules under IRC §1001 govern most events. Rev. Rul. 2023-14 confirmed staking rewards are includible in gross income in the year the taxpayer gains dominion and control. Beyond these two, practitioners are applying professional judgment and analogical reasoning — and that judgment must be documented.

Per-Protocol Classification: How We Approach Common Protocols

Uniswap V3: Swaps and Concentrated Liquidity

Swaps. A standard Uniswap swap — for example, disposing of 1 ETH in exchange for 2,000 USDC — is a straightforward taxable disposition under IRC §1001. The amount realized equals the fair market value (FMV) of the USDC received. The cost basis is the taxpayer's adjusted basis in the ETH.

Concentrated liquidity positions. When a user deposits Token A and Token B into a Uniswap V3 position, they receive an ERC-721 NFT representing that liquidity position. The defensible position is that this constitutes a simultaneous disposition of both tokens in exchange for the LP NFT — a taxable exchange. Upon withdrawal, the NFT is disposed of, and the tokens received constitute the amount realized.

The complicating factor: the ratio of Token A to Token B at withdrawal will differ from the deposit ratio due to price movement, requiring precise tracking of the NFT's adjusted basis throughout the holding period.

Aave V3: Supply, Interest, and Borrow

Supplying assets. When a user deposits USDC into Aave V3, they receive aUSDC — an interest-bearing receipt token. One reasonable position treats this as analogous to a bank deposit rather than a taxable property exchange, since aUSDC is redeemable 1:1 for USDC plus accrued interest. A counter-argument exists that any exchange of one digital asset for a different digital asset triggers IRC §1001. We document whichever position is adopted and apply it consistently.

Interest accrual. The aUSDC balance increases on each block as interest accrues. Under the reasoning of Rev. Rul. 2023-14, these accruals are likely ordinary income at the time the taxpayer gains dominion and control — which with Aave occurs continuously.

Borrowing. Taking a loan against collateral on Aave is generally not a taxable event, consistent with traditional secured lending treatment. The collateral lockup is not a disposition. However, if the position is liquidated, the seizure of collateral is a taxable disposition that must be reported.

Curve Finance: Pool Deposits and Meta-Pools

Curve pool deposits involve sending one or more stablecoins in exchange for a Curve LP token. The mechanical analysis parallels Uniswap LP provision: the deposit is likely a disposition of the contributed assets in exchange for the LP token, with basis in the LP token equal to the FMV of assets contributed at deposit.

Curve's meta-pool structures — where LP tokens are deposited into additional pools — create layered basis tracking requirements. Each layer needs to be independently documented to reconstruct an accurate cost basis at the point of final disposition.

Lido: Liquid Staking (Actively Debated)

Lido allows users to stake ETH and receive stETH. The tax treatment remains one of the most contested areas among practitioners:

Position A — Not a taxable exchange. stETH represents a claim on staked ETH and its accrued rewards, analogous to a deposit receipt. Under this view, no gain or loss is recognized at the time of staking, and the daily stETH balance increases are ordinary income as staking rewards accrue.

Position B — Taxable exchange. ETH and stETH are distinct digital assets with independent market values and different risk profiles. The exchange triggers IRC §1001, and basis in stETH is established at its FMV at receipt.

Both positions have merit under current guidance. The practitioner's obligation is to choose one position, apply it consistently across all relevant clients and tax years, and document the reasoning thoroughly. Regardless of which position is adopted, the ongoing staking reward accruals are almost certainly ordinary income under Rev. Rul. 2023-14.

Where Classification Errors Are Most Common

Many DeFi tax analyses rely on a single data source — typically a block explorer export or a single-source aggregation tool. This approach introduces systematic classification errors that are difficult to detect after filing.

The most common failure points include:

• Missing internal transactions. Block explorers do not consistently surface internal contract calls, meaning token transfers within a single transaction hash can be entirely invisible in a standard export.
  
  
• Incorrect event labeling. Single-source tools often label transactions based on the outermost function call (e.g., "swap") without examining what happened at the token transfer level. A "swap" routed through three intermediate liquidity pools generates multiple distinct dispositions.
  
  
• No cross-chain visibility. A bridge transaction moving tokens from Ethereum to Arbitrum appears as a send on one chain and a receive on another. Without correlating both sides, a single-source approach may classify the send as a disposition and the receive as income — double-counting the taxable event.
  
  
• Stale or imprecise price data. Accurate FMV at the exact block timestamp is essential. Tools relying on daily closing prices rather than block-level pricing introduce basis errors that compound across subsequent transactions.
  
  

Based on practitioner experience, single-source classification produces errors in 15–40% of events for a typical DeFi-active wallet with 200+ transactions across multiple chains. These are not edge cases — they are the expected outcome of an inadequate methodology.

Documentation Standards for Audit Defense

If a return involving DeFi activity is selected for examination, the classification methodology itself will be reviewed. At CFO Associates, we maintain the following documentation standards for all DeFi-active clients:

1. A written classification policy mapping each DeFi event type to its tax treatment, with citations to applicable authority or documented analogical reasoning.
   
   
2. Per-client transaction logs showing raw on-chain data — transaction hash, block number, timestamp, token transfers — alongside the classification applied to each event.
   
   
3. Basis tracking records tracing cost basis from original acquisition through each intermediate event (wrapping, pooling, bridging) to final disposition.
   
   
4. FMV source documentation identifying which price feeds were used and at what timestamp granularity for each event.
   
   

The objective is to demonstrate that a consistent, well-reasoned methodology was applied — particularly in areas where IRS guidance is ambiguous. Inconsistent treatment of similar transactions across clients or across tax years is the most common vulnerability we see in examination situations.

Key Takeaways for Crypto Investors and Web3 Operators

DeFi transaction classification is not a problem that will simplify itself over time. Protocol complexity is increasing, cross-chain activity is growing, and IRS guidance continues to lag significantly behind the technology.

If you are a crypto investor, Web3 founder, or operator actively using DeFi protocols, the essential steps to protect your tax position are:

1. Ensure your CPA has a documented classification policy covering each type of DeFi event — not just centralized exchange activity.

1. Verify that your transaction data is being reconstructed from multi-source on-chain data, not a single block explorer export.
2. Confirm that ambiguous positions — particularly around LP token treatment and liquid staking — have been explicitly addressed and documented.
3. Maintain block-level pricing records for FMV determinations throughout the tax year.

Are you currently working with a CPA who has a documented methodology for your on-chain activity? If you would like us to review your DeFi tax position, schedule a strategy call with our team at https://www.thecfoassociates.com/contact