Wasabi Wallet announced on March 13, 2022 that the zkSNACKs coordinator would begin refusing certain unspent transaction outputs, or UTXOs, when users attempted to register them for CoinJoin transactions.
The statement marked a significant boundary for Bitcoin privacy infrastructure. CoinJoin remained a permissionless transaction technique supported by Bitcoin’s ordinary rules, but access to the coordinator operated by zkSNACKs would no longer be neutral with respect to every eligible input. A private service built to facilitate collaborative transactions had asserted the ability to screen participation before a round began.
The announcement did not disclose the screening criteria, identify an analytics provider, specify an implementation time or enumerate affected UTXOs. Its wording was prospective: the coordinator “will start” refusing certain inputs. The defensible March 13 development is therefore the policy announcement, not proof that a particular bitcoin output had already been rejected.
What the coordinator could control
A CoinJoin combines inputs and outputs from multiple participants in one Bitcoin transaction, weakening the common assumption that every input belongs to one owner. Participants retain their private keys and must authorize the transaction that spends their inputs. The technique can make the relationship between participating inputs and outputs more difficult to infer from the public ledger.
Coordination, however, introduces a service layer. Wasabi’s zkSNACKs coordinator organized rounds, accepted registrations and helped participants construct a common transaction. Because inputs had to register with that coordinator, its operator could decline an input before allowing it into a round even though the Bitcoin network itself would regard the UTXO as spendable if accompanied by a valid signature.
That distinction prevents two misleading conclusions. zkSNACKs was not freezing bitcoin on March 13, and it was not changing Bitcoin’s consensus rules. An excluded owner could still spend the UTXO in another valid transaction. The announcement also did not prohibit CoinJoin generally: alternative implementations and coordinators existed, and users could theoretically coordinate collaborative transactions without the zkSNACKs service.
Privacy met service-level gatekeeping
The policy nevertheless mattered because convenient coordination affects whether privacy tools are usable in practice. An open transaction method does not guarantee equal access to a widely used default service. Screening at registration could divide otherwise valid UTXOs into accepted and rejected categories based on an assessment made outside Bitcoin’s consensus system.
Contemporaneous reporting on March 14 attributed the decision to zkSNACKs’ desire to reduce use of its coordinator by hackers and scammers and avoid trouble for the company. That explanation came from a Wasabi developer’s social-media statement, not from a published legal order or detailed compliance policy. No reviewed event-day record established which jurisdiction, regulator, legal demand or voluntary risk standard prompted the change.
The terminology also required care. Reports commonly described the measure as “blacklisting,” but the March 13 announcement said only that certain UTXOs would be refused. It did not publish a list, prove that rejected funds were criminal proceeds or establish an appeals process. Blockchain attribution can depend on transaction-history analysis and address-clustering judgments rather than a legal determination about the current owner of a coin.
What remained unresolved
As of March 13, users did not know how zkSNACKs would select inputs, whether an external vendor would perform screening, how frequently classifications would change or whether a rejected user would receive a reason. The surviving record also does not quantify how many CoinJoin registrations, users or bitcoins would be affected.
On March 14, contemporaneous coverage clarified that the restriction applied to the zkSNACKs coordinator rather than CoinJoin as a Bitcoin transaction pattern. Wasabi founder Ádám Ficsór separately characterized blacklisting as a setback for bitcoin fungibility. Those reactions framed the central unresolved question: whether privacy software remained meaningfully permissionless when its most accessible coordination layer could classify valid coins before admitting them.
No bitcoin price, trading-volume or market-impact claim is attached to the announcement. The verified significance was architectural and institutional: a centralized gateway inside a noncustodial privacy workflow had announced selective access, while the underlying Bitcoin protocol remained unchanged.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.