FinCEN has withdrawn two separate digital-asset proposals: a 2020 proposal concerning certain wallet transactions and a 2023 proposal concerning international convertible virtual currency (CVC) mixing. For banks, money services businesses and digital-asset compliance teams, the immediate task is to update the status of these proposals without treating their withdrawal as permission to remove other controls.
Two withdrawals, two separate records
FinCEN announced the withdrawals on 5 October 2026. The published Federal Register notices date both withdrawals to 6 October 2026. Keep the announcement date and withdrawal date separate in regulatory inventories.
The 2020 wallet proposal would have required banks and MSBs to report, retain records and verify customer identity for certain CVC or legal-tender digital-asset transactions involving unhosted or otherwise covered wallets. Its withdrawal notice identifies the original proposal as 85 FR 83840, published on 23 December 2020, and states that FinCEN will take no further action on that notice of proposed rulemaking. The 2023 mixing proposal concerned international CVC mixing and a proposed special measure under section 311 of the USA PATRIOT Act. It would have imposed reporting and recordkeeping duties on covered financial institutions for specified transactions. The withdrawal covers both the finding and proposed rulemaking published as 88 FR 72701 on 23 October 2023.
These records should remain distinct. A project based on wallet-counterparty requirements is different from a project based on a mixing-related special measure, even if both appear in the same digital-asset programme.
Withdrawal does not remove the rest of the framework
The notices withdraw proposed measures; they do not repeal a final rule created by either proposal. No implementation deadline should be inferred for requirements that will not proceed through these withdrawn notices. The mixing notice also says that FinCEN will continue monitoring mixers for illicit finance activity and may take further action. It does not give a general assurance that mixing activity is lawful or free of financial-crime risk.
Separate AML and sanctions requirements remain relevant. For example, 31 CFR 1022.210 requires MSBs to maintain an effective, risk-appropriate AML programme, with applicable identification, reporting and recordkeeping controls. OFAC's virtual-currency guidance explains that sanctions obligations apply to virtual-currency transactions as well as fiat-currency transactions. Those are separate sources of responsibility. Which requirements apply to an individual business depends on its activities and circumstances; the withdrawals are not a substitute for that assessment.
AnyAccount's practitioner view: review the basis of each control
A useful response starts with the regulatory record and follows the proposal into implementation plans. The following questions are a suggested change-management approach, rather than additional requirements imposed by the withdrawal notices.
Update the inventory
Record each proposal as withdrawn, retain its original citation and link the relevant withdrawal notice. Check whether board reports, horizon-scanning dashboards or project trackers still show it as pending. Give each record an owner. A status change is easier to audit when someone is responsible for checking the evidence and updating related work.
Trace policies and procedures
Identify draft wording, proposed data fields and verification steps introduced in anticipation of either measure. Ask whether each item also supports an existing obligation, a documented risk assessment or an operational need. A withdrawn proposal may justify closing an anticipated implementation task. It does not, by itself, justify removing a control with a separate basis. Document the distinction before changing policy language.
Keep a clear decision trail
Preserve the source documents, affected project references, decision rationale and responsible owners. Where a proposed change affects controls, involve the appropriate legal, compliance, operations and technology teams. This creates a record of why a project was closed or amended and why other controls were retained. It also gives future reviewers a starting point if FinCEN publishes another measure on the same subject.
The practical takeaway
Keep the two withdrawn proposals separate, record 5 October as the announcement date and 6 October 2026 as the withdrawal date, and review the assumptions attached to each project. The priority is accurate regulatory change management. Any firm-specific decision to alter controls requires a separate assessment of applicable obligations and risk. This article provides general regulatory and operational commentary, not personalised legal advice.