AZTEC

Aztec: A Privacy-Focused Ethereum Layer 2 With Staking and Onchain Governance

Aztec combines private smart-contract execution with an Ethereum-connected rollup, while AZTEC supports transaction fees, network security, block production incentives, and protocol governance. The system remains early, and its practical value depends on proving infrastructure, sequencer participation, governance safeguards, and adoption by developers and users.

What Aztec is designed to do

Aztec is an Ethereum Layer 2 designed for applications that need programmable privacy. The project describes the network as supporting private smart contracts and decentralized applications through zero-knowledge cryptography, while also retaining a public execution environment. That combination is intended to let developers build applications where selected information can remain private without abandoning Ethereum as the settlement layer.

The network is not presented as a general-purpose privacy add-on for existing Ethereum applications. Developers must deploy contracts and users must transact through Aztec-specific infrastructure, including its execution environment, proving system, bridges, and wallet or account tooling. This makes developer support and compatibility practical dependencies rather than optional extras.

How the network is organized

Aztec operates as an Ethereum-connected rollup with separate network roles. Sequencers propose and validate blocks, while provers create the zero-knowledge proofs required for finalized blocks. The official token description says sequencers and provers receive AZTEC emissions after blocks are finalized, linking the token economy to both block production and proof generation.

The network documentation identifies Alpha as Aztec’s initial mainnet phase. It is connected to Ethereum mainnet and has governance, networking, and transaction processing active, but the documentation also describes the network as live and early, with critical bugs still possible. That qualification matters: network operation does not by itself establish production-grade maturity or a completed security track record.

What AZTEC does

AZTEC has three central protocol roles. It can be bridged from Ethereum and used to pay transaction fees on Aztec; it can be staked by sequencers and validators; and it can be used in governance. The documentation describes fees on Aztec as being paid in Fee Juice, a non-transferable fee asset created by bridging AZTEC into the network. This separates the fee accounting asset used inside the rollup from the transferable ERC-20 token on Ethereum.

Staking is intended to provide economic security and make malicious behavior punishable through slashing. Token holders can also delegate stake rather than operate infrastructure themselves. The delegation documentation sets a minimum Token Vault balance of 200,000 AZTEC for delegation, while the official token page gives the same threshold for running a sequencer. These thresholds make participation accessible to more holders through delegation, but they also leave infrastructure operation concentrated among participants with substantial balances and technical capacity.

Governance and upgrade control

Aztec’s governance process combines sequencer signaling with token-based voting. A proposed upgrade first needs support from block producers during assigned slots. If the payload reaches the required quorum within a round, it can be submitted as a formal proposal. Token holders then vote, followed by an execution delay before an approved change can be carried out. The process is designed to make upgrades pass through several stages rather than allowing a single administrator to apply them immediately.

The governance contracts include a Registry that tracks rollup instances, a Governance contract that manages proposals and voting power, and a Governance Proposer that filters proposals through sequencer signaling. The latest rollup in the Registry is treated as canonical for block rewards. Governance actions and voting occur on Ethereum Layer 1, so Ethereum transaction costs, contract correctness, and the availability of the L1 governance contracts are part of Aztec’s upgrade and security model.

Who the system is for

Aztec is aimed primarily at developers and users who need privacy within programmable applications, as well as sequencers, provers, delegators, and governance participants. Developers depend on the network’s private execution and proving tools. Operators depend on staking economics and node software. Users depend on bridges, wallets, fee conversion, and applications that actually make use of private state. The project’s network documentation therefore lists both sequencer operators and builders as target participants, rather than treating the token as a standalone payment asset.

For ordinary token holders, the practical choices are narrower than the full protocol design may suggest. A holder can retain AZTEC, lock it for governance, stake through an operator, or operate infrastructure if the technical and balance requirements are met. Delegation may reduce the operational burden, but it introduces dependence on the chosen operator and on the staking contract’s exit, reward, and slashing rules.

Limitations and open questions

Aztec’s main limitation is execution risk at an early stage. The official network documentation explicitly warns that the Alpha network may contain critical bugs. Privacy also depends on more than zero-knowledge proofs: contract design, wallet behavior, metadata, bridge implementation, user mistakes, and application-level disclosure can all affect the privacy a user actually receives. The project materials establish the intended architecture, but they do not by themselves prove that every application will preserve privacy under all conditions.

The token model also creates several questions for long-term participants. Emissions fund sequencers and provers, but issuance can dilute holders; staking creates slashing and lock-up exposure; and governance influence may favor large stakers or delegated operators. Adoption must still be demonstrated through sustained developer activity, useful applications, reliable proving capacity, and meaningful user demand. AZTEC therefore has clear protocol functions, but those functions do not guarantee usage, decentralization, or economic value.

Key takeaways

• Aztec is an Ethereum-connected Layer 2 focused on programmable privacy through zero-knowledge technology.
• AZTEC is used for fees, staking, block-production and proving incentives, and governance.
• Aztec governance combines sequencer signaling, token voting, execution delays, and rollup registry controls.
• Fee Juice is the non-transferable fee asset created when AZTEC is bridged into Aztec for network use.
• Delegation lowers the infrastructure burden, but introduces operator, staking, slashing, and lock-up dependencies.
• The network is in an early Alpha phase, so bugs, adoption, proving capacity, and governance concentration remain material questions.

Risks and open questions

• The official documentation describes Alpha as early and warns that critical bugs are possible.
• Privacy outcomes may depend on application design, wallet behavior, metadata, bridges, and user practices, not only on the underlying proof system.
• AZTEC emissions may dilute holders, while staking introduces slashing and withdrawal-delay exposure.
• Sequencer and prover participation may become concentrated among large or technically capable operators.
• Governance power can be influenced by staking balances, delegation, quorum rules, and the design of upgrade payloads.
• The existence of protocol functions does not establish sustained application adoption, deep liquidity, or long-term economic value.