Ethereum Privacy New Infrastructure: In-depth Analysis of How Aztec Achieves "Programmability Privacy"

Written by: ZHIXIONG PAN Link:

Statement: This article is a reprinted content, and readers can obtain more information through the original link. If the author has any objections to the form of reprint, please contact us, and we will make modifications according to the author's request. Reprinting is for information sharing only and does not constitute any investment advice, nor does it represent Wu's views and positions.

In the second decade of blockchain technology development, the industry is facing a fundamental philosophical and technical paradox: Ethereum, as the “world computer”, has successfully established a trustless value settlement layer, but its radical transparency is evolving into an obstacle to widespread adoption. Currently, every interaction, asset allocation, salary flow, and even social relationship of on-chain users is exposed in a permanently immutable public panoramic prison. This “glass house” living condition not only infringes on personal sovereignty but also excludes the vast majority of institutional capital due to the lack of protection for commercial secrets.

2025 marks a decisive turning point for industry consensus. Ethereum co-founder Vitalik Buterin clearly stated that “privacy is not a feature, but hygiene,” defining it as a fundamental basis for freedom and a necessary condition for social order. Just as the internet evolved from plaintext HTTP to encrypted HTTPS, giving rise to the prosperity of e-commerce, Web3 is at a similar critical juncture. With approximately $119 million in funding support, Aztec Network (Ignition architecture) is driving Ethereum towards an upgrade in programmable privacy infrastructure through the Ignition Chain, the Noir language ecosystem, and proof applications based on Noir, such as zkPassport.

Macro Narrative: From Point Breakthrough to “Overall Privacy” Defense Depth

The Ethereum ecosystem's understanding of privacy is no longer limited to a single mixing protocol, but has evolved into a “Holistic Privacy” architecture that spans the network layer, hardware layer, and application layer. This paradigm shift became the focus of the industry at the Devconnect conference in 2025, establishing that privacy protection must have a full-stack defensive depth.

Software Standard Refactoring: Kohaku and Stealth Address

The Kohaku reference implementation, developed by the Ethereum Foundation's Privacy Exploration team (PSE), marks a transition of privacy technology from “wild plugins” to a “regular army.” Kohaku is more than just a wallet SDK; it attempts to fundamentally restructure the account system.

By introducing the “Stealth Meta-Address” mechanism, Kohaku allows the receiver to only disclose a static meta public key, while the sender generates a unique one-time on-chain address for each transaction based on elliptic curve cryptography.

For external observers, these transactions are like being sent to random black holes, unable to establish a correlation map with the user's real identity. Furthermore, Kohaku provides reusable integration components around mechanisms such as stealth meta-address/stealth addresses and attempts to advance privacy capabilities from being an “add-on” to a more standardized wallet infrastructure.

The Last Bastion of Hardware Defense: ZKnox and Quantum Threat Resistance

If Kohaku protects the logic at the software level, then ZKnox, a project funded by the Ethereum Foundation (EF) that fills the ecological hardware gap, is dedicated to addressing deeper issues of key security and future threats. With the widespread adoption of ZK applications, more and more sensitive witnesses (which may contain key materials, identity data, or transaction details) need to participate in the proof and signing processes on the client side, thereby increasing the risk of leakage when the client is compromised. ZKnox focuses more on improving and implementing infrastructure that makes post-quantum cryptography “usable and affordable” on Ethereum (for example, promoting related precompiles to reduce the cost of lattice cryptographic computations), paving the way for future migration to PQ signature schemes.

More importantly, in the face of the potential threat that quantum computing may pose to traditional elliptic curve cryptography in the 2030s, ZKnox is focusing more on the infrastructure work of “making quantum-resistant cryptography available and affordable on Ethereum”. For example, EIP-7885 proposes adding NTT precompiles to reduce the on-chain verification costs of lattice cryptography (including schemes like Falcon), paving the way for future PQ migration.

The historical status and technical architecture of Aztec: defining “private world computer”

In the evolution of the privacy track, Aztec occupies a unique ecological niche. Unlike the pseudonymous mechanisms of the Bitcoin era, and surpassing the single “transactional privacy” provided by Zcash or Tornado Cash, Aztec is dedicated to achieving Turing-complete “programmable privacy.” Its core team includes co-inventors of the PLONK zero-knowledge proof system, which gives Aztec a deep-rooted cryptographic originality from its very genes.

Hybrid State Model: Breaking the Impossible Triangle

The biggest challenge in building a privacy smart contract platform is how to handle state. Traditional blockchains either have entirely public states (like Ethereum) or entirely private states (like Zcash). Aztec creatively proposes a hybrid state model: at the private level, it adopts a Bitcoin-like UTXO model, storing user assets and data as encrypted “notes.”

These notes express “spent / expired” by generating a corresponding nullifier, thus preventing double spending and maintaining privacy regarding the content of the notes and the ownership relationships. On the public side, Aztec maintains a publicly verifiable state, which is updated by public functions in the network's public execution environment.

