I was halfway through a cold coffee when the notice landed, and my first reaction was not celebration. It was a quiet, slightly suspicious relief. Two proposals that had sat in the regulatory drawer for years, one from late 2020 and one from 2023, were being pulled. Banks would not, after all, be told to build a fresh reporting machine around self-custody wallets and mixing. If you have ever tried to explain a hardware wallet to a compliance officer who still thinks of cash as the suspicious asset, you know why that sentence matters.
The bureau that enforces the Bank Secrecy Act filed two withdrawal notices on October 5, with formal publication set for the following day. One notice walks away from the wallet rule. The other withdraws both a mixing proposal and the underlying finding that international convertible virtual currency mixing was a class of transactions of primary money laundering concern. Same signature on both documents. Same broader policy backdrop: a push to make digital-asset rules fit the activity they actually touch.
What The Treasury Actually Withdrew
Strip the legal phrasing and the move is simpler than it looks. The financial-crimes bureau said it would take no further action on the wallet proposal. Separately, it withdrew the mixing package in full, finding and all. That second part is easy to miss. Dropping a proposed form is one thing. Dropping the official label that justified the form is another.
Deputy Director Jimmy L. Kirby signed both filings. They were placed on public inspection on October 5. In the wallet notice, the bureau pointed to an administration effort to keep digital-asset regulation fit-for-purpose. Both documents also leaned on a July 2025 report from the President’s Working Group on Digital Asset Markets. I have read enough of these cross-references to know they are doing real work here. Agencies rarely abandon a multi-year proposal without a political and policy hook they can cite in the Federal Register.
None of this erases the Bank Secrecy Act. Banks, money services businesses, and other covered firms still file suspicious activity reports. They still keep records. They still know their customers. What changed is a pair of drafts that would have stretched those duties into places the industry, and a fair number of civil-liberties lawyers, argued the statute was never meant to reach so bluntly.
The 2020 Wallet Proposal, In Plain English
The December 2020 draft would have required banks and money services businesses to collect information on certain crypto transfers involving wallets held outside regulated institutions. Think of a customer moving value from an exchange account into a wallet they control themselves, or the reverse. Under the draft, the institution on the regulated side would have had new homework.
Two thresholds did most of the lifting. Above $3,000, the firm would have kept transaction and counterparty records and verified its own customer’s identity on a covered transfer. Above $10,000, it would also have filed a report. Aggregation mattered too. Several movements that added up to more than $10,000 inside 24 hours could trip the reporting line. Deposits, withdrawals, exchanges, payments, and other transfers were all in the frame.
The draft did not stop at self-custody. It also reached wallets at foreign financial institutions sitting outside the Bank Secrecy Act framework, in jurisdictions the bureau had identified. When the department floated the idea in December 2020, it framed the gaps as an anti-money-laundering problem. The pitch was extra records so investigators could see who sat on the other side of a transfer that left the regulated perimeter.
A recordkeeping rule that quietly turns every counterparty into a data subject is not a small compliance tweak. It is a change in who gets watched.
Privacy advocates objected on a point that still feels under-discussed. The information collected would not only describe the bank’s own customer. It could describe the person on the other end, someone who never opened an account, never agreed to the bank’s privacy notice, and might simply have sent or received a payment. That is a long way from classic cash reporting at a teller window.
The 2023 Mixing Designation
The mixing package used a different legal tool. Section 311 of the USA PATRIOT Act lets the Treasury impose special measures when it finds a foreign money-laundering risk. In October 2023 the bureau found that international convertible virtual currency mixing was a class of transactions of primary money laundering concern, and it attached a proposed reporting measure to that finding.
Covered institutions would have reported a transaction when they knew, suspected, or had reason to suspect that foreign mixing was involved. The definition did not stop at brand-name mixing services. The draft swept in pooling funds, splitting transfers, single-use wallets, exchanging one digital asset for another, and delaying a transaction, whenever those steps obscured source, destination, or amount.
Read that list again. A lot of ordinary blockchain behavior looks like that list. People split a payment. They use a fresh address. They swap tokens. They wait. On a public ledger, privacy is often a stack of small habits, not a single button labeled “mix.” A definition that wide was always going to collide with lawful use. The withdrawal notice essentially admits the collision.
Why The Agency Changed Course
The mixing withdrawal is the more revealing of the two documents, because the bureau had to explain itself. Commenters warned that the definition could chill legitimate activity and pile on reporting costs. The notice also cited the White House working group’s recognition that lawful users may use mixers to protect privacy on public blockchains. That sentence would have been hard to imagine in the original announcement.
The bureau did not pretend criminals had discovered ethics. It said mixing tools are still used to obstruct investigations. It said it would keep watching for money laundering, terrorist financing, and other illicit finance, and that it could act again when the facts support it. So this is a retreat from a particular instrument, not a promise of permanent silence.
Perhaps the most interesting aspect is the split tone. One paragraph nods to privacy and cost. The next keeps the enforcement door ajar. Anyone building a compliance program should read both paragraphs, not just the headline.
How The Two Drafts Compared
I keep a simple table in my notes for proposals like these, because the thresholds and the legal hooks get mashed together in social posts. Here is the version I would actually hand a colleague.
| Draft | Year | Core trigger | What firms would have done |
| Wallet reporting and recordkeeping | 2020 | Covered transfer involving an unhosted or certain foreign wallet | Records and identity checks above $3,000; a report above $10,000, including 24-hour aggregation |
| Mixing special measure | 2023 | Knowledge, suspicion, or reason to suspect foreign mixing | Extra reporting and records tied to a Section 311 finding on international mixing |
| Status after October 2026 | 2026 | Neither proposal moves forward | Existing Bank Secrecy Act duties remain; these two expansions do not |
Notice what the table does not say. It does not say exchanges can ignore sanctions. It does not say a mixer operator is suddenly a licensed bank. It says two proposed expansions are off the table.
The Privacy Argument That Stuck
Coin Center called the withdrawals a major win for financial privacy in an October 5 post by Jason Somensatto. The group had opposed both proposals in comments and in public advocacy. On the wallet draft, its core American-user objection was personal data. Banks or crypto service providers would have collected details about counterparties who were not their customers.
On mixing, the earlier challenge, reported in January 2024, went after scope, the treatment of domestic transactions, and the spillover onto lawful users. The practical fear was almost bureaucratic. If a compliance team cannot confidently say a transaction is foreign, the safe move is to report activity that happened entirely inside the United States. Over-reporting is how wide definitions become domestic surveillance by accident.
The group also questioned whether the proposal stayed inside Section 311’s limits on transaction classes tied to foreign jurisdictions. It raised due-process concerns about labeling lawful activity a money-laundering concern without individual notice or a hearing. I am not a constitutional lawyer, but that second point has always struck me as the one regulators underestimate. A class finding feels abstract until it lands on a product people use for payroll, donations, or simply not publishing their salary on a public ledger.
Difficulty identifying where a transaction “is” can push cautious institutions to report activity conducted entirely at home.
Privacy advocates, summarizing their mixing objection
A Parallel Fight Over Software And Control
The wallet and mixer drafts were not the only pressure point. In May 2024, Senators Cynthia Lummis and Ron Wyden wrote to then-Attorney General Merrick Garland about money-transmitter interpretations aimed at noncustodial software. Their letter argued that a service needed control over customer assets to qualify as a money transmitter under the provision they cited. Wyden also warned that holding software developers responsible for users’ alleged crimes could raise First Amendment concerns.
That letter is not the withdrawal. It is context. For several years, the policy argument around crypto privacy tools has had two tracks. One track is reporting by banks. The other is criminal or licensing exposure for people who write software they do not custody. Pulling the FinCEN proposals eases the first track. It does not, by itself, settle the second.
In my experience, founders hear those tracks as one threat. A compliance officer hears them as separate memos. Both are right, which is why the October filings feel larger than their page count.
What Still Sits On The Books
A withdrawal is not a repeal of the statute underneath it. Covered financial institutions still live inside a reporting culture built for cash, wires, and, more recently, digital-asset firms that already file at scale. If you want a sense of that scale, look at the bureau’s own scam analysis published in early September.
That review identified suspicious scam activity totaling about $12.7 billion across 33,904 Bank Secrecy Act reports filed between September 2023 and December 2025. Roughly 1,300 financial institutions submitted them. Money services businesses, mostly digital-asset firms, filed 55 percent and identified $5.5 billion in suspicious activity. Banks reported another $6.4 billion.
The bureau was careful. The aggregate is not a direct measure of victim losses. Reports can include attempted transfers, duplicate filings, and errors. Even with that caveat, the geography is blunt: victims in all 50 states and several U.S. territories. Some funded fraudulent investments with retirement savings, home equity, mortgages, and personal loans. Since 2015, the Rapid Response Program has recovered just over $1 billion for 5,790 U.S. victims.
I mention those figures because the political counterargument writes itself. If scam reports are already this thick, why loosen anything? The fair answer is that these two proposals were not the tool that produced those reports. The reports came from the existing system. Killing a bad expansion is not the same as switching off the radar.
- Existing suspicious-activity reporting stays in place.
- Sanctions screening and customer due diligence stay in place.
- The $3,000 and $10,000 wallet thresholds from the 2020 draft do not become law through these notices.
- The 2023 mixing class finding is withdrawn, not paused.
- The bureau reserved the right to act again on illicit finance.
Who Feels This On Monday Morning
Compliance teams at exchanges and banks are the first practical audience. Many of them had already sketched workflows for the wallet thresholds, even while the proposal gathered dust. Vendor decks promised counterparty-wallet collection. Policy manuals had placeholder sections. Those placeholders can come out. The budget attached to them can be argued over, which is a different meeting.
Self-custody users feel it more indirectly. Nothing in the withdrawal hands them a new legal shield. It removes a proposed duty on the institution sitting across the transfer. That is still meaningful. A rule that forces your exchange to harvest the name behind every external address changes how comfortable you are using that exchange at all.
Mixer developers and privacy-protocol teams get a narrower kind of relief. The class finding that treated international mixing as a primary money-laundering concern is gone. A class finding is a heavy label. Losing it matters in court, in banking relationships, and in the way payment partners talk about risk. It does not mean every privacy tool is blessed. Fraud, sanctions evasion, and unlicensed money transmission remain separate questions.
Law enforcement is the constituency that loses a tool it had not fully received. Investigators wanted more structured data on unhosted flows and on mixing. They will keep using subpoenas, blockchain analytics, existing reports, and international cooperation. Some of them will say the public just made their job harder. Some of that complaint is fair. Some of it assumes the drafts would have produced clean data rather than a flood of defensive filings.
The Cost Argument Was Not Cosmetic
People outside compliance tend to treat “burden” as a lobbyist word. Sometimes it is. Here, the operational picture was specific. A $3,000 recordkeeping line on external-wallet transfers means identifying a counterparty who may not want to be identified, storing that data, securing it, and producing it later. A $10,000 report, with a 24-hour aggregation rule, means monitoring systems that can see across products, not just inside one account view.
The mixing draft was messier. “Reason to suspect” is a compliance phrase with a long life in suspicious-activity work. Applied to a definition that included splitting, single-use addresses, and delays, it risked turning normal settlement patterns into reportable events. Every false positive is a form, a reviewer, and a customer who may never know they were filed on.
I’ve found that rules fail in the gap between the example in the preamble and the queue on a Tuesday night. The preamble imagines a cartel cash-out. The queue is a freelancer paid in stablecoins who hops addresses because a blog told them to. Write the rule for the cartel and you still process the freelancer.
Public Blockchains And The Privacy Paradox
Here is the tension the working-group report finally said out loud. Most major chains are public by default. Balances, counterparties, and timing sit in a database anyone can query. That transparency is a gift to investigators and a problem for everyone else. A salary paid on-chain is a salary published. A medical payment, a political donation, a remittance to family: same issue.
Mixing, coinjoin-style coordination, shielded pools, and fresh addresses are attempts to put a curtain on a street that was built without one. Some of those attempts are abused. Some are the only reason a dissident, a domestic-violence survivor, or a ordinary person with a nosy neighbor can use the network at all. Treating the entire category as inherently suspect was always going to be a blunt instrument.
Does that mean every mixer is a public good? No. A service that markets itself to ransomware crews is not a privacy start-up with bad branding. The withdrawal leaves room to go after specific actors. What it refuses is the idea that the technique itself, defined broadly enough to cover half of normal wallet hygiene, should trigger a special measure.
A workable line, roughly: Specific illicit service -> investigate and charge Broad technique on a public chain -> do not label the class Bank seeing clear red flags -> file under existing duties
Fit-For-Purpose Is A Standard, Not A Slogan
The wallet notice borrows the administration’s language about rules that fit the activity. Fine. Slogans are cheap. The useful test is whether a requirement maps to a risk the firm can actually see, at a cost that does not swamp the smaller risk it misses.
Unhosted wallets are not invisible. They are unintermediated. The person who holds the keys is not a money services business by default. Asking a bank to reconstruct that person’s identity from an address, a memo field, or a screenshot is how you get bad data with a legal stamp on it. Fit-for-purpose, if the phrase means anything, means refusing data collection that looks complete and is not.
The July 2025 working-group report is doing a lot of silent labor in these notices. Agencies cite it because it gives them cover to prefer narrower tools. Whether later rulemakings follow that preference is the real test. A withdrawal can be a pivot or a pause. The documents read like a pivot. I would still watch the next proposal before I bet the farm.
What Banks Should Do This Week
If I were sitting in a compliance chair, I would not throw a party and delete the folder. I would do a short, slightly boring cleanup.
- Mark the 2020 wallet draft and the 2023 mixing package as withdrawn in the regulatory tracker, with the October 5 inspection date and the October 6 publication date.
- Tell product and vendor teams that counterparty-wallet collection built only for those drafts is no longer on the mandatory roadmap.
- Leave sanctions, fraud, and suspicious-activity procedures untouched until someone shows a concrete conflict.
- Brief the board in one page: what died, what did not, and the bureau’s line that further action remains possible.
- Keep the comment file. The objections that landed will matter if a narrower proposal returns.
That last step is the one teams skip. Regulatory memory inside a company is usually a shared drive and two people who might leave. The arguments that worked, scope, domestic spillover, cost, lawful privacy use, are worth keeping in a form a new counsel can read.
What Users Should Not Assume
A few assumptions are already floating around, and most of them are too neat.
First, this is not a statute saying self-custody is exempt from every financial law. Taxes still exist. Sanctions still exist. A court order still exists. The withdrawal stops a proposed reporting overlay. It does not mint a new right.
Second, exchanges can still ask questions. A platform’s own terms, its banking partners, and its risk models did not vanish at 6 p.m. on October 5. Some firms will keep collecting external-wallet information because their bank told them to, not because FinCEN’s 2020 draft survived. Partner pressure is a shadow rulebook. It is slower to withdraw.
Third, privacy tools remain a legal patchwork. State money-transmitter theories, federal criminal statutes, and sanctions programs do not read the Federal Register and update themselves. Anyone building in that space still needs a lawyer who is bored by headlines.
The Thresholds That Almost Became Muscle Memory
$3,000 and $10,000 were clever numbers. They echo older currency rules, so they sound familiar in a congressional hearing. Familiar is not the same as fitting. Cash at a branch is a face, an ID, and a drawer. A wallet transfer is an address and a signature. Importing the cash thresholds without importing the cash context was the original sin of the 2020 draft.
Aggregation inside 24 hours made it stricter than the headline. A person moving $4,000 three times in a day would have crossed the reporting line even if no single transfer did. That design fights structuring, which is a real behavior. It also catches freelancers, market makers, and anyone who simply does not batch payments. The bureau never had to defend that tradeoff in a final rule. Now it does not get to impose the tradeoff either.
Foreign wallets outside the Bank Secrecy Act perimeter were the other expansion. The draft tried to follow value when it left the U.S. regulatory map. Cross-border evasion is not imaginary. The method, though, asked U.S. firms to voucher for institutions and users they do not supervise. That is a hard job to do well and an easy job to do badly.
Section 311 After This Retreat
Section 311 is a serious authority. It has been used against banks and jurisdictions where the foreign nexus was concrete. Using it against a technique, defined to include pooling, splitting, single-use wallets, asset exchange, and delay, stretched the idea of a “class of transactions” until the class looked like the network.
Withdrawing the finding matters more than withdrawing the form. A finding can outlive the measure attached to it. It can be cited in later talks with foreign counterparts, in bank de-risking memos, in speeches. Taking the finding off the table is the part privacy lawyers will quote. Taking the form off the table is the part operations teams will feel.
Could a future bureau write a narrower 311 action against a named foreign service with a documented laundering role? The October notice almost invites that reading. It says monitoring continues and further action is possible when appropriate. A scalpel remains available. The net is what got folded.
Politics, Timing, And The Working Group
The notices sit inside a wider shift. The administration has spent the past year telling agencies that digital-asset rules should match use, not fear. The working-group report from July 2025 is the document they keep pointing at. Citing it twice, once in each withdrawal, is a way of saying this is not a lone bureau going soft. It is an executive-branch line.
Timing is its own message. Filing on October 5 for publication on October 6 is routine Federal Register mechanics, but the choice to clear both proposals together is not. Wallet rules and mixer rules attract different critics. Bundling the withdrawals makes the story one story: proposed expansions of crypto surveillance are being cut, while baseline anti-money-laundering duties stay.
I do not think that framing will satisfy either pole. Privacy advocates wanted a clearer statutory line, not just two dead dockets. Enforcement hawks wanted the data. The middle, which is where most banks live, gets a year of not building a system nobody could quite specify.
Scams, Losses, And The Wrong Moral
It would be dishonest to celebrate the withdrawals and ignore the scam file. Tens of thousands of reports. Billions flagged. Victims using home equity and retirement accounts. A recovery program that has returned a bit over a billion dollars since 2015, which is real money and still a fraction of the harm described.
The wrong moral is that wallet reporting would have stopped those scams. Many of the flows in investment-fraud cases already touch a regulated on-ramp or off-ramp, which is why the reports exist. The gap is often speed, mules, and platforms that look legitimate until they do not. A counterparty form on an unhosted address does not rewind a wire the victim authorized.
The better moral is narrower. Keep the reporting that already surfaces patterns. Improve recovery. Be suspicious of proposals that collect more identity than they can use. Those are compatible goals, even if they do not fit in a single headline.
How Comment Letters Actually Moved This
Rulemaking lore says comment letters are theater. Sometimes they are. Here, the withdrawal notice describes commenter concerns almost in the commenters’ own shape: lawful activity discouraged, reporting costs substantial, privacy uses recognized by the working group. That is what it looks like when a docket changes a draft’s fate.
Coin Center’s record is part of that docket, not the whole of it. Exchanges, banks, developers, and individual users filed too. The domestic-spillover point is the one I would steal if I were writing the next comment. If your definition forces a U.S. bank to guess whether a hop was foreign, you have written a domestic rule with a foreign label. Agencies notice that argument because it is statutory, not just rhetorical.
Due process was the quieter point. A class designation can brand a practice without ever notifying the person using it. For a tool used by thousands of lawful parties, that is a strange fit. You can still prosecute the party who launders. You do not need to deputize the practice first.
A Practical Reading For Founders
Founders will ask whether they can ship a privacy feature on Monday. The adult answer is: you could have shipped a lawful privacy feature last Monday, and you still cannot ship a service whose business model is concealing crime. The withdrawal changes the temperature. It does not rewrite the criminal code.
Banking access may ease at the margin. De-risking memos loved to cite the 2023 finding. A withdrawn finding is a worse citation. Relationship managers will not all update their templates this week. Some will. If you are the person on those calls, bring the notice, not a thread.
Product copy should calm down too. “Fully anonymous” was a bad phrase before October and it is a bad phrase after. Public chains leak. Privacy tools reduce leaks. They do not grant invisibility, and marketing that pretends otherwise is how you attract the exact customers who make your banking partner nervous.
What A Better Rule Would Have Looked Like
Imagine the bureau had wanted data without drafting a net. A better wallet proposal would have stayed with institutions that already know both sides, or with transfers where the customer voluntarily identifies a counterparty as part of a regulated service. It would have skipped the fantasy that an exchange can reliably name the human behind an address they do not custody.
A better mixing action would have named services, documented foreign control, and defined the transactions by those services rather than by techniques everyone uses. Suspicion would have required more than “this address looks fresh.” Fresh addresses are hygiene. They are also, sometimes, a clue. The job of a rule is to tell a reviewer which is which without making the clue the violation.
Maybe that narrower version comes back. The notice leaves the lane open. If it does, the comment file from 2020 and 2023 is a head start, not a trophy.
International Spillover
U.S. proposals travel. Other finance ministries watch what the Treasury almost does. A final wallet-reporting rule would have been cited in capitals that want a template. A withdrawal travels too, though more quietly. It tells foreign regulators that the most watched anti-money-laundering bureau looked at unhosted-wallet collection and foreign-mixing class findings and stepped back.
That will not stop regimes that want the data anyway. It removes a convenient American precedent. For global exchanges, precedent is not academic. It shows up in licensing questionnaires: “Does your home regulator require counterparty collection on unhosted transfers?” The honest answer, after publication, is that a proposal existed and was withdrawn.
Standards bodies and bank-to-bank messaging groups have their own travel-rule debates. Those are not these notices. Still, compliance culture rhymes. When the U.S. draft looked aggressive, vendor standards drifted toward collecting more. When the draft dies, the drift can slow. It rarely reverses overnight.
Language Worth Watching In The Notices
A few phrases deserve a highlighter.
No further action on the wallet rule is cleaner than a delay. Delays come back. “No further action” means this docket is done unless someone opens a new one.
Fit-for-purpose is the political standard they want quoted. It is vague enough to justify almost anything later, which is why industry should pin it to examples: no counterparty harvesting from unhosted addresses, no technique-based class findings that swallow ordinary use.
The mixing notice’s nod to lawful privacy on public blockchains is the sentence advocates will frame. The following assurance that criminals still use mixing tools, and that monitoring continues, is the sentence investigators will frame. Both are in the same document on purpose.
Withdrawal ≠ amnesty
Existing reports stay
New wallet thresholds do not start
Mixing class finding is withdrawn
Further action remains possibleA Note On Tone In Coverage
Some write-ups will call this a rollback of oversight. That flatters the drafts. They were proposals. They never became the daily rule. Calling a withdrawn proposal a repeal confuses readers who think a live duty just disappeared. It did not.
Others will call it the end of crypto surveillance. That flatters the advocates. The Bank Secrecy Act did not close for the afternoon. Digital-asset firms already file a majority share of the scam reports in the bureau’s own review. Surveillance, if that is the word you want, has a working channel. These notices close two proposed side channels.
The accurate line is duller and better. Two expansions died. The base regime did not. Privacy gained ground on public-chain tools without a promise that crime will be ignored.
Questions The Next Proposal Has To Answer
If the bureau returns to this ground, I want five answers before I take the draft seriously.
- Can the firm actually know the fact you are asking it to report, or are you asking it to guess?
- Does the definition capture domestic activity while claiming a foreign hook?
- What does a lawful user do that will not look like the prohibited pattern?
- What is the false-positive cost per useful lead, not per filing?
- Why will existing suspicious-activity reports not already catch the case you are describing?
Those questions are not hostile to enforcement. They are how you avoid building a cathedral of forms that investigators never open. The scam review itself warned that aggregates mix attempts, duplicates, and errors. More raw filings are not automatically more signal.
The Human Side Of A Public Ledger
I keep coming back to a small scene that never makes the legal summary. Someone gets paid, moves the funds to a wallet they control, and does not want their landlord, their ex, or a data broker reconstructing the month. That person is not a typology in a preamble. The 2020 draft would have pressed their exchange to write down the other side. The 2023 draft might have treated their address hygiene as a clue worth a form.
Financial privacy is an old idea wearing new tooling. Cash had it. Bank secrecy laws traded some of it for traceability after real abuses. Crypto reopened the argument because the default setting flipped to public. The October withdrawals do not settle the philosophy. They do say the first drafts overreached.
Perhaps that is the adult outcome. Not a victory lap. A correction.
What I Would Tell A Skeptical Friend
If a friend asked over dinner whether this means the government “legalized mixers,” I would say no, and I would say it before the bread arrived. I would say the Treasury dropped a proposal that treated a wide set of mixing-like behaviors, including foreign mixing it defined very broadly, as a class of primary money-laundering concern. I would say a separate proposal forcing banks to record and sometimes report unhosted-wallet transfers at $3,000 and $10,000 is also dead. I would say criminals did not get a holiday, and neither did banks.
If they asked whether I trust the privacy cheerleading, I would say partly. The domestic-spillover critique was concrete. The cost critique was concrete. The working group’s own language on lawful mixer use gave the bureau a place to land. That is a better foundation than a meme. I would still want to see whether banking partners loosen up, because shadow rules outlast Federal Register notices.
And if they asked whether investigators should be angry, I would say they can be disappointed without being owed those particular drafts. Disappointment is not a legal theory. A subpoena is. A suspicious activity report is. A named action against a service that actually moves illicit funds is. Those tools were here before December 2020. They are here now.
The Bottom Line For Markets And Policy
Markets do not usually reprice on a FinCEN withdrawal, and they should not treat this like an ETF decision. The effect is structural and slow. Less mandated counterparty collection. One less class finding for de-risking memos to cite. A clearer signal that the current policy center wants digital-asset rules tied to real intermediation, not to the mere existence of a public address.
Policy people should archive the notices next to the 2020 and 2023 drafts and read them as a pair. The story is the distance between what was proposed and what survived contact with comments, costs, and a working-group report that admitted lawful privacy use. That distance is the news.
For anyone who holds their own keys, the practical change is the dog that will not bark. Your exchange is less likely to be forced, by these particular rules, to turn an outgoing transfer into a mini investigation. Other pressures remain. They are just no longer wearing these two docket numbers.
The useful outcome is not that oversight vanished. It is that two overbroad drafts did not become the way oversight works.
I started the day suspicious of my own relief. I am ending it in the same place, which feels about right. Relief is warranted. Amnesia is not. The bureau said it will keep watching, and the scam figures explain why that line is in the notice. The win, if you need a win, is narrower and sturdier than the posts will claim: self-custody transfers and mixing techniques were not folded into a new reporting machine. Not this time.
Hold onto the thresholds, the dates, and the distinction between a withdrawn finding and a living statute. Those details age better than the victory lap. And if a slimmer proposal returns, you will want them close, coffee optional, suspicion intact.
