Episode Summary
Executive Summary: This episode examines the IRS’s proposed crypto broker reporting rules, which would expand tax reporting far beyond centralized exchanges into DeFi, wallets, payment processors, and other intermediaries. Guests from Coinbase and CoinTracker argue the rules are overbroad, administratively unworkable, and privacy-invasive, while proposing narrower, phased reporting and blockchain-based compliance tools instead.
Main Topics: Scope of the IRS proposed crypto broker rules (Priority: 5/5): The guests explain the 2021 Infrastructure Act, the August 2023 proposed regulations, and how they attempt to define who counts as a broker and what transactions must be reported. Impact on centralized exchanges vs. DeFi (Priority: 5/5): Centralized exchanges are expected to comply, but the rules could also capture DeFi front ends, wallets, liquidity providers, and payment processors in ways the guests say are impractical. Administrative burden and data quality concerns (Priority: 5/5): The guests argue the rules would create massive volumes of incomplete or duplicated reporting, overwhelming brokers, taxpayers, and the IRS itself. Stablecoins, NFTs, and tokenized assets (Priority: 4/5): They debate whether stablecoins and NFTs should be excluded, with both guests favoring carve-outs for non-financial or low-gain/loss transactions. Privacy and wallet-address reporting (Priority: 5/5): The transcript highlights concerns that requiring wallet addresses and transaction hashes on forms would undermine crypto privacy and raise security risks. Alternative compliance models and blockchain solutions (Priority: 4/5): The guests propose attestation tokens, taxpayer-reconciled data, and blockchain-native reporting as better long-term approaches than broad broker reporting. Process, comments, and likely timeline (Priority: 4/5): They discuss the unusually high number of public comments, the November 13 hearing, and why final rules may be delayed or vulnerable to litigation.
Key Arguments: The proposed rules are unadministrable because they treat too many actors as brokers and require information many intermediaries cannot know, such as cost basis for self-custodied assets. The IRS/Treasury should focus first on parity with traditional financial brokers, covering the majority of transactions before expanding to more complex parts of crypto. DeFi interfaces, hosted wallets, and payment processors may be forced into KYC/reporting roles that conflict with how they currently function and with user privacy expectations. Stablecoin transactions often create trivial gains or losses, so forcing 1099-DA reporting on them would create huge reporting volume with little tax value. NFTs should be treated based on what they represent: financial NFTs may be reportable, but non-financial NFTs should not be automatically swept in. Including wallet addresses and transaction hashes on tax forms could expose users to surveillance and hacking risks, unlike traditional securities reporting. Blockchain-based attestation tokens could let platforms prove tax identity and compliance without revealing full PII to everyone on-chain. Tax aggregation tools like CoinTracker could help brokers incorporate missing cost-basis information from self-custodied wallets to produce more accurate reports. The IRS should phase in reporting, starting with centralized exchanges, and avoid imposing an impossible compliance deadline on smaller firms. The final regulations, if unchanged, may be challenged in court as exceeding statutory intent and the Administrative Procedures Act process.
Data Points: Infrastructure bill passed: November 2021 - Established that crypto brokers should report like stockbrokers, prompting later Treasury/IRS regulations. Proposed IRS regulations released: August 2023 - A 282-page proposal defining crypto broker reporting requirements. Comment period length: 60 days - Industry had a 60-day window to submit feedback on the proposed rules. Comment deadline: November 13, 2023 - Last day for public comments before IRS moved toward finalizing the rules. Public comments submitted: Almost 120,000 - Reported as an unprecedented volume of responses to an IRS proposed rule. IRS expected reports: 8 billion - IRS commissioner’s office estimate for reports generated by the crypto rules alone. Current IRS information-reporting volume: About $5 billion - Existing annual information-reporting regime across all brokers and other forms. Potential reporting timeline: 2025 tax year / 2026 filing season - Guests discussed that regulations may be effective for 2025 activity, though likely delayed. Number of speakers at hearing: About 12 - Industry hearing on November 13 included Coinbase, OpenSea, Blockchain Association, CoinTracker, and others. Number of broker-type categories described: 5 - Digital asset platforms, hosted wallet providers, payment processors, other brokers, and real estate persons transacting crypto. Number of broker exclusions described: 3 - Merchants directly accepting crypto, validators, and wallets/software without swap features were excluded. Number of recommendations in comment letters: 15 - Coinbase speaker said the two comment letters contained fifteen recommendations.
Pivotal Quotes: "Well, my own view is that these rules, as proposed, are unadministrable." — Lawrence Lakin: Opening assessment of the proposed IRS broker regulations. "The current entire information reporting regime ... is about $5 billion today. So, just for crypto alone ... the IRS is expecting $8 billion." — Lawrence Lakin: Illustrating the scale mismatch between existing IRS reporting capacity and the proposal. "we strongly believe that if you self-custody, you had to kind of self-reconcile your crypto activity across multiple wallets and exchanges" — Shihan Chandra Sekara: Explaining why CoinTracker sees a need for data aggregation tools in the reporting ecosystem.
Implications: The rules could reshape crypto compliance, push DeFi and wallet providers toward KYC/reporting, and spark litigation if finalized unchanged. A narrower phased approach and blockchain-native identity/reporting tools may be the most workable path.