This architecture allows developers to mix the definition of private functions and public functions within the same smart contract. For example, a decentralized voting application can publicly disclose the “total number of votes” as a global state, but keep strictly confidential through private states “who voted” and “what they voted for.”

Dual Execution Model: The Convergence of PXE and AVM

The execution of Aztec is divided into two layers: private functions are executed in the client's PXE and generate proofs and commitments related to the private state; public state transitions are executed by the sequencer (running the public execution environment / VM) and generate (or delegate the prover network to generate) validity proofs that can be verified on Ethereum.

Client-Side Proving: All private data processing occurs in the user's local “Private Execution Environment (PXE)”. Whether generating transactions or computing logic, the user's private keys and plaintext data never leave their device. PXE is responsible for running the circuit locally and generating a zero-knowledge proof.

Public Execution and Verification (AVM): Users only submit the generated proof to the network. On the network side, the sorter/block committee verifies the private proof during the packaging process and re-executes the public part. The public contract logic is executed in AVM and included in the final validity proof that can be verified on Ethereum. This split of “private inputs on the client, public state transitions verifiable” compresses the conflict between privacy and verifiability into a provable interface boundary, without requiring the entire network to see all plaintext data.

Interoperability and Cross-Layer Communication: Portals and Asynchronous Messaging

Under the Ignition architecture, Aztec does not treat Ethereum as a “back-end execution engine” to proxy DeFi instructions, but instead establishes L1↔L2 communication abstraction through Portals. Since private execution requires “preparation and proof” on the client side in advance, and public state modifications must be executed by the sequencer at the chain head, Aztec's cross-domain calls are designed as a one-way, asynchronous messaging model: L2 contracts can initiate call intent to the L1 portal (or vice versa), and the message becomes consumable state in subsequent blocks through the rollup mechanism, with applications needing to explicitly handle scenarios such as failures and rollbacks.

The Rollup contract assumes key responsibilities such as maintaining the state root, verifying state transition proofs, and transporting message queue states, thereby achieving composable interaction with Ethereum while maintaining privacy constraints.

Strategic Engine: Democratization of Noir Language and Zero-Knowledge Development

If Ignition Chain is the backbone of Aztec, then the Noir language is its soul. For a long time, the development of zero-knowledge proof applications was constrained by the “double-brain problem,” where developers had to be both seasoned cryptographers and skilled engineers, manually translating business logic into underlying arithmetic circuits and polynomial constraints, which was not only inefficient but also prone to introducing security vulnerabilities.

The power of abstraction and backend independence

The emergence of Noir is to end this “Tower of Babel” era. As an open-source domain-specific language (DSL), Noir adopts a modern syntax similar to Rust, supporting advanced features such as loops, structs, and function calls. According to the developer report by Electric Capital, the amount of code written in Noir for complex logic is only one-tenth that of traditional circuit languages (such as Halo2 or Circom). For example, the Payy privacy payment network, after migrating to Noir, saw its core codebase reduced from thousands of lines to about 250 lines.

More strategically significant is Noir's “Backend Agnosticism.” Noir code is compiled into an Intermediate Representation Layer (ACIR), which can interface with any proof system that supports the standard.

Noir decouples circuit expressions from concrete proof systems through ACIR: it is paired by default with Barretenberg within the Aztec protocol stack, and ACIR can also be converted/adapted to different backends such as Groth16 in off-chain or other systems. This flexibility is making Noir a universal standard across the entire ZK field, breaking down barriers between different ecosystems.

Ecological Explosion and Developer Moat

Data proves the success of the Noir strategy. In Electric Capital's annual report, the Aztec/Noir ecosystem has ranked among the top five fastest-growing ecosystems for developer growth in the industry for two consecutive years. Currently, there are over 600 projects on GitHub built using Noir, covering areas from authentication (zkEmail), gaming to complex DeFi protocols.

Aztec, by hosting the NoirCon Global Developer Conference, not only solidified its technological moat but also nurtured an active ecosystem of privacy-native applications, signaling that privacy applications are about to experience a Cambrian explosion.

Cornerstone of the Internet: Decentralized Practices of Ignition Chain

In November 2025, Aztec will launch the Ignition Chain on the Ethereum mainnet (the current phase focuses on decentralized block production and proof process exercises, with transactions and contract execution expected to gradually open in early 2026). This is not only a technical milestone but also a radical practice of the commitment to Layer 2 decentralization.

The courage to be decentralized from the start.

In the current Layer 2 scaling competition, the vast majority of networks (such as Optimism and Arbitrum) initially rely on a single centralized sequencer to ensure performance, postponing decentralization to an uncertain future.

Aztec chose a completely different path: Ignition Chain has operated on a decentralized validator/ sequencer committee architecture since its inception, aiming to front-load key authorities to an open set of validators. The network triggers the genesis block once the validator queue reaches the launch threshold of 500, and in the early stages after going live, it attracted over 600 validators to participate in the block production and endorsement process.

