Tracing the liquidity trails through the U.S. tax code is a strange discipline for someone who spent three months in 2018 arguing about Casper FFG gas assumptions in private Discord channels. But here we are. On a Monday that will be remembered less for what it announced and more for what it deliberately refused to name, the Internal Revenue Service dropped a notice suggesting that the in-kind redemption mechanism used by a slice of the crypto fund complex may be an abusive tax shelter. No name. No ticker. No list. Just a wide, cold net cast into a corner of the market most retail investors did not know existed — and a companion revenue ruling, dated 2026-20 in the document trail, that simultaneously killed the Section 351 conversion pathway wealthy investors had used for years to swap appreciated assets without triggering a taxable event.
The framing matters more than the facts, and the framing is wrong. Every headline I have read in the last forty-eight hours has compressed this into a story about the IRS "coming for crypto ETFs." That is not what happened. What happened is narrower, stranger, and far more revealing about how deeply crypto has embedded itself into the machinery of traditional finance. The IRS did not attack crypto ETFs. The IRS attacked a specific tax-arbitrage architecture that a set of regulated investment companies use to maintain a privileged tax status they probably should never have qualified for in the first place. The distinction is not semantic. It is the difference between a hunter shooting into a forest and a hunter shooting at one specific animal while the rest of the herd panics.
I have spent the better part of two decades watching regulators write rules so broad that compliance officers cannot tell what is legal, and so vague that enforcement becomes a discretionary act of narrative selection. This notice belongs to that tradition. But before the panic metastasizes into a full-blown 'IRS vs. Bitcoin' storyline, it is worth doing what I always do when the market reacts to a headline without reading the document: construct the truth from fragmented data.
What Actually Dropped, and Why the Date Itself Is a Warning
Let me start with the anomaly, because forensic deconstruction begins with the inconsistency, not the conclusion. The parsed material describes two separate time markers that point to 2026 — a tweet dated September 28, 2026, and a revenue ruling numbered 2026-20 — while the surrounding narrative adopts the tense of breaking news, complete with a comment period closing on October 28. Both cannot be true in a single coherent timeline. Either this is synthetic or test data, a date transposition, or a forward-cast scenario being written as if it were present. I flag this up front because the integrity of your response to a tax rule depends entirely on knowing whether the rule actually exists yet. Anyone building a position around a document whose own timestamp is internally contradictory is doing astrology, not analysis.
That said, the substance is coherent enough to reverse-engineer, and the substance is what matters for the funds involved. The notice targets a mechanism, and the mechanism has three moving parts that anyone holding a crypto-adjacent fund needs to understand.
Part one: the in-kind redemption. In a conventional ETF, when a large holder wants out, the fund does not sell assets on the open market. It hands the underlying assets to an authorized participant — usually a Wall Street trading desk — and the AP extinguishes the shares. For tax purposes, this is treated as a transfer of property rather than a sale, which means unrealized gains stay off the fund's books. In a bitcoin ETF, this is the mechanism that keeps the fund's capital-gains distributions near zero. It is elegant, it is legal in most contexts, and it is the entire reason a spot bitcoin ETF can track its underlying asset with a whisper of tracking error.
Part two: the RIC threshold. A Regulated Investment Company escapes tax at the fund level — a status that functions as a subsidy — only if it derives at least ninety percent of its income from dividends, interest, and gains on securities. Crypto profits and commodity profits do not count as qualifying income. A fund that holds too much crypto-derived income can blow through the threshold and lose its pass-through status entirely. Suddenly the fund itself owes tax, and the shareholders who bought it for the tax efficiency get the opposite of what they paid for.
Part three: the workaround. Here is where it gets interesting, and where the IRS's actual target sits. A fund that wanted to hold crypto exposure without poisoning its RIC income basket could route those positions through an offshore subsidiary, or hold trust shares, or — and this is the surgical pin the IRS is now driving into — use in-kind redemptions to push bad income off the ledger before it can be counted. The notice explicitly states that its guidance applies both to funds holding assets directly and to funds holding them through a trust. That sentence is the whole ballgame. It forecloses the shell-swap defense before anyone has a chance to raise it.
And then there is the derivative layer. According to ETF analyst commentary embedded in the source material — the kind of detail that only surfaces when someone is reading the technical footnotes rather than the press release — the structures under scrutiny included box spreads and straddle options used to manufacture or defer specific tax outcomes. I have seen this movie before. In 2021, while the rest of the market was chasing yield in the Curve Wars, I was mapping how veCRV mechanics created governance power that had nothing to do with the token's stated utility. Tracing the liquidity trails taught me one lesson that never stops paying: the interesting money is never where the chart says it is. It is in the structure. The structure is where the arbitrage lives, and the arbitrage is always what the regulator eventually finds.
The Ruling Nobody Is Talking About
If the crypto ETF notice is the loud half of this story, Revenue Ruling 2026-20 is the quiet half, and the quiet half is the one that tells you what the IRS actually believes.
Section 351 of the Internal Revenue Code has long allowed investors to contribute appreciated property to a corporation in exchange for stock without triggering immediate recognition of gain — provided the contributor ends up with control of the receiving entity. Financial engineers spent decades stretching this into a vehicle for wealthy investors to swap a concentrated, appreciated stock position into a diversified fund without paying capital gains on the way in. The conversion pathway was never intended to be a free lunch of infinite deferral, but it functioned as one. Revenue Ruling 2026-20, released the same day as the crypto notice, closes it.
The simultaneity is not a coincidence, and I want to be precise about why it unsettles me. A regulator that fires two shots in one afternoon is not reacting to a single complaint. It is executing a doctrine. The doctrine, stripped to its core, is this: a transaction that changes the economic substance of a position should be taxed, and the wrapping is irrelevant. Whether the wrapper is a stock swap or a crypto fund's in-kind redemption, the principle is identical. The IRS has decided that a decade of structure-driven tax avoidance has gone far enough, and it is using the crypto fund complex as one of several demonstration sites.
The reason this matters for the crypto narrative is that it inverts the causal story the market tells itself. The market believes crypto gets special hostile treatment because crypto is new and scary and decentralized. The document trail suggests the opposite: crypto funds are being treated exactly like every other sophisticated financial product that uses structure to escape tax. That is, in a strange way, a sign of maturity. You are not being singled out. You are being assimilated. And assimilation into the old tax physics is not the victory celebration the ETF approval crowd promised.
I sat through the entire spot bitcoin ETF approval cycle in 2024 and wrote at the time that it was not a crypto adoption event but a traditional finance encapsulation event. The IRS notice is the proof of concept arriving two years late. Once your asset is inside a regulated vehicle, it becomes subject to the same gravitational laws as every other regulated vehicle. That means the same audits, the same income thresholds, the same structure police. The encapsulation was never going to spare you. It was going to expose you.
The Architecture That Decides Who Is Bleeding and Who Is Not
Now the operational part, because in a bear market the only question that matters is whether your specific exposure is safe. The source material gives us enough to draw a hard line between two classes of crypto fund, and that line is structural, not performative.
Class one: the grantor trusts. The iShares Bitcoin Trust — and its siblings sitting inside the largest spot bitcoin ETFs — is structured as a grantor trust. In a grantor trust, the trust itself is not a taxable entity. The tax attributes of the underlying assets pass straight through to the holders. There is no RIC threshold to breach, because there is no RIC status to protect. There is no ninety-percent income test, because the fund is not even trying to be a regulated investment company. Whatever tax consequences exist are borne by the shareholder in the same way they would be if the shareholder held the bitcoin directly. This is precisely why the mainstream spot bitcoin ETFs are, in the language of the source analysis, low risk with respect to this notice. They are not using the mechanism the IRS is targeting, because their architecture does not require it.
That structural immunity is the single most important fact in this entire episode, and it is the fact that the headlines most aggressively obscure. If you hold a spot bitcoin ETF in a grantor-trust wrapper, the IRS notice is not aimed at your vehicle. You can stop refreshing the news.
Class two: the RIC-constrained funds. Here is where the bleeding starts. A fund that wants crypto exposure but insists on maintaining RIC status — because RIC status means fund-level tax exemption, which is a real economic advantage — faces a fatal arithmetic problem. Crypto gains and commodity income do not count toward the ninety-percent qualifying-income threshold. Hold enough crypto directly and you fail the test. The workaround was to hold through a trust, or to use in-kind redemptions to keep the offending income off the ledger, or to park positions in an offshore subsidiary outside the notice's reach. Each of these is now either explicitly covered by the notice, explicitly closed by the revenue ruling, or — in the case of the offshore subsidiary — conspicuously left untouched.
That last point deserves a flag rather than a conclusion. The source material notes that funds holding crypto through offshore subsidiaries sit outside the notice's stated coverage. I am not going to tell you that this is a durable safe harbor, because I have watched enough regulatory cycles to know that the apparent gap is often the trap. But I will tell you what it means in the near term: the gap creates an incentive to migrate structure offshore, and migration incentives create the next compliance-arbitrage wave. Watch the SEC filings. When a fund changes its structure, the disclosure shows up in the paperwork before it shows up in the price.
The Retroactivity Problem — The Real Tail Risk
I want to spend disproportionate time on one sentence from the notice, because that sentence is where the actual danger lives, and it is the sentence the market is most aggressively underpricing.
The IRS stated that any forthcoming guidance might apply only prospectively — or it might apply retroactively to transactions that have already occurred. Read that twice. A regulator is explicitly reserving the right to reach backward in time and reclassify transactions that were, at the moment they were executed, plausibly compliant.

This is the regulatory equivalent of changing the rules of a card game after you have already shown your hand, and then telling the table the change might apply to the hands already played. The core risk here is not the enforcement itself. The core risk is the destruction of legal certainty. A prospective rule tells you what to do next. A retroactive rule tells you that what you did last year might now be a liability, and that you cannot know which until the comment period closes and the final language drops.
For funds that executed Section 351 conversions or leaned on in-kind redemptions to protect their RIC status, retroactivity means a one-time tax liability against transactions already booked, plus penalties, plus a period of frantic reconstruction in which every past redemption has to be re-examined. The source material flags this as the highest-priority risk, and I agree, because it hits the two most fragile things a fund has: its tax provision and its net asset value. A surprise tax bill against past transactions does not just cost money. It corrupts the NAV that the market prices against, and a corrupted NAV in a fund is a wound that bleeds for quarters.
There is also a legal-doctrinal reason to expect a fight. U.S. tax law generally resists retroactive application where taxpayers had a reasonable reliance interest in the prior treatment. Retroactivity is not a magic wand the IRS can wave without consequence. The source analysis anticipates that a final rule with retroactive teeth could draw litigation on due process and reliance grounds. That is the second-order gamble: the IRS proposes retroactivity to maximize deterrence, and the courts may strip it back, and the market has to price the whole uncertain arc. Constructing the truth from fragmented data here means accepting that the most important variable — whether the reach extends backward — is unknowable for weeks, and that any fund telling you it has already assessed the impact with confidence is telling you something it cannot possibly know.
Who Is Actually Exposed, Mapped Cold
The honest answer is that this is a story about two different markets wearing the same ticker prefix, and the two markets have opposite risk profiles. Let me lay it out the way I would lay out a forensic audit, because that is the discipline this deserves.
On the immune side sits the grantor-trust complex: the large spot bitcoin ETFs, structured so that tax attributes pass through and no RIC threshold is ever at stake. The notice does not reach them because they are not using the mechanism. The headline says 'crypto ETFs.' The document reaches a subset of them, and for the largest and most widely held products, the subset does not include you.
On the exposed side sits a thinner, quieter layer: the RIC-form funds that hold crypto or trust shares, the funds that depended on in-kind redemptions and Section 351 conversions to keep their tax status intact, and the funds whose tax provisions were built on top of those mechanisms. These are not household names. They are exactly the kind of product that gets voted on once, quietly, in a committee, and then never makes the front page — until now. If you own exposure you cannot fully explain, this is the week to explain it.
The middle layer is the operational one, and it is the layer most people miss. The authorized participants and the Wall Street trading desks that execute in-kind redemptions are the transmission machinery. If the IRS suppresses in-kind redemption for the affected funds, those funds may be forced toward cash creation and redemption — a cheaper-to-administer but less capital-efficient model. Less efficiency means wider spreads, higher tracking error, and fatter discount/premium cycles. You may never notice it in a quiet market. In a bear market with stressed liquidity, you will notice it every time you try to exit.
And then there is the value transfer nobody is pricing. Compliance and tax advisory demand is surging. The source material cites advisors recommending that clients review their historical conversion positions. Somebody has to do that review. In a market where the trading desks are shrinking, the audit desks are expanding. The collateral damage of a tax-enforcement wave is never evenly distributed: it is a transfer from the aggressive to the cautious, and from the fund to the accountant.
The Contrarian Cut — Why This Is Not an Attack on Crypto, and Why That Should Worry You More
Here is the reading I am offering against the grain, and I want to be direct about the trade I am making with you as a reader: the bearish headline is wrong, but the bullish dismissal is also wrong, and the truth is worse than both for anyone who invested emotionally in the 'crypto grows up' narrative.
The surface-level contrarian take is obvious and I will dispatch it quickly: this is not an IRS war on bitcoin. ETF analysts quoted in the source material characterized the action as targeting trades that departed from the spirit of the law, not the asset class. The grantor-trust products are untouched. Bitcoin the asset does not care about a fund's RIC status. So if your takeaway is 'IRS vs. Bitcoin,' you have been played by a headline writer who needed your click. Discard it.
The deeper contrarian take is the one nobody wants to hear, and it is this: being assimilated into the traditional tax regime is the true end of the crypto exemption narrative, and it arrived not with a bang of prohibition but with a whisper of compliance. When the IRS treats a crypto fund exactly as it treats a stock-conversion shelter — same doctrine, same revenue-ruling hammer, same retroactivity reservation — it is confirming that crypto is no longer special. It is just another asset class subject to the same structure-police that have always governed wealth. The people who sold you the ETF as a bridge to a new financial system omitted the part where the bridge deposits you directly into the old one.
I learned this framing the hard way in 2022, when I spent weeks auditing the on-chain flow from Alameda to FTX and concluded that the collapse was not a market event but a narrative collapse of 'trustless trust.' The lesson transferred: diagnosing the fatal flaw in a structure is more valuable than debating its ideology. The ideology of this notice says 'crackdown.' The structure of this notice says 'normalization.' Normalization is the less comfortable outcome, because it means the crypto tax advantages that early adopters treated as a birthright were always a temporary arbitrage, and the window is closing on schedule.
There is a final irony worth naming, and it connects to why I have been screaming into the void about regulatory overreach since Tornado Cash. When the state can declare a fund's internal redemption mechanism abusive and reach back in time to reclassify transactions, it is exercising a power of retroactive narrative control that is structurally identical to the power it asserted when it sanctioned a smart contract. In both cases the state is not regulating conduct. It is regulating the after-the-fact meaning of conduct. I opposed that power when it was aimed at open-source developers. I oppose it now when it is aimed at tax engineers. The fact that the current target is unsympathetic does not make the precedent less dangerous. A regulator that can rewrite the past can define the future, and you do not get to opt out by being compliant in the present.
What the Comment Window Really Is
October 28 is not a deadline in the way the headlines frame it. It is a lever. The comment period is the interval in which the Investment Company Institute — the fund industry's lobbying arm, which the source material confirms has already gone to the Treasury arguing that conversion operations provide diversification and reduce cost — makes its case, and in which the final shape of the rule is still negotiable.
I have watched enough of these cycles to know what a comment period is for. It is not a listening exercise. It is a negotiation with a clock attached. The industry's best outcome is a safe harbor that surgically separates legitimate in-kind redemption from the tax-engineering maneuvers the IRS actually wants to kill. If that safe harbor emerges, the current panic will look, in hindsight, like a buying opportunity — and the funds that were 'at risk' will re-rate on the relief. The industry's worst outcome is a retroactive final rule with no safe harbor, in which case the litigation begins and the uncertainty extends for years.
Both outcomes are live. That is what a comment period means: the rule you are panicking about today is a draft, and drafts are the only moment when the eventual shape is genuinely undetermined. Anyone treating this final guidance as a settled fact is trading a scenario as if it were a price.
The Signals I Am Watching
I do not publish watchlists to look thorough. I publish them because in a bear market, the survival question is always 'which protocol is bleeding,' and to answer it you need to know which gauge to read. Here are the four that matter for this episode.
First, the retroactivity language in the final guidance. If the word 'retroactive' appears in the operative text rather than the preamble, the tail risk activates and the affected funds face restatement. If it disappears between draft and final, the entire risk premium unwinds. Watch the verb, not the noun.
Second, the ICI's fate. If the Treasury partially adopts the industry's safe-harbor framing, the rule softens and the market re-rates upward. If the Treasury ignores it, the industry's option is litigation, which extends uncertainty and suppresses valuations.
Third, structural migration in SEC filings. If funds begin shifting crypto exposure into offshore subsidiaries or converting away from RIC structures, that is the industry voting with its paperwork, and it is a leading indicator of where the compliance cost is landing.
Fourth, redemption mechanics. If affected funds shift from in-kind to cash creation and redemption, tracking error and discount/premium volatility will widen. In a stressed market, that widening is the first place retail holders actually feel the policy, long before any tax consequence materializes.
None of these signals are price signals. That is deliberate. Price is the last thing to know and the first thing to react. Structure is the first thing to know and the last thing to react. Bet on structure.
Takeaway — The Window That Is Actually Closing
The IRS did not come for your bitcoin ETF. The IRS came for a tax-arbitrage architecture that a subset of crypto funds built to keep a privileged status they were never obviously entitled to, and it came with a doctrine broad enough to reach backward in time. The mainstream spot products — the grantor trusts, the ones most people actually own — are structurally outside the blast radius. The exposure sits in the quiet layer of RIC-constrained funds and structure-driven tax engineering that most holders cannot name.
But here is the forward-looking judgment I want to leave you with, and it is the one the headlines buried: the more interesting event is not the enforcement. It is the integration. Every time a tax authority treats a crypto vehicle with the same suspicion it reserves for a stock-conversion shelter, it is quietly admitting that crypto is no longer an exception to the financial order — it is a component of it. The exemption narrative died not from hostility but from acceptance, and the people who bought ETFs expecting to escape the old rules are discovering that they bought a seat inside them. The next question is not whether the IRS softens this rule. The next question is what else, in a system that now reaches backward as readily as forward, you believed was permanent because it was merely recent. Follow the structure. Audit the certainty. The rest is noise dressed as news.