Privacy on Ethereum has always sat at the edge of the stack: mixers that hide transfers without touching the contract layer, ZK rollups that compress computation but leave application logic public. Neither approach works for institutions that need to prove compliance without exposing client data, or for applications that require private state inside a smart contract.
Aztec launched its Alpha Network on 31 March 2026 as an attempt at a different architecture: a Layer 2 where private execution, private identity, and private data are native to the contract layer rather than layered on top.
In this edition, we look at what Aztec is actually building, where the architecture is genuinely different from earlier attempts, and what a launch with known vulnerabilities means for its prospects.

Why Existing Privacy Solutions Stalled
The mixer and shielded-transfer model hides token movements but does not hide what contracts do, who calls them, or what state they read. That is fine for basic anonymity and useless for anything more complex: a lending protocol, a payroll system, or a tokenized securities trade where counterparty identity and trade terms need to stay confidential. Generic ZK rollups solved the throughput problem but did not address application-level privacy. Developers still had to expose contract logic, account balances, and execution traces to the public chain.
Aztec’s argument, made consistently for nine years of development, is that privacy needs to be at the execution layer. The Alpha Network lets developers write contracts where some functions run privately on the user’s device, generating a proof that sequencers verify without seeing the underlying data. Private state stays offchain and only proofs and public state touch Ethereum, which batches them roughly every 12 seconds.
Alpha Network
Developers write contracts in Noir, Aztec’s purpose-built language, and label functions public or private.
Private functions execute locally, using a proving system designed to run on ordinary hardware including phones and browsers. The design supports 3 capabilities:
Hiding balances and transfers
Proving identity attributes like accreditation or residency without exposing full transaction history
Running smart-contract logic privately while still settling to Ethereum
These can be used together or independently, which matters for regulated use cases where an application might need private computation but public settlement.
Aztec’s selective disclosure mechanism is where the institutional story lives. A user can prove creditworthiness to a lender, or satisfy KYC without revealing their entire onchain history. Earlier privacy layers typically treated compliance as a second-order problem. Aztec treats it as the primary reason institutions would use private computation at all.
2 weeks before launch, on 17 March, the team found a critical vulnerability in its proving system which could have risked loss of funds if exploited. The fix is scheduled for July 2026 in a v5 release. Third party audits have flagged additional issues in the underlying proving library.
Who is the Alpha Release For?
The Alpha is a developer environment, specifically designed for them to build and test applications before the network reaches full production maturity. However, the institutions Aztec wants to serve, regulated lenders, payroll processors, asset managers, likely will not touch infrastructure with a known critical vulnerability.
The July patch and subsequent Beta process are what determine whether Aztec reaches that audience. Consumer usage is another determinant as Noir is a relatively new language with a small ecosystem and client-side proving adds friction compared to standard EVM development.