# Privacy Networks Aztec and Miden Detail Live Confidential-Execution Designs

Both teams argue that selective, client-side privacy, not full transparency or opaque secrecy, is the precondition for serious on-chain use.

- Published: 2026-07-09T05:30:42.272Z
- Canonical: https://polylog.news/crypto/2026-07-09/privacy-networks-aztec-and-miden-detail-live-confidential-ex
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Miden](https://miden.xyz/blog/practical-privacy), [Aztec Network](https://aztec.network/blog/inside-an-aztec-transaction), [Miden (Guardian)](https://miden.xyz/blog/what-is-miden-guardian)

Two privacy-focused networks published detailed accounts of how confidential transactions actually work on their systems, part of a broader shift in which privacy is being reframed from a niche feature into a prerequisite for institutional adoption. Miden argues in [a technical post](https://miden.xyz/blog/practical-privacy) that practical privacy means computation happens locally on a user's device, with only validity proofs posted to the network, so the chain verifies that a transaction is correct without learning its contents.

Aztec described [the anatomy of one of its transactions](https://aztec.network/blog/inside-an-aztec-transaction), in which a user generates a zero-knowledge proof client-side and the network confirms it against public state. The design separates private execution from public settlement, letting some parts of a transaction stay hidden while others remain verifiable. Miden also detailed [Guardian](https://miden.xyz/blog/what-is-miden-guardian), a mechanism intended to give users and applications control over what is disclosed and to whom.

The unresolved question across both projects is governance of disclosure. Confidential execution is what serious counterparties want for order flow, payroll, and treasury operations, but a privacy system that a single operator or regulator can silently disable offers weaker guarantees than its cryptography suggests. That control question, who can turn privacy off and under what process, is now the main point of contention rather than whether the proofs themselves work.

## What this means

Client-side proving with selective disclosure lets regulated institutions transact on public chains without broadcasting positions to competitors, which widens the addressable market for privacy-focused layer-2 networks beyond the small base of privacy-maximalist retail users. The parties exposed are transparent-by-default chains that lose confidential-flow business, and privacy teams whose adoption now hinges on convincing auditors and regulators that selective disclosure satisfies compliance without a backdoor. The decisive variable is who holds the disclosure keys, since that determines whether the privacy is real or nominal.

## What to watch

- Total value and transaction counts actually settling through Aztec and Miden mainnets, which would show whether institutional interest converts into usage rather than whitepapers.
- How each network specifies control of the ability to turn privacy off in code, because a unilateral operator control undercuts the institutional case it is built on.