Decoding Onchain Privacy
Key Insights
- Privacy is becoming modular and programmable, with middleware like Railgun and chains like Aztec enabling integrated and application-layer confidentiality across existing networks.
- Regulatory pressure remains a key obstacle to onchain privacy, with privacy coins and mixers subject to sustained scrutiny and policy action.
- Composability remains a core technical challenge, as privacy-focused blockchains often sacrifice interoperability, developer tooling, and UX in exchange for privacy.
- Mainstream blockchains are embedding privacy at the base layer with Vitalik’s privacy roadmap on Ethereum and Solana’s Confidential Token Extensions.
A Brief History of Onchain Privacy
Blockchains promised transparency, but in a world where wallets function as identities and every transaction broadcasts intent, full visibility comes at a cost. As crypto matures, privacy has become a structural dilemma. Compliant, default privacy is no longer optional. It is essential infrastructure for the next wave of adoption. To see how privacy reached today’s point, let’s revisit where it started.
Foundational Era (2009-2013)
The first era of crypto privacy was shaped by uneven understandings of Bitcoin’s pseudonymity. While technically literate users understood the transparency of Bitcoin’s ledger, others mistakenly believed that unlinked addresses guaranteed anonymity. During this period, privacy and transactional freedom were central values among many users within the emerging crypto community. This period saw a renaissance of cypherpunk values, with cryptocurrency offering a lifeline to individuals living under oppressive regimes.
However, cryptocurrency's pseudonymous nature also attracted some individuals engaging in illicit activities. Users tested Bitcoin’s privacy limits through Darknet platforms like Silk Road. Early custodial mixers such as Bitcoin Fog and obfuscation tools like CoinJoin emerged to attempt to solve Bitcoin’s lack of native privacy.
The 2013 takedown of Silk Road, amid growing regulatory pressure and mounting illicit activity, marked a turning point. It catalyzed broader regulatory scrutiny and demonstrated the viability of blockchain forensics, paving the way for companies like Chainalysis and Elliptic to commercialize the opportunity.
Privacy Coin Expansion (2014-2018)
As blockchain analysis techniques increasingly exposed Bitcoin’s privacy limitations, a new generation of privacy-focused cryptocurrencies emerged as alternatives. Coins like Dash (DASH), Monero (XMR), Zcash (ZEC), and Verge (XVG) were launched with varying approaches to enhancing user anonymity.
Monero, launched in April 2014, quickly gained adoption among privacy-conscious users and early darknet markets. Built on the CryptoNote protocol first implemented by Bytecoin, Monero enhanced its predecessor’s design and enabled default privacy. It used ring signatures and stealth addresses to obscure sender and recipient identities, and later introduced confidential transactions to conceal amounts.
In 2016, Zcash introduced the first onchain implementation of zk-SNARKs. Zcash enabled optional privacy through shielded transactions, in which the sender, receiver, and transaction amount were hidden from the public ledger but remained cryptographically verifiable by the network. This represented a major advancement in the cryptographic foundations of privacy-preserving digital assets.
Monero, Zcash, and other privacy-focused cryptocurrencies continued to evolve with ongoing technical improvements. However, they also attracted increasing regulatory scrutiny. In 2018, Japan’s Financial Services Agency became the first major regulator to prohibit registered exchanges from listing Monero, Zcash, and Dash due to concerns over their potential use in money laundering. This marked the beginning of a broader trend of exchange delistings and policy pushback against privacy coins.
Rise of Programmable Privacy (2019-2022)
While privacy coins would continue to develop, privacy developments would begin to accelerate and expand toward Layer-2 (L2) rollups and smart contract-based privacy. As Ethereum and DeFi gained in adoption, developers within the ecosystem explored zero-knowledge proofs (ZKPs) not only for privacy but also as a tool for scalability and security. The viability of this application of the technology was demonstrated in 2019 when Loopring launched as the first ZK Rollup on Ethereum.
Tornado Cash emerged as the first non-custodial, zk-SNARK–based mixer on Ethereum. It enabled users to anonymize ETH and ERC-20 transactions by breaking onchain links between sender and recipient, and used smart contracts to eliminate reliance on third parties. In 2020, Secret Network launched as the first smart contract platform with built-in privacy, using trusted execution environments (TEEs) to support private computation.
​​In 2021, Aztec launched zk.money, the first privacy-focused ZK-rollup for Ethereum, which later introduced programmable privacy for smart contracts. Although the network was eventually sunset, Aztec contributed significantly to the privacy ecosystem by developing the PLONK proving system and introducing the Noir programming language.
As technical innovation progressed, regulatory pressure intensified. The 2019 introduction of the FATF Travel Rule imposed new compliance burdens on crypto transactions that constrained the potential for onchain anonymity. Delistings of privacy coins on centralized exchanges accelerated. The crackdown on mixers escalated further, culminating in 2022 when the U.S. Treasury’s OFAC sanctioned Tornado Cash. This was followed by the arrest of two of its developers, which highlighted the growing tension between privacy innovation and regulatory enforcement.
Pragmatic Privacy Era (2023-Present)
Today, onchain privacy solutions are increasingly incorporating features to address regulatory requirements. These solutions are programmable and increasingly modular, enabling integration not just at the protocol level but across the stack in DeFi, identity systems, and crosschain infrastructure. ZKPs have become a cornerstone of onchain privacy.
At the same time, continued regulatory pressure is accelerating interest in selective disclosure tools. New primitives for selective disclosure, such as zkKYC and zkAML, are emerging that allow users to prove compliance-relevant attributes without revealing their full identity. This is evidenced by solutions like zkMe, zkPass, and Polygon ID. Meanwhile, growing concerns around online bot activity and fake users have led to increased corporate interest in World’s Proof-of-Personhood solution, which verifies that each user is a unique human using iris scans. Despite the privacy tradeoffs, World has secured key partnerships and recently reported over 12 million verified users. These developments indicate a growing shift away from full anonymity toward tools that aim to balance privacy preservation with accountability.
The policy landscape remains fragmented, and surveillance capabilities continue to advance. Onchain privacy architectures today reflect a spectrum of design choices, shaped by varying jurisdictional requirements, institutional interests, and developer priorities. Ongoing regulatory developments like the recent lifting of Tornado Cash sanctions and implementation standards will play a central role in determining how privacy is embedded into blockchain infrastructure going forward.
An Overview of Privacy Sectors
The privacy sector in crypto can be broken down into three main categories: Private Payment Networks, Programmable Privacy Chains, and Privacy Applications/Middleware. Each of these categories employs different design goals and architectural tradeoffs to deliver privacy across the stack, from user-level asset transfers to developer-level support for building privacy-native applications.
Private Payment Networks
Private payment networks are blockchains built to facilitate shielded peer-to-peer (P2P) transfers. They prioritize privacy at the transaction level and generally exclude programmability. This category represents one of the earliest approaches to onchain privacy.
- Monero: Enforces full privacy by default, meaning every transaction automatically hides the sender, recipient, and amount. It uses ring signatures to make it unclear which of several possible accounts actually sent the transaction. Stealth addresses create one-time destination addresses so that the recipient’s identity is not publicly visible. To hide amounts, Monero uses Ring Confidential Transactions (RingCT), a method that lets the network verify the math behind a transaction without revealing how much was sent. Users interact with Monero through a typical wallet interface, but the transaction details are fully hidden onchain.
- Zcash: Offers optional privacy by supporting two types of addresses: transparent and shielded. Transparent addresses work like Bitcoin, where transaction details such as sender, recipient, and amount are publicly visible. In contrast, shielded addresses use zk-SNARKs to hide this information while still allowing the network to verify the transaction is valid. This dual-address model gives users flexibility and can accommodate regulatory needs, but it also means privacy depends on how users and wallets are configured. To learn more about how Monero and Zcash work, refer to this Messari report on Onchain Privacy.
These networks are optimized for digital cash-like transfers. They offer strong guarantees for transactional privacy but are structurally siloed from composable blockchain ecosystems. In practice, usage of private payment networks has been stagnant. Both Monero and Zcash have seen stagnant growth in the past three years. Monero’s monthly transactions have remained stable since mid-2022. Zcash experienced brief spikes in August 2022, which was likely in response to the Tornado Cash sanctions, and again in early 2023, but activity has since declined and remained flat.
Programmable Privacy Chains
Programmable privacy chains bring confidentiality to smart contract execution. Unlike private payment networks, which focus on anonymizing transfers, these chains embed privacy at the smart contract layer. This enables developers to build composable applications that keep data, logic, and state changes hidden from public view.
- Aztec: A privacy-first L2 on Ethereum that launched its public testnet on May 1, 2025. It introduces the Aztec Virtual Machine (AVM), designed for private execution, supporting both user-side private functions and public functions executed onchain. State is split between encrypted UTXOs and a public Merkle tree. By departing from EVM compatibility, Aztec adopts custom tools like the Noir programming language to prioritize privacy over integration with existing Ethereum infrastructure.
- Aleo: A non-EVM Layer-1 (L1) built from the ground up for privacy-preserving computation. It uses ZKPs to verify transactions without exposing inputs or outputs. Developers write programs in Leo, a domain-specific language that compiles into ZK circuits executed by the SnarkVM. Its dual consensus model, Proof-of-Succinct Work(PoSW) for proof generation and AleoBFT for block validation, separates execution from consensus to improve scalability and maintain privacy guarantees.
- Secret Network: A Cosmos-based L1 that launched in 2020 as the first mainnet with private-by-default smart contracts. Contracts written in CosmWasm execute inside Trusted Execution Environments (TEEs), which decrypt and process encrypted user data within secure hardware enclaves. The resulting outputs are re-encrypted before being committed onchain. Users can selectively share data using viewing keys, enabling auditability without forfeiting privacy.
Programmable privacy chains represent a meaningful evolution in onchain privacy. By embedding confidentiality into application logic and user data, they expand the design space for private applications well beyond the capabilities of transactional anonymity alone.
Privacy Applications / Middleware
Privacy applications and middleware are modular tools that bring privacy functionality directly to users on top of existing L1 or L2 networks. Instead of requiring users to migrate to privacy-focused chains, these protocols integrate discreetly into mainstream ecosystems like Ethereum.
For example, Tornado Cash is a decentralized, non-custodial mixer that allows users to obscure transaction history by depositing tokens into a smart contract and later withdrawing them from a new address, severing the onchain link between source and destination. The protocol operates fully onchain across multiple networks and uses zk-SNARKs to enable anonymous transfers. However, following its sanction by the U.S. Treasury’s OFAC in 2022, Tornado Cash’s usage plummeted. Even after sanctions were lifted in March 2025, its volume has not recovered.
Newer designs like Privacy Pools and Railgun attempt to address Tornado Cash’s limitations around composability, compliance, and usability. Privacy Pools builds on the mixer model but introduces the concept of customizable association sets, allowing users to prove their funds were not linked to illicit activity. This offers a potential path toward regulatory acceptance while preserving privacy. Railgun allows users to interact with DeFi directly through shielded smart contracts, enabling private transfers, swaps, and liquidity provision without leaving the base chain. Railgun has seen notable adoption, with monthly transfers growing to approximately 11k and cumulative transaction volume surpassing $3 billion. This steady growth serves as a clear confirmation of users’ demand for privacy solutions onchain.
Onchain privacy has expanded beyond financial transfers to include identity, messaging, and fiat on-ramps. ZKPassport enables users to prove attributes like age or residency from official documents without revealing underlying data, supporting use cases like KYC-lite onboarding and access control. ZK Email verifies email authenticity using ZKPs of DomainKeys Identified Mail (DKIM) signatures, allowing users to prove message details without exposing content. ZKP2P facilitates P2P fiat-to-crypto swaps via platforms like Venmo or Revolut, using proof-based escrow releases to eliminate fees, custodians, and invasive KYC while preserving user privacy.
Why Privacy is Still Hard
Regulatory Pressure
The global regulatory landscape remains a major obstacle for onchain privacy. In the United States, regulatory approaches remain fragmented across state and federal levels. States like New York require strict licensing regimes such as the BitLicense, while others like Wyoming and Texas adopt more permissive policies. These disparities discourage the use and development of privacy solutions, including coins like Monero and Zcash, in more restrictive jurisdictions. At the federal level, agencies such as the Office of Foreign Assets Control (OFAC), Department of Justice (DOJ), and Financial Crimes Enforcement Network (FinCEN) continue to emphasize expansive compliance requirements and view privacy tools with skepticism.
The recent reversal of Tornado Cash sanctions and the final ruling against a reinstatement or blacklisting by OFAC create a more favorable outlook for smart contract platforms. However, the rulings do not address legal protections for developers of immutable smart contracts used in decentralized, open-source projects.
Regulatory fragmentation across national borders further complicates the outlook for privacy solutions. Countries take widely divergent approaches. Privacy coins are banned on registered exchanges in jurisdictions such as Japan and South Korea, while broader restrictions like the European Union’s MiCA framework and the FATF Travel Rule limit their usability by requiring the collection and exchange of personal data. Some nations, like China and Egypt, have implemented full bans on all crypto activity.
In contrast, countries like Switzerland support privacy-oriented financial systems, and in places like Venezuela, coins such as Monero are used pragmatically amid hyperinflation and institutional distrust. This global divergence in regulatory posture creates deep uncertainty around the development and deployment of privacy-preserving tools and complicates efforts to establish coherent norms across jurisdictions.
While outcomes will depend on jurisdiction and system design, the potential future adoption of Central Bank Digital Currencies (CBDCs) poses significant structural challenges to onchain privacy solutions. Wholesale CBDCs could shape regulatory norms and institutional practices that encourage stricter transparency requirements. Meanwhile, many retail CBDCs are positioned to compete with cryptocurrencies and often emphasize compliance over user privacy. If adopted widely, their accessibility and government backing could diminish demand for privacy-focused alternatives, even as some users may seek out such options in response to perceived surveillance risks.
Technical Challenges
Privacy-preserving protocols continue to face structural limitations that constrain their adoption and integration into the broader crypto ecosystem. While different cryptographic techniques have made meaningful progress, and some products now incorporate ZKPs in production, many privacy systems remain in early development or limited deployment. Performance has improved, thanks to purpose-built proving systems and hardware acceleration, but latency and cost are still material constraints. This is especially true for use cases that require frequent interactions or low-fee environments. The tradeoffs between privacy, speed, and usability are narrowing but have not yet reached parity with public-by-default systems.
Interoperability poses an additional challenge. Many privacy-first blockchains are not EVM compatible, requiring developers to learn new languages, such as Leo (Aleo) or Noir (Aztec), and custom tooling. This increases development overhead and makes integration with mainstream networks’ infrastructure difficult. Furthermore, private transactions often require distinct execution models and storage formats, which complicates crosschain messaging and limits composability. These architectural differences make it harder for privacy systems to plug into existing ecosystems.
Onboarding Friction
User onboarding also faces friction. Privacy products tend to operate in isolated environments that are not seamlessly connected to the broader DeFi or wallet infrastructure. Users must acquire ecosystem-specific tokens, bridge assets across networks, and interact with unfamiliar interfaces before they can access privacy features. These steps introduce cognitive and operational hurdles that deter casual users and fragment liquidity across isolated pools. Without smoother entry points, most privacy systems struggle to achieve meaningful adoption beyond niche, privacy-native audiences.
Architectural Constraints
Privacy guarantees are highly sensitive to liquidity conditions. Systems like coin mixers and privacy pools depend on large anonymity sets to effectively obscure transaction metadata. When participation is low, users become more identifiable through patterns in transaction timing, amounts, or frequency. For example, privacy in Tornado Cash relies on having enough users to blend individual activity into a crowd. However, research shows that when usage is low, it becomes easier to detect patterns, such as a user depositing and then withdrawing the same amount shortly after. Although the underlying cryptography remains sound, these behavioral patterns can expose links between actions that are intended to be private.
The Road Ahead
Complete privacy isn’t enough. The future depends on attestable privacy: systems that protect user activity while still allowing users to prove the legitimacy of their actions to regulators when necessary. Full onchain transparency, especially when linked to real-world identities, creates serious risks. In 2022, the Celsius bankruptcy filings exposed over 15,000 personal crypto wallets holding a combined $3 billion at peak value. As Taylor Monahan, lead product manager at MetaMask, pointed out, exposing onchain activity can link users to personal details like names, emails, and addresses, putting them at risk of scams, hacks, and even physical threats. This level of exposure is a major obstacle to broader adoption. Retail users don’t want their entire portfolio made public just to split a $10 USDC bill, and institutions won’t tolerate full visibility into every onchain swap or yield position they take.
What’s needed is a way to keep routine activity private. This includes hiding sender and receiver details, shielding specific transaction amounts, and giving users the option to unlink real-world information, while still allowing them to prove that their funds and activity are legitimate without revealing sensitive metadata or exposing their identity. Tools like Privacy Pools can offer this balance. Through association sets, users can prove their funds are not connected to illicit sources without revealing their full transaction metadata.
The key to adoption, though, also depends on usability. The most effective solutions will be the ones that integrate privacy without disrupting the user experience. Most users don’t care which chain they are on or how their wallet works under the hood. Privacy should feel native and integrated into existing workflows. Whether that comes from middleware like Railgun, which connects directly to users’ wallets, or from dApps like 0xbow.io with clean interfaces built on Ethereum, usability will decide what wins.
However, even well-designed privacy solutions come with tradeoffs, particularly around liquidity. They can cause liquidity fragmentation by isolating assets in private pools or requiring users to create additional wallets, thereby adding the burden of keeping an extra set of seed phrases. These shielded assets are often not seamlessly composable with transparent protocols, making integration with existing DeFi infrastructure more difficult. As a result, capital efficiency declines and user activity becomes fragmented across multiple platforms.
Recognizing this issue, leading networks have begun embedding privacy into the infrastructure itself. Several leading projects have outlined incremental privacy strategies.
Ethereum: A Path to Default Privacy
On April 10, 2025, Vitalik Buterin published a privacy roadmap for Ethereum focused on improving user privacy without making major changes to the consensus layer. The approach emphasizes practical upgrades at the wallet and application level, designed to work within Ethereum’s current modular architecture. Key components include:
- Native Shielded Balances: Wallets should integrate privacy protocols like Railgun and Privacy Pools directly, allowing users to send from shielded balances without needing a separate privacy wallet.
- One Address Per Application: Wallets would generate unique addresses for each application. This prevents activity on one application (e.g., Aave) from being publicly linked to activity on another (e.g., ENS).
- Private Send-To-Self Flows: As users manage assets across multiple addresses, internal transfers should be private by default to preserve separation between identities.
- FOCIL+ EIP-7701: These proposals enable private transactions without relying on public relayers. This simplifies integration for privacy protocols and improves censorship resistance.
Solana: Confidential Balances via Token Extensions
Solana has introduced Confidential Balances, a suite of token extensions that allow for discreet handling of transfers, minting, burning, and fees. The goal is to give users and token issuers more privacy without breaking compatibility with regulations. Key components include:
- Confidential Transfers: This option lets users send tokens without publicly revealing the amount. The system uses cryptographic proofs to confirm that the math checks out without showing the actual number.
- Confidential Fees, Minting, and Burning: Applies the same principles to protocol operations, allowing token issuers to conceal how much is created, destroyed, or paid in fees.
- Auditor Key Support: Adds an optional tool for trusted third parties, such as regulators or institutions, to view confidential activity when needed. This balances privacy with oversight.
Inco x Circle Research: Confidential ERC-20 Framework
Inco and Circle have proposed a Confidential ERC-20 framework that extends the standard ERC-20 token with encrypted balances and transfers. The framework introduces confidentiality at the token level without sacrificing composability or programmability across Ethereum applications. Key features include:
- Encrypted Balances and Transfers: User balances and transfer amounts are hidden from the public while transaction logic can still execute through encrypted computation.
- Delegated Viewing: Permissions can be granted to specific third parties, such as auditors or regulators, to decrypt and view confidential token data as needed.
- Programmable Transfer Rules: Compliance logic like blacklists or transfer thresholds can be enforced within the smart contract using encrypted identity or transaction data.
Base acquires Iron Fish
On March 6, 2025, Base acquired the Iron Fish team known for developing a privacy-focused L1 network, Iron Fish, which features encrypted transactions and a multi-asset shielded pool powered by ZKPs. The move reflects Base’s strategy to build native privacy capabilities by integrating Iron Fish’s infrastructure and technical expertise into its L2 ecosystem.
Collectively, these initiatives reflect a growing recognition that privacy is not just a user preference but a foundational infrastructure challenge. Full transparency is no longer sufficient. The conversation is shifting toward a more nuanced view: privacy must be context-aware, programmable, and capable of supporting regulatory requirements. This shift is reshaping how privacy is implemented across the stack. It is no longer treated as a standalone feature or confined to isolated chains. Instead, it is becoming a native capability designed to coexist with composability and compliance. As privacy becomes more modular and policy-aware, the boundary between public and private onchain activity is being redefined. The protocols that succeed will not be those that pursue absolute anonymity, but those that make selective disclosure both practical and secure.
Conclusion
The future of crypto depends not just on scalability or decentralization but on embedding meaningful privacy within transparent systems. Onchain privacy has matured from niche experiments into essential infrastructure, spanning payment networks, programmable environments, and composable middleware. Yet, it remains constrained by regulatory uncertainty, technical tradeoffs, and adoption hurdles.
Regulatory pressure remains one of the most persistent obstacles, not only because of fragmented and ambiguous policies across jurisdictions, but because the long-term trajectory of oversight has consistently moved toward reduced anonymity and greater traceability. For privacy to scale with the broader crypto ecosystem, it must become practical, compliant, and default. Achieving this will require coordinated progress in protocol design, policy frameworks, and user experience, where privacy is no longer a radical feature but an expected standard of digital systems.