# Aztec Turns On Private Smart Contracts for Ethereum, Proving on Phones

The V5 alpha cut block times to six seconds and pushes zero-knowledge proving onto users' own devices, as rival privacy layers including Miden make the same case to institutions.

- Published: 2026-07-28T05:30:46.251Z
- Canonical: https://polylog.news/crypto/2026-07-28/aztec-turns-on-private-smart-contracts-for-ethereum-proving
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Aztec Network](https://aztec.network/alpha-v5), [Miden](https://miden.xyz/blog/practical-privacy), [Miden (Guardian)](https://miden.xyz/blog/what-is-miden-guardian)

Aztec Network has taken its [V5 alpha](https://aztec.network/alpha-v5) live on the Ethereum main network, delivering what it describes as the first Ethereum layer-2 with a complete execution environment for private smart contracts. The upgrade, approved by an on-chain vote of AZTEC token holders, lets users generate the zero-knowledge proofs that keep a transaction private on ordinary laptops and phones rather than on centralized proving hardware. Aztec reports that average transaction costs fell by roughly half, block times dropped from 14 seconds to six, and a private token transfer now costs under five cents.

The architecture separates privacy into three layers: confidential data for payments and real-world-asset transfers, private identity that still permits selective disclosure for compliance, and private compute that keeps application logic hidden. That last point is the center of the current contest. Aztec is not arguing that confidentiality is a feature for people with something to hide. It is arguing, alongside competitors, that no serious institution will settle payrolls, treasury flows, or client positions on a ledger where every counterparty can read them.

The competing argument is arriving in parallel. Miden argues that [practical privacy](https://miden.xyz/blog/practical-privacy) built on a client-side, actor-based model is the precondition for blockchain's next phase, and its [Guardian](https://miden.xyz/blog/what-is-miden-guardian) design pairs confidentiality with recovery and compliance controls aimed at regulated users. The shared point is that confidential execution is being reframed from a niche demand into infrastructure.

The task here is separating what has shipped from what has been promised. An alpha on mainnet is a live network with real constraints, not a finished product, and Aztec itself has said security remains the priority after vulnerabilities appeared in its V4 release. What is verifiable today is that proving is moving to the user's device and that costs have fallen, which lowers the two barriers, latency and price, that kept private execution theoretical.

## What this means

The mechanism that matters is who holds the proving key and where the proof is computed. Moving proof generation onto a user's own device reduces dependence on a small set of proving servers, which is the point where privacy chains have historically re-centralized. If confidential execution becomes a requirement for institutional on-chain activity, the beneficiaries are the privacy layers that deliver working networks and the tokenized-asset issuers that need to hide flows from competitors, while transparent general-purpose chains lose the assumption that public-by-default is acceptable.

## What to watch

- Whether real value and active applications settle on Aztec's alpha in the coming weeks, which separates a live network from a functioning economy.
- How regulators treat selective-disclosure designs, because a privacy chain that cannot satisfy compliance reporting will be excluded from the institutions it is trying to attract.
- Whether device-side proving performs reliably under heavy demand, since a fallback to centralized provers would reintroduce the single point of control these systems are built to remove.