# Aztec

> Privacy-first Ethereum L2 zkRollup for private smart contracts, private state, public/private execution, and Aztec.nr/aztec.js application development.

- Readiness score: **70/100** (score.v2)
- Integration difficulty: high
- Chains: ethereum
- Categories: privacy, layer-2, zero-knowledge, smart-contracts
- Last verified: 2026-06-04 by composewith.eth research (Aztec docs, local quickstart, and GitHub resources live-verified via WebFetch 2026-06-04) (confidence: high)

## Resources

- docs: https://docs.aztec.network/
- sdk: https://github.com/AztecProtocol/aztec-packages
- template: https://github.com/AztecProtocol/aztec-starter
- support: https://forum.aztec.network/

## Good for

- private smart contracts and private application state
- apps that need both private and public execution
- builders willing to use Aztec.nr rather than EVM Solidity contracts

## Avoid for

- projects that require EVM compatibility
- simple wallet token shielding on existing EVM chains

## Capabilities

### Private smart contracts (beta)
Best for: confidential application logic and private state, hybrid private/public smart contract flows
- Aztec is not EVM compatible and requires Aztec.nr, PXE, and Aztec-specific tooling.

### Local network and testnet development tooling (beta)
Best for: local private contract prototyping, testnet development with aztec, aztec-wallet, Noir, and Barretenberg
- Toolchain requirements are heavier than standard EVM development and docs identify alpha/testnet versions.

## Composes with

- **the-graph** (indexing_and_data; supports) — Public Aztec-adjacent events and application settlement surfaces can be indexed for dashboards where data is intentionally public.
- **semaphore** (alternative; alternative) — Semaphore is a narrower anonymous signaling primitive when full private smart contracts are not needed.
- **maci** (alternative; alternative) — MACI is the more direct fit for private voting when the app does not need general private smart contracts.

## Known issues

- **Aztec is not EVM compatible** (medium, confirmed) — workaround: Use Aztec when private smart contracts are central to the product. Use EVM privacy protocols such as Railgun when the requirement is private token flows on existing EVM chains.
  - source: https://docs.aztec.network/ (retrieved 2026-06-04, high)

---
Canonical: https://composewith.eth/protocols/aztec · JSON: https://composewith.eth/protocols/aztec.json