Aztec - Privacy ZK Rollup
Category: Privacy L2Maturity: Production (Ignition Chain)
Privacy Approach: ZK-ZK Rollup with hybrid state model
Overview
Aztec is a privacy-focused rollup on Ethereum that enables private transactions and programmable privacy. It provides a fully programmable network where applications can access both private and public state. The platform uses the Noir language with the Aztec.nr framework to write smart contracts featuring a hybrid execution model: private functions execute client-side for privacy, while public functions execute on the network for transparency and auditability.Supported Patterns
- Noir Private Contracts - Noir private smart contracts
- Privacy L2s - Privacy-native rollup execution
- ZK Shielded Balances - Confidential balances for derivatives
- Shielding - Confidential ERC-20 transfers
Architecture
Hybrid State Model
- Private State - UTXO-based model managed by wallet on user’s device
- Public State - Account-based model managed by AVM (Aztec Virtual Machine) on nodes
Key Components
Smart Contracts- Written in Noir using Aztec.nr framework
- Hybrid execution: private (client-side) and public (network) functions
- Honk (UltraHonk) and UltraPlonk
- Honk enables fast recursion without trusted setup
- Rollup posts data to Ethereum L1 using EIP-4844 blobs
- Decentralized sequencers with randomized leader election
- L2 validity proofs verified on Ethereum L1
Privacy Capabilities
Private Transfers
Optional shielding of token amounts and counterparties from public chain observation.Selective Disclosure
Users can export viewing keys for auditors and regulators while maintaining general privacy.Programmable Privacy
Circuits enable private execution of DeFi logic including DEX operations and lending within Aztec.Enterprise Use Cases
Financial Institutions- Private stablecoin transfers and settlement
- Confidential payment rails
- Confidential DeFi strategies
- Private portfolio movements
- Cross-border payments with regulatory audit
- Hidden competitive data
Technical Details
Proof System
- zkSNARKs with Plonkish proving system
- Efficient verifier contracts
- UTXO note commitments with nullifiers preventing double spends
L1/L2 Communication
“Portals” enable cross-layer communication:- Contract pairs (L1 and L2) pass messages asynchronously
- Enables token bridges and cross-chain governance
- No trusted third parties required
Account Model
- Native account abstraction at protocol level
- All accounts are smart contracts
Sequencer Model
- Decentralized sequencer network (Fernet)
- VRF-based randomized leader election
- Based Fallback mechanism for censorship resistance
- Users can submit transactions directly to L1 if L2 sequencers attempt censorship
Strengths
- Strong Privacy Guarantees - Privacy for data, execution, contract code, and executor identity
- Programmable Privacy - Smart contract execution extends beyond simple shielded transfers
- Mature Infrastructure - Open-source with audited components and active research team
- Censorship Resistance - Based Fallback mechanism for direct L1 submission
Limitations
State Synchronization
Users must download and trial-decrypt note history to discover funds. Cannot simply query a balance. Wallets must actively track, discover, and consume notes, creating synchronization bottlenecks compared to public L2s.Client-Side Proving
Private execution requires local proof generation via PXE (Private Execution Environment), demanding significant compute resources from end users.Compliance Considerations
While selective disclosure exists, regulatory acceptance of retroactive auditing versus proactive censorship (e.g., OFAC screening at sequencer level) remains unclear.Performance Trade-offs
The system requires extensive engineering with lower throughput compared to public rollups, raising questions about suitable use cases.Integration Notes
Development Environment- Noir language and Aztec.nr framework
- Local PXE for private execution
- Standard Ethereum tooling for public state
- Client-side proving capability
- Note synchronization infrastructure
- Portal contracts for L1/L2 communication
- UTXO-based private state requires note tracking
- Viewing key management for selective disclosure