On September 16, the House Ways and Means Committee will spend its afternoon deciding when a validator earns money. Not whether. When.
The distinction sounds academic until you run the arithmetic. A miner receives a block reward at 03:14 and, under current IRS treatment, recognizes ordinary income equal to the fair-market value of that reward at 03:14. The reward may not be sold. It may not be liquid. By the following April, the same coins can be worth forty percent less, and the tax bill is still denominated in the number from 03:14. That is not taxation. That is a margin call wearing the costume of civic duty. The ledger does not lie; only the interpreters do.
Two bills sit on the committee's schedule. H.R. 9172 and H.R. 9175 have already been filed by the trade press under "crypto tax clarity." They are nothing of the sort. They are an accounting patch: a correction to a timestamp. And the correction, if it survives the legislative relay, will move the economics of proof-of-stake more than any yield curve this cycle.
Context
Some framing is necessary, because the reporting on this has been loose. The "U.S. House Fundraising Committee" does not exist. The body is the House Ways and Means Committee, the oldest committee in Congress, and the one that owns Article I tax legislation. When Ways and Means schedules a markup, tax practitioners listen, because the committee's output is where tax law actually begins.
The current framework rests on a single administrative document: IRS Notice 2014-21, which classified convertible virtual currency as "property." That classification has two consequences that matter here. First, miners and stakers recognize income when they receive a reward, at fair-market value, as ordinary income. Second, because virtual currency is property and not a security, the wash sale rule of Internal Revenue Code Section 1091 does not apply. A trader in equities who sells at a loss and repurchases within thirty days is denied the loss deduction. A trader in bitcoin is not. That asymmetry is the entire commercial rationale behind H.R. 9175.
H.R. 9172 appears to address the timing question for miners and stakers. H.R. 9175 appears to close the wash sale gap. They are numbered consecutively, which suggests a package. Neither is law. A committee markup is one step in a relay that runs from the full House to a Senate companion, then to conference, then to the President. I have audited systems that shipped faster than this legislation will.
Core
Let me deal with the harder bill first, because it is the one the industry has misjudged.
The tax timing question is not a valuation question. It is a definition question. H.R. 9172, if it follows the structure of recent drafts, offers three choices for when income is recognized. Option A keeps the status quo: recognize at receipt. Option B defers recognition until sale, treating a block or staking reward like a restricted stock unit. Option C creates a separate "digital asset" category with its own treatment. The three produce materially different cash-flow profiles, and the difference is not cosmetic.
Consider a validator operating at scale. Under Option A, the operator pays tax on rewards that have not been sold, in a currency that has not been converted. This is the phantom-income problem, and it is the main reason large staking operations domicile outside the United States. Under Option B, the taxable event shifts to disposal, when the operator actually holds the fiat to pay. The economics of running a validator change by the cost of capital on the deferred liability, a number that CFOs, not traders, care about.
There is a wrinkle on the miner side that the commentary has ignored. A pool miner does not receive a block reward at all; the pool does. The miner receives a payout, typically on a schedule the pool controls, sometimes net of fees. If the bill defines receipt at block production, the pool miner's taxable event may precede the miner's actual receipt by days. If it defines receipt at payout, the pool becomes the reporting party. Either definition changes who files, when, and for how much. The bill does not have to be wrong to be expensive. It has to be unspecified.
The second bill is simpler and, in my view, more consequential. Section 1091 exists to prevent a specific abuse: the same economic position cannot be held across a loss-recognition boundary to manufacture a deduction. If H.R. 9175 extends it to digital assets, one of the quietest edges in crypto trading disappears. I have watched it get harvested for three years. When I reverse-engineered the incentive distribution of the early Curve Finance gauge system in 2021, I found that whale wallets were systematically subsidized by later depositors, because the reward-claim mechanics lacked slippage protection. The wash sale gap is the same story in a different ledger: an asymmetry that informed participants farm and uninformed participants fund.
Run the mechanics once, because abstraction hides the money. A trader holds one bitcoin at $60,000. She sells at $45,000, books a $15,000 loss, and buys back nine minutes later at $45,100. Under equity rules, that loss is void; she never left the position. Under current crypto rules, the $15,000 offsets gains elsewhere, and she keeps the exposure for $100. Multiply it across a book and it becomes a strategy. Multiply it across a retail base and it becomes a cottage industry. Remove it, and December volume at every exchange serving US taxpayers drops, not because the asset got worse, but because a subsidy was withdrawn.
The legislation also reaches DeFi, whether it means to or not. Liquidity mining rewards are received at accrual, at a market price, and paid out in the same illiquid token the protocol is subsidizing. If wash sale treatment extends to those rewards, the tax-loss harvesting that has become routine in yield farming shuts down. Protocols that subsidize TVL with emissions discover in the next quarter which of their "users" were liquidity and which were mercenaries. Tax symmetry does to strategy what an emission halt does to TVL. Most of it was never conviction.
Now the part neither bill names, and the part I care about most. The tax code asks for a timestamp. It does not define one. When, precisely, did the validator "receive" the reward? At the moment the block was produced? At the moment it achieved finality, which in most proof-of-stake networks is a probabilistic property, not a discrete event? At withdrawal from the staking contract to a wallet? Or at sale? Each answer maps to a different line in a different system and produces a different liability.
This is where the legislation becomes an engineering document by accident. Income recognition on a distributed ledger requires the tax authority to accept a consensus-defined state transition as the moment of ownership, and that is a trust assumption, not a mathematical fact. Trust is a bug, not a feature. The moment the IRS names a block height and calls it "receipt," it has adopted a definition of finality. And finality is a parameter, not a constant. Ethereum is the live example: for a long period, staking rewards accrued but could not be moved, which makes "receipt" a philosophical term before it becomes an accounting one.
The cross-chain industry has spent years trying to make verification trustless, and the honest practitioners will admit that the leading interoperable designs still route attestation through an oracle and a relayer, a small set of signers standing between state and settlement. The IRS is about to build the same architecture for tax: a single attesting party, the block producer, reporting an income event, with no relayer to check the signature. The treasury will get a number. It will not get a proof.
Structural checklist, because I do not publish without one:
- Definition risk: does the bill define "receipt" by block production, block confirmation, or withdrawal? Undefined terms become enforcement.
- Scope risk: are liquid staking rewards treated as received by the depositor or the protocol? The answer determines who files, and liquid staking is now the majority of staked ETH.
- Reporting risk: do the bills impose broker-style 1099 reporting on exchanges and wallet providers? This is where the industry has historically fought hardest and lost.
- Retroactivity risk: does the bill reach backward, converting prior filing positions into liabilities?
- Cross-agency risk: if the tax treatment assumes something about a reward's securities status, the IRS and the SEC can diverge. A single dataset supports both conclusions.
I audited the custody arrangements of the top three spot Bitcoin ETF applicants before the January 2024 approval, and the finding that shaped my practice was this: the operational gaps in multi-signature key management did not appear in any valuation model. Nobody priced them because no spreadsheet had a column for them. Tax timing is that same category of risk. It does not show up in a price. It shows up in a cash-flow statement, twelve months late.
The indirect effects are larger than the direct ones. If recognition moves to sale, the after-tax yield of every US-based proof-of-stake position rises without any change to the nominal reward rate. Staking-as-a-service providers, Coinbase, Kraken, the institutional validators, see taxable friction on their customers fall. Tax software sees demand rise no matter which option passes, because complexity is the product. And the honest answer to "who benefits most" may not be the miner or the staker. It may be the compliance industry the legislation forces into existence. The rollup world spends enormous capital debating data availability it will never saturate; the tax world is about to do the same with precision it will never use.
Contrarian Angle
The bulls have the direction right and the mechanism wrong. The consensus read is that "regulatory clarity is bullish." I do not accept the premise as stated. Clarity is not bullish. Clarity is a discount rate applied to uncertainty. What is bullish is symmetry, being taxed by the same rules as everyone else, at a moment you can plan around. The two bills move toward symmetry, which is why I think the medium-term signal is genuinely positive.
But the market is pricing the September 16 hearing as if it were the rule. It is not. It is a procedural step in a relay that has dropped the baton more often than it has carried it. FIT21 passed the House in May 2024 and then stalled in the Senate. The gap between a committee's stated intent and the Code's final text is where business models built on early assumptions go to die. The bullish case is right that infrastructure is being built. It is wrong that it is finished. And it is ignoring the possibility that the final text arrives harsher than the headline, that a bill sold as "clarity" lands as a reporting mandate with teeth.
Takeaway
Watch the definition, not the vote. If H.R. 9172 defines receipt by block finality, then every validator in the United States becomes a node in a public ledger the IRS can read, and the protocol's consensus mechanism quietly becomes the tax authority's clock. History repeats, but the gas fees change. The question worth answering is not whether these bills pass. It is who defines the timestamp when they do.
