Search for projects by name or address
Aztec Connect is an open source layer 2 network that aims to enable affordable, private crypto payments via zero-knowledge proofs.
Aztec Connect is an open source layer 2 network that aims to enable affordable, private crypto payments via zero-knowledge proofs.
The section shows the operating costs that L2s pay to Ethereum.
Immutable smart contract exploit
2026 Jun 15th
$~2.3M of assets are drained by exploiting a bug in a smart contract.
Aztec operator sunset
2024 Apr 30th
Aztec stops rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. operators, renouces ownership. Users must run the Rollup manually to withdraw.
In the event of a sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. failure, users can force transactions to be included in the project’s chain by sending them to L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. Proposing new blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. requires creating ZK proofs.
SNARKs are succinct zero knowledge proofs that ensure state correctness, but require trusted setupGeneration of a piece of data that must then be used for some cryptographic protocol to run. Generating this data requires some secret information. The "trust" comes from the fact the secret must be destroyed after the ceremony, otherwise cryptographic properties of the protocol could be broken. Once the data is generated, and the secrets are forgotten, no further participation from the creators of the ceremony is required. There are two types of trusted setups for SNARKs: (i) trusted setup per circuit where it is generated from scratch for each circuit, (ii) trusted universal setup per proving system where it can be used for several circuits..
All of the data needed for proof construction is published on Ethereum L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development..
Users can exit funds at any time because contracts are not upgradeable.
If the ProposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block. fails, users can leverage the source available proverAn entity that generates the cryptographic proof to convince the verifier that the statement is true. In a ZK-Rollup, the prover generates the ZK (validity) proof to submit to the verifier contract. to submit proofs to the L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge..
Since EOL this is only true if the user themself runs the rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. locally and publishes the data.
The entire stack’s source code is housed in a single monorepo, which can be found here. For instructions on running the nodeA software client that participates in the network., please refer to this readme. Since EOL the aztec-connect-ejector can be used to run a rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. instance and withdraw.
No compression is used.
The code to decode onchain data can be found here
Each update to the system state must be accompanied by a ZK proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. These proofs are then verified on Ethereum by a smart contract.
The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.
Discovery rerun on the same block number with only config-related changes.
Discovery rerun on the same block number with only config-related changes.
| + | Status: CREATED |
| contract AztecFeeDistributor (0x4cf32670a53657596E641DFCC6d40f01e4d64927) | |
| +++ description: None | |
| + | Status: CREATED |
| contract DefiBridgeProxy (0xA1BBa894a6D39D79C0D1ef9c68a2139c84B81487) | |
| +++ description: None | |
| + | Status: CREATED |
| contract Verifier28x32 (0xb7baA1420f88b7758E341c93463426A2b7651CFB) | |
| +++ description: None | |
| + | Status: CREATED |
| contract ProxyAdmin (0xC5b735d05c26579B701Be9bED253Bb588503B26B) | |
| +++ description: None | |
| + | Status: CREATED |
| contract Aztec Multisig (0xE298a76986336686CC3566469e3520d23D1a8aaD) | |
| +++ description: None | |
| + | Status: CREATED |
| contract RollupProcessorV3 (0xFF1F2B4ADb9dF6FC8eAFecDcbF96A2B351680455) | |
| +++ description: None | |
Discovery rerun on the same block number with only config-related changes.
Discovery rerun on the same block number with only config-related changes.
| + | Status: CREATED |
| contract AztecFeeDistributor (0x4cf32670a53657596E641DFCC6d40f01e4d64927) | |
| +++ description: None | |
| + | Status: CREATED |
| contract Aztec Multisig (0xE298a76986336686CC3566469e3520d23D1a8aaD) | |
| +++ description: None | |
Aztec connect was sunset on March 31st, 2024 and deposits are disabled (pendingCap = 0, dailyCap = 0). Furthermore, the ownership- and governance roles of the rollup are irrevocably renounced in this update. Assets can still be manually withdrawn with the Aztec Connect Ejector.
Aztec connect was sunset on March 31st, 2024 and deposits are disabled (pendingCap = 0, dailyCap = 0). Furthermore, the ownership- and governance roles of the rollup are irrevocably renounced in this update.
Assets can still be manually withdrawn with the Aztec Connect Ejector.
| - | Status: DELETED |
| contract Emergency Multisig (0x23f8008159C0427458b948c3DD7795c6DBE8236F) | |
| +++ description: None | |
| - | Status: DELETED |
| contract Resume Multisig (0x62415C92528C7d86Fd3f82D3fc75c2F66Bb9389a) | |
| +++ description: None | |
| - | Status: DELETED |
| contract Lister Multisig (0x68A36Aa8E309d5010ab4F9D6c5F1246b854D0b9e) | |
| +++ description: None | |
| contract ProxyAdmin (0xC5b735d05c26579B701Be9bED253Bb588503B26B) { | |
| +++ description: None | |
| values.owner: | |
| - | "0xE298a76986336686CC3566469e3520d23D1a8aaD" |
| + | "0x0000000000000000000000000000000000000000" |
| } | |
| - | Status: DELETED |
| contract Aztec Multisig (0xE298a76986336686CC3566469e3520d23D1a8aaD) | |
| +++ description: None | |
| contract RollupProcessorV2 (0xFF1F2B4ADb9dF6FC8eAFecDcbF96A2B351680455) { | |
| +++ description: None | |
| values.accessControl.DEFAULT_ADMIN_ROLE.members.0: | |
| - | "0xE298a76986336686CC3566469e3520d23D1a8aaD" |
| values.accessControl.OWNER_ROLE.members.0: | |
| - | "0xE298a76986336686CC3566469e3520d23D1a8aaD" |
| values.accessControl.EMERGENCY_ROLE.members.0: | |
| - | "0x23f8008159C0427458b948c3DD7795c6DBE8236F" |
| values.accessControl.LISTER_ROLE.members.0: | |
| - | "0x68A36Aa8E309d5010ab4F9D6c5F1246b854D0b9e" |
| values.accessControl.RESUME_ROLE.members.0: | |
| - | "0x62415C92528C7d86Fd3f82D3fc75c2F66Bb9389a" |
| } | |
RollupProcessorV3: - Make processRollup() public by removing the rollupProviders[msg.sender] check from the function - Remove default asset caps from the initializer (caps are currently set to 0) This allows external participants to withdraw from the rollup and keeps deposits disabled, in line with their March 30 sunset. Verifier28x32: Change of six constants. From chatgpt: - Two of the constants represent the elliptic curve point Q2 - The other four describe the elliptic curve point g2 x These points among others are used to compute the verification key.
rollupProviders[msg.sender] check from the functionThis allows external participants to withdraw from the rollup and keeps deposits disabled, in line with their March 30 sunset.
Change of six constants.
From chatgpt:
Q2g2_xThese points among others are used to compute the verification key.
| - | Status: DELETED |
| contract Verifier28x32 (0x9BDc85491BD589e8390A6AAb6982b82255ae2297) | |
| +++ description: Verifier contract used by the RollupProcessorV2. | |
| contract RollupProcessorV2 (0xFF1F2B4ADb9dF6FC8eAFecDcbF96A2B351680455) { | |
| +++ description: None | |
| upgradeability.implementation: | |
| - | "0x8430Be7B8fd28Cc58EA70A25C9c7A624F26f5D09" |
| + | "0x7d657Ddcf7e2A5fD118dC8A6dDc3dC308AdC2728" |
| implementations.0: | |
| - | "0x8430Be7B8fd28Cc58EA70A25C9c7A624F26f5D09" |
| + | "0x7d657Ddcf7e2A5fD118dC8A6dDc3dC308AdC2728" |
| values.getImplementationVersion: | |
| - | 2 |
| + | 3 |
| +++ description: Address of the ZK verifier. | |
| +++ type: PERMISSION | |
| +++ severity: LOW | |
| values.verifier: | |
| - | "0x9BDc85491BD589e8390A6AAb6982b82255ae2297" |
| + | "0xb7baA1420f88b7758E341c93463426A2b7651CFB" |
| derivedName: | |
| - | "RollupProcessorV2" |
| + | "RollupProcessorV3" |
| } | |
| + | Status: CREATED |
| contract Verifier28x32 (0xb7baA1420f88b7758E341c93463426A2b7651CFB) | |
| +++ description: Verifier contract used by the RollupProcessorV2. | |
On Feb 16, 2024 the verifier has been updated. The difference between the source code contains only changes to hardcoded values. This update is way simpler than AztecV1. The update was done in a single step and the Sequencer of Aztec Connect still posts and processes data without reverts.
On Feb 16, 2024 the verifier has been updated. The difference between the source code contains only changes to hardcoded values. This update is way simpler than AztecV1. The update was done in a single step and the Sequencer of Aztec Connect still posts and processes data without reverts.
| - | Status: DELETED |
| contract Verifier28x32 (0x71c0Ab7dF00F00E4ec2990D4F1C8302c1D178f69) { | |
| } | |
| contract RollupProcessorV2 (0xFF1F2B4ADb9dF6FC8eAFecDcbF96A2B351680455) { | |
| values.verifier: | |
| - | "0x71c0Ab7dF00F00E4ec2990D4F1C8302c1D178f69" |
| + | "0x9BDc85491BD589e8390A6AAb6982b82255ae2297" |
| } | |
| + | Status: CREATED |
| contract Verifier28x32 (0x9BDc85491BD589e8390A6AAb6982b82255ae2297) { | |
| } | |
Only specific addresses appointed by the owner were permitted to propose new blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. during regular rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. operation. Now that the system is EOL, the rollup can only be processed locally by volunteers.
Because the blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. production is open to anyone if users experience censorship from the operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. they can propose their own blocks which would include their transactions.
EOL: Aztec team announced they are going to shut down the rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. infrastructure on March 31st, 2024. Deposits are disabled and ownership of the rollup contract is irrevocably renounced. Assets in the escrow can be manually withdrawn with the Aztec Connect Ejector.
The user initiates the withdrawal by submitting a transaction on L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups.. When the blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. containing that transaction is proven on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. the assets are automatically withdrawn to the user.
Balances and identities for all tokens on the Aztec rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. are encrypted. Each transaction is encoded as a zkSNARK, protecting user data.


Main RollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. contract (immutable) responsible for withdrawals and accepting transaction batches alongside a ZK proof.
Contract responsible for distributing fees and reimbursing gasA virtual fuel used to execute smart contracts on a rollup. The EVM (or other VM within the rollup) uses an accounting mechanism to correspond the consumption of gas to the consumption of computing resources, and to limit the consumption of computing resources. to RollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. Providers.
BridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. Connector to various DeFi Bridges.
Standard PlonkA zk-SNARK proving system introduced by Gabizon, Williamson and Ciobotaru in 2019 that allows proving custom circuits. Plonk is based on KZG polynomial commitments and thus requires a universal trusted setup. zkSNARK VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover..