The Rule That Never Mentioned Lightning

OCTOBER 6, 2026

Original diagram. Definition language from FinCEN's proposed rule, 88 FR 72701 (October 23, 2023), and its withdrawal notice, 91 FR 63513 (October 6, 2026). The Lightning column is the author's own reading.

Alex Stanczyk posted this morning that FinCEN, the Treasury bureau that polices money laundering, had killed its 2023 plan to treat crypto mixers as a "primary money laundering concern." My first question was what that means for Bitcoin, for Lightning, and for the service providers (LSPs) that phone-wallet Lightning leans on. So I went and read the notice, and then the proposal it kills. The first surprise: neither document contains the word "Lightning." I searched. Zero hits in each. The second surprise is that the proposal's definition of "mixing" was written so broadly that, read literally, it brushes against Lightning anyway. A rule that never names you can still describe you.

What Was Actually Withdrawn

The proposal was published October 23, 2023 (the withdrawal notice cites it as 88 FR 72701). It used Section 311 of the USA PATRIOT Act, which lets Treasury declare something a "primary money laundering concern" and then order banks and other regulated financial firms to do extra paperwork about it. Here the paperwork was a report to FinCEN whenever a firm knew, suspected or had reason to suspect that a crypto transaction involved mixing connected to a jurisdiction outside the United States. The report would have carried the amount, the coin, which mixer was used, the customer's wallet address, transaction hashes, dates and IP addresses, and the firm would have had to keep the customer's identity records too.

The notice was filed October 5 and published October 6, 2026, signed by FinCEN Deputy Director Jimmy L. Kirby. FinCEN withdraws both the finding and the proposed rule. The stated reason is plain: "the expansive definition of CVC mixing in the proposed rule could have a chilling effect on legitimate activity and place a large reporting burden on covered financial institutions." (CVC is FinCEN's acronym for convertible virtual currency, which includes bitcoin.) The notice doesn't pretend mixers are harmless. It says "illicit actors continue to use mixers and other tools and methods to hinder law enforcement investigations," and that FinCEN "will continue to monitor activity involving CVC mixers" and "may take appropriate steps in the future."

One small correction to the tweet's framing, because it matters for how much weight to put on it. The line Alex highlights, that "lawful users of digital assets may leverage mixers to enable financial privacy when transacting through public blockchains," is real and it is in the notice. But the notice is quoting the July 2025 report of the President's Working Group on Digital Asset Markets, not announcing a new FinCEN finding. That is still significant: FinCEN is leaning on the White House's own report to retreat. It's just a citation, not a new policy.

Per The Block and TFTC, a second proposal died the same day: a 2020 plan for banks and money services businesses to collect counterparty details on transfers to and from self-hosted wallets, with record-keeping above $3,000 and reporting above $10,000. I read the mixer notice itself, not that one, so treat the second item as press-reported. It matters more for Lightning users than the mixer rule does, and I'll come back to why.

Why a Rule About Mixers Touches Lightning

Start with how the proposal defined its target. "CVC mixing" meant "the facilitation of CVC transactions in a manner that obfuscates the source, destination, or amount involved in one or more transactions, regardless of the type of protocol or service used." A "mixer" was "any person, group, service, code, tool, or function that facilitates CVC mixing." Then came six examples of what that could look like. Here they are, each next to the piece of ordinary Lightning plumbing it brushes against. This is my reading; FinCEN never drew these lines.

Pooling funds from many people. An LSP routes many users' payments through one pool of its own liquidity. Your payment and a stranger's both pass through the same balance.
Code that coordinates a transaction's structure. LSPs batch channel opens for several users into one on-chain transaction, and splicing rewrites a channel's on-chain footprint.
Splitting a payment across independent transactions. Multi-path payments are a standard Lightning feature: one payment, carved into pieces that take different routes.
Single-use wallets and addresses. A Lightning invoice is built to be paid once.
Swapping between types of digital asset. Only if you swap out of bitcoin, for example into a sidechain asset. Ordinary Lightning stays in bitcoin.
User-initiated delays. I can't find a close match.

And the test itself, "obfuscates the source, destination, or amount," is close to a one-line description of what an off-chain payment does to the public blockchain. Lightning payments don't get written to the chain one by one; that is the point of them. So the honest answer to "did the rule cover Lightning?" is that nobody can say, because it didn't say, and the drafting is broad enough that a compliance department could have argued either way. I would be surprised if FinCEN meant to target it. Nothing in the proposal's examples is a Lightning payment, and the services it names are all mixers (Tornado Cash, Blender and the like), the privacy-pool kind. But a compliance officer reading "regardless of the type of protocol or service used" is not reading FinCEN's mind. That uncertainty is the chilling effect the withdrawal cites, and an LSP would have felt it first.

Why LSPs, Specifically

The proposal didn't regulate mixers directly. It regulated the regulated firms that touch them: banks, money services businesses, exchanges. So the practical question for an LSP was never "will FinCEN call me a mixer?" It was "will the bank, exchange or payment processor I depend on decide I look like one?" Three things about LSPs made that a live worry:

They sit in the middle. An LSP opens channels to users and forwards their payments. That's pooled liquidity with many people's flows crossing it, which is what item 1 above describes in the abstract.
Many are not American. The rule keyed on a foreign connection. Phoenix's operator, ACINQ, is a French company, for one. A US exchange with a customer who withdrew to a foreign-run Lightning service might have had a reporting question to answer.
The edges are on-chain and visible. Opening and closing a channel are ordinary Bitcoin transactions. Those are the moments a bank's analytics software could see and flag.

That list describes a risk of over-reading, not a finding that LSPs were covered. The withdrawal removes the cloud that made over-reading attractive. A bank can no longer point to a pending Treasury rule as the reason to decline a Lightning-adjacent customer. It can still decline on its own, which is a business decision and not a regulation.

What the Withdrawal Does Not Touch

Three things are not changed by this notice, and I'd rather say so than let the headline imply otherwise.

Nothing was in force. The 2023 rule was only ever a proposal. No US firm had a mixer-reporting duty that now disappears. What disappears is the possibility that one arrives.
The custody question is separate. Whether an LSP is a "money transmitter" turns mostly on whether it controls users' funds while moving them. FinCEN's 2019 guidance on crypto business models drew that line, and software that never takes custody sits on the favorable side of it. A non-custodial LSP and a custodial wallet with a Lightning front end are different legal animals. This withdrawal doesn't move that line.
The cases that hurt privacy developers weren't Section 311. As I understand them, the prosecutions of mixer builders, Tornado Cash and Samourai among them, were criminal cases under the unlicensed-money-transmitting statute, a different law from the one withdrawn here. I covered the open questions in the shielded-Bitcoin piece. A friendlier regulator doesn't erase them.

The self-hosted wallet proposal is where the practical stakes were larger for ordinary Lightning users. Most people reach Lightning through an exchange withdrawal to a self-custody wallet. A rule that made that step collect names and addresses above $3,000 would have hit that on-ramp directly, mixer or no mixer. With it withdrawn, that on-ramp stays as it is.

What I Take From It

This is a retreat on one tool, announced with unusually friendly language, by an agency that kept the right to come back. The 2025 report FinCEN cites supports lawful users transacting privately on a public blockchain. A future administration can read it differently, and a rulemaking is cheaper to restart than to finish. So I'd read this as lowering the temperature, not as settling the question. For Bitcoin's privacy tools, the best thing the notice does is put "lawful users" and "financial privacy" into the same sentence in the Federal Register. For Lightning, it removes a rule that never mentioned it and might have caught it anyway.

Where I Could Be Wrong

The Lightning mapping is mine. FinCEN never said any of these six tests describe Lightning, and the proposal's examples are all mixers. I'm showing where the wording could be stretched, not where it was aimed. A lawyer who works on this could well say the stretch is a long one.
I read the mixer notice and the original proposal, not the self-hosted wallet withdrawal. The $3,000 and $10,000 figures and the same-day timing come from press coverage (The Block, TFTC), and the 2020 proposal itself I only know from those reports.
I haven't re-verified the current status of the Tornado Cash and Samourai cases. I'm describing what kind of case they were, not where they stand today.
My point about LSP jurisdictions is an illustration. I named one operator I know is French. I haven't surveyed where LSPs are incorporated, and many serve US users through other arrangements.
I'm not a lawyer, and I hold bitcoin. I'd like Bitcoin and Lightning to stay private and legal, which is a bias worth naming. None of this is legal or investment advice.