This design is not superfluous but rather the survival baseline of a privacy network. If the sorter is centralized, regulatory agencies or powerful entities can easily exert pressure to demand the review or rejection of privacy transactions for specific addresses, rendering the entire privacy network ineffective. The decentralized sorter/committee design eliminates the single point of censorship of a single sorter and significantly enhances the censorship resistance of transactions being packaged under the premise of “honest participants existing and protocol assumptions holding.”

Performance Roadmap

Although decentralization brings security, it also poses challenges to performance. Currently, the block generation time of the Ignition Chain is about 36-72 seconds. Aztec's roadmap aims to gradually compress the current long block interval to around 3-4 seconds (with a target time of the end of 2026) through parallelizing proof generation and network layer optimization, in order to approach the interactive experience of the Ethereum mainnet. This marks a transition for privacy networks from “usable” to “high performance.”

Killer application: zkPassport and the paradigm shift in compliance

Technology itself is cold until it finds application scenarios that solve real human pain points. zkPassport is more accurately one of the identity / compliance signal tools in the Noir ecosystem. Aztec uses its circuits for compliance proofs like sanction list checks in its own scenarios, thereby exploring a compromise between privacy and compliance.

From data collection to fact verification

Traditional KYC (Know Your Customer) processes require users to upload passport photos and ID documents to centralized servers, which not only makes the process cumbersome but also creates countless vulnerable data honeypots. zkPassport completely overturns this logic: it utilizes the NFC chip embedded in modern electronic passports and government digital signatures to read and verify identity information locally through the physical contact between the phone and the passport.

Subsequently, the Noir circuit generates zero-knowledge proofs in the user's local environment on their mobile phone. Users can prove facts such as “over 18 years old”, “nationality is on the allowed list / not on the prohibited jurisdiction list”, “not on the sanctions list check”, without disclosing complete details like full date of birth, passport number, etc.

Preventing Witch Attacks and Institutional Access

The significance of zkPassport goes far beyond identity verification. By generating passport-based anonymous identifiers, it provides a powerful tool for “Sybil Resistance” in DAO governance and airdrop distribution, ensuring fairness of “one person, one vote,” while eliminating the possibility of reverse tracking users' real identities.

On a practical level, such verifiable, minimal disclosure compliance signals are expected to reduce compliance friction for institutions participating in on-chain finance, but they are not equivalent to a complete KYC/AML process. Institutions can use zkPassport to prove their compliance qualifications and participate in on-chain financial activities without exposing their trading strategies and capital scales. Aztec demonstrates through this application that compliance does not necessarily mean establishing a total surveillance system; technology can achieve regulatory requirements while preserving individual privacy.

Economic Model: Continuous Clearing Auction (CCA) and Fair Distribution

As the fuel of a decentralized network, the issuance mechanism of the native token AZTEC itself reflects the project's ultimate pursuit of fairness. Aztec abandons traditional issuance models that easily lead to bot sniping and gas fee wars, and collaborates with Uniswap Labs to introduce the innovative “Continuous Clearing Auction (CCA).”

Price Discovery and Anti-MEV

The CCA mechanism allows the market to engage in sufficient competition within a set time window to discover the true price. In each clearing cycle of the CCA, transactions are settled at a unified clearing price, thereby reducing the space for front-running and Gas bidding that arises from the rush to complete transactions. This mechanism effectively eliminates the profit margin for frontrunners, enabling retail investors to stand on the same starting line as the whales.

The liquidity owned by the agreement

What is even more innovative is that CCA has achieved an automated closed loop for issuance and liquidity establishment. The auction contract can automatically inject (some) auction proceeds and tokens into the Uniswap v4 liquidity pool based on pre-published parameters, forming an on-chain verifiable “issuance → liquidity” closed loop.

This means that the AZTEC token has had a deep on-chain liquidity from the very moment of its inception, avoiding the common volatility associated with new coin listings and protecting the interests of early community participants. This more DeFi-native method of issuance and liquidity guidance is often used to illustrate a pathway through which AMM can expand from “trading infrastructure” to “issuance infrastructure.”

Conclusion: Building the “HTTPS Era” of Web3

The ecological panorama of the Aztec Network, from the underlying Noir language standard to the upper-layer zkPassport application, and further to the network support of Ignition Chain, is transforming the long-conceived “HTTPS upgrade” of the Ethereum community into a usable engineering reality. This is not an isolated technical experiment, but rather resonates with Ethereum-native initiatives such as Kohaku and ZKnox, collectively building a layered privacy defense system from hardware to applications.

If the early development of blockchain established trustless value settlement, then the core theme that follows will be the establishment of data autonomy and confidentiality. In this process, Aztec plays a crucial infrastructure role: it does not attempt to replace the transparency of Ethereum, but rather complements the missing half of the puzzle through “programmable privacy.” With the maturation of technology and the improvement of compliance frameworks, we can expect a future where privacy is no longer an “add-on feature” but a “default attribute,” a “private world computer” that retains the verifiability of public ledgers while respecting individual digital boundaries.