ZK proof verification contract.

Calculates boosted reward shares for active provers based on a configured curve, incentivizing consistent participation.

• Roles:
  • rollup: Rollup

Library immutably linked into the Rollup for checkpoint proposal, proof verification, pruning, and chain-tip operations. Its functions operate on the calling Rollup’s storage through DELEGATECALL, so direct getter calls on the library are ignored.

Holds tokens allocated for protocol rewards. The canonical Rollup contract, as defined by the Registry, can draw from the implicit reward pool while any address can claim only funds explicitly earmarked to it.

• Roles:
  • canonicalRollup: Rollup
  • registryOwner: Governance

A template for specific slashing payload contracts deployed deterministically to encode one or more slashing actions (validators and amounts) that the Slasher executes.

Core rollup logic contract. It processes checkpoint proposals, verifies ZK proofs for state transitions, manages data availability, and coordinates validator selection and chain tip updates.

• Roles:
  • getSlasher: Slasher the active Slasher authorizes the call under its own execution rules; ultimately Governance the active Slasher authorizes the call under its own execution rules, SlashingProposer the active Slasher authorizes the call under its own execution rules
  • owner: Governance

Executes payload actions submitted by the authorized slashing proposer or Governance. Execution is blocked while slashing is disabled or when the vetoer has vetoed the payload; voting and execution-delay rules are enforced by the proposer, while Governance can bypass the proposer.

• Roles:
  • governance: Governance slashing is enabled and the payload has not been vetoed
  • proposer: SlashingProposer matching ballots meet the proposer quorum, the execution delay has elapsed, the voting round is still within its lifetime, slashing is enabled, and the payload has not been vetoed
  • vetoer: SlashVeto Council

Library immutably linked into the Rollup for sequencer and prover reward accounting. Its functions operate on the calling Rollup’s storage through DELEGATECALL, so direct getter calls on the library are ignored.

Library immutably linked into the Rollup for validator entry, exits, slashing, and Slasher rotation. Its functions operate on the calling Rollup’s storage through DELEGATECALL, so direct getter calls on the library are ignored.

Provides a fallback mechanism for block production if the primary sequencer committee fails or censors. Candidates post a bond of 332,000,000 AZTEC and enter the candidate set. For each hatch, the contract snapshots the eligible set and uses RANDAO to select one designated proposer; posting a bond does not grant immediate proposal rights. If the designated proposer fails to propose and prove, their bond is slashed by 9,600,000 AZTEC. The minimum tax deducted from their bond is 1,660,000 AZTEC, even if the proposal is successful. The escape hatch regularly opens every 112 epochs, given there are any eligible bonded candidates.

• Roles:
  • getRollup: Rollup

Manages the inflation and minting schedule of the Aztec token. It enforces an annual percentage cap and mints new tokens for the budget.

• Roles:
  • owner: ProtocolTreasury; ultimately Governance

Central directory that tracks the current ‘canonical’ (active) Rollup contract address and key system contracts like the Reward Distributor.

• Roles:
  • owner: Governance

Holds the protocol’s funds controlled by Governance. It acts as a timelocked executor for spending or relaying transactions approved by the DAO.

• Roles:
  • governance: Governance GATED_UNTIL has passed, the oldest unmarked Governance proposal was created after the ATP-derived activation timestamp, and markNext was not called in the same block

Implementation registered by the ATP Registry for upgradeable staker proxies that manage locked AZTEC positions.

AZTEC token contract

• Roles:
  • owner: CoinIssuer

Central staking manager independent of Rollup implementations. Sequencers deposit stake here through their chosen Rollup contract. Their stake is then transferred to the Governance contract and activated for voting. The GSE tracks which rollup instance validators are securing, and gives them an option to automatically move to the latest Rollup version.

• Roles:
  • getLatestRollup: Rollup
  • owner: Governance

AZTEC token-position Registry referenced by the ProtocolTreasury for its activation cutoff and by other ecosystem vesting contracts.

• Roles:
  • owner: EOA 1

Facilitates L2 to L1 communication. It stores the roots of L2 to L1 message trees per epoch, which are inserted by the Rollup contract. Users and portals can consume these messages on L1 by providing a Merkle proof against the stored root. A nullifier bitmap prevents double consumption.

• Roles:
  • rollup: Rollup

Facilitates canonical L1 to L2 communication. It accepts messages (including fee asset deposits) from L1, accumulates them in an append-only frontier tree per checkpoint, and forces the Sequencers and the Rollup contract to sequentially consume the roots of these message trees, ensuring message inclusion.

• Roles:
  • rollup: Rollup

One-way gas bridge: Escrows the fee asset (AZTEC) used to pay for L2 mana (gas). Users deposit tokens here, which are minted on L2 via the Inbox. The Rollup contract holds exclusive rights to withdraw tokens from this portal to distribute them as rewards to L1 sequencers and provers. Apart from that, this escrow does NOT afford a way to withdraw tokens.

• Roles:
  • rollup: Rollup