# Aztec Launches Alpha V5, an Ethereum Layer-2 That Proves Private Transactions on the User's Own Device

The network proves a fully private transaction in about 2.5 seconds on a laptop and cuts fees below five cents, but a critical vulnerability remains unpatched and audits are still running.

- Published: 2026-08-02T05:31:41.327Z
- Canonical: https://polylog.news/crypto/2026-08-02/aztec-launches-alpha-v5-an-ethereum-layer-2-that-proves-priv
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Aztec Network](https://aztec.network/alpha-v5), [Aztec Network (Introducing Alpha V5)](https://aztec.network/blog/introducing-alpha-v5)

Aztec has taken its V5 alpha network live on the Ethereum mainnet. It describes Alpha V5 as the first Ethereum layer-2 on which smart contracts can hold both private and public state, and where every private transaction is [proven on the user's own device](https://aztec.network/alpha-v5) rather than by a sequencer or operator. No intermediary sees the data of a private transfer.

The engineering gains are the core of the release. Aztec says Alpha V5 proves a fully private transaction in roughly 2.5 seconds on a laptop and lowers fees to under five cents. It also cut block time from 14 seconds to six and reduced the protocol circuit gate count by about half. The team reports lowering the cost of elliptic-curve signature verification by around half and speeding up its Poseidon2 hashing by roughly three times. The first applications, [introduced with the launch](https://aztec.network/blog/introducing-alpha-v5), begin with a wallet called Nyx for private transfers and private yield on the lending protocol Aave.

The team is direct about the stage of the project. A critical security vulnerability remains unpatched, audits are in progress, and users are told to deposit only funds they can afford to lose. That candor is the point. Privacy at the base layer is now being released as working code that outside parties can test, not as a whitepaper promise.

For a reader focused on sound money, the important claim is architectural. If proving happens on the client's own device, confidentiality is a property of the protocol rather than a permission granted by an operator who could later revoke it or monitor activity. That is the difference between genuine privacy and privacy that only appears to exist, and it is what privacy-focused networks are now competing over.

## What this means

Confidential execution is moving from a niche feature to a design baseline that institutions and ordinary users can actually run, which pressures transparent-by-default chains to explain how large investors can transact without broadcasting their positions. The exposed parties are the established public layer-2s competing for the same liquidity, and any privacy design that relies on a trusted operator, because a client-side proving model undercuts the case for operator-managed confidentiality. The unpatched vulnerability is the near-term risk that determines whether early users treat this as usable infrastructure or a testbed.

## What to watch

- Whether Aztec discloses and patches the flagged critical vulnerability before meaningful funds move onto the network, the condition for institutional testing.
- How much value flows into the first Nyx and Aave integrations, an early signal of real demand for on-chain privacy rather than curiosity.
- Whether competing privacy layers such as Miden respond with their own live-network claims, which would show the contest is over who controls confidentiality.