Aztec V5 Launches: Client-Side ZK & Hybrid State Enable Private Smart Contracts on Ethereum

Aztec has pushed privacy deeper into Ethereum with the alpha launch of its v5 execution layer, rolling out what it calls a programmable privacy framework that lets apps handle both public and private state inside the same layer-2 environment. Aztec Labs says Alpha V5 is live on mainnet and delivers its fastest private transactions yet — with apps beginning to go live this week (starting with invite-only Nyx, briefly opened to all for 24 hours). What’s new - Client-side ZK execution: Instead of exposing transaction inputs and execution data to every validator, Aztec moves private computation to the user’s device. Confidential computations run locally, then the client submits cryptographic proofs for on-chain verification, shrinking what the network sees while preserving Ethereum security. - Noir integration and recursive SNARKs: The release centers on a zero-knowledge execution engine paired with Noir, Aztec’s domain-specific language for private smart contracts. Private functions execute off-chain and produce recursive SNARK proofs that attest to correct state transitions without revealing plaintext inputs, amounts, or identities. - Hybrid state model: To solve a core problem for privacy chains — contention when private actors update shared public state — Aztec separates private and public state. Private data lives in UTXO-like note trees; public state uses key-value trees. Private functions can emit deferred public calls that are processed later in the same transaction lifecycle, enabling confidential and public operations to interoperate deterministically and without race conditions. Why it matters Aztec’s architecture is built to let developers combine confidential user data with public blockchain state — for example, private order matching that still interacts with shared liquidity pools, private liquidity provisioning, and systems that selectively disclose only required information for compliance. By keeping transaction details hidden until state commitment, Aztec also makes it harder for observers to frontrun or extract value from pending transactions, addressing MEV risks tied to visible mempool data. Privacy + compliant identity Aztec has long advocated “programmable privacy” rather than simple anonymity. CEO Zac Williamson told crypto.news in April 2025 that practical on-chain privacy rests on three pillars — user privacy, confidential transaction data, and private smart contract execution — and argued privacy should be baked into mainstream crypto: “all crypto will be private.” He also emphasized selective disclosure over blanket anonymity for compliance, pointing to ZKPassport demos where an NFC passport can generate a zero-knowledge proof that reveals only the specific attribute a user chooses (nationality, age, etc.). That vision expanded in May 2026 when Aztec Labs acquired ZKPassport and committed to keep the identity platform open source. The integration brings zero-knowledge identity verification into Aztec’s stack; the tech has already been used on Aztec’s network for Sybil resistance and to perform sanctions screening during the AZTEC token sale while keeping participant data private. Security context The v5 launch comes shortly after Aztec addressed unrelated security incidents involving legacy products. Earlier this month the team disclosed an investigation after roughly $2 million was moved from an immutable payments contract created in 2021 (a product retired in 2022). Separately, about $2.1 million was lost from a deprecated RollupProcessorV3 contract tied to Aztec Connect. Aztec said both incidents involved legacy infrastructure that remained live on Ethereum after the products were sunset and stressed these events were not related to the active Aztec network or the AZTEC ERC‑20 token. Bottom line Alpha V5 is a significant technical step toward making private smart contracts practical on Ethereum by combining client-side zero-knowledge execution, a hybrid state model to avoid contention, and selective disclosure building blocks for compliance. The release will be watched closely by DeFi builders looking to add confidential computation without losing access to public liquidity and composability.