Summary Value Secured Onchain costs Milestones & Incidents Risk analysis Stage Data availability State derivation State validation Upgrades & Governance Updates Operator Withdrawals Other considerations Smart contracts

Zk.Money v2 (Aztec Connect)

This project is archived and no longer maintained.

Badges

About

Aztec Connect is an open source layer 2 network that aims to enable affordable, private crypto payments via zero-knowledge proofs.

Total Value SecuredTVS

$0.000.00%

Past day UOPSDaily UOPS

No data

Stage

Type

ZK Rollup

Purposes

Payments, Privacy

Tokens breakdown

Value secured breakdown

0.00% with additional trust assumptions

View TVS breakdown

Sequencer failureState validationData availabilityExit windowProposer failure

Explore more in Discovery UI

About

Aztec Connect is an open source layer 2 network that aims to enable affordable, private crypto payments via zero-knowledge proofs.

Value Secured View TVS breakdown

Exclude restricted RWA tokens

Total

Canonically BridgedCanonically Bridged ValueCanonical

Natively MintedNatively Minted TokensNative

Externally BridgedExternally Bridged ValueExternal

ETH & derivatives

Stablecoins

BTC & derivatives

Other

View TVS breakdown

Onchain costs

The section shows the operating costs that L2s pay to Ethereum.

2023 May 01 — 2026 Jun 16

Total cost

$104.82 K

Avg cost per L2 UOP

No data

Avg cost per day

$303.83

Milestones & Incidents

Aztec operator sunset

2024 Apr 30th

Aztec stops rollup operators, renouces ownership. Users must run the Rollup manually to withdraw.

Learn more

Introducing Noir

2022 Oct 6th

Noir - programming language for zero-knowledge proofs, has been introduced.

Learn more

Risk analysis

EOL: Aztec team shut down their offchain rollup infrastructure on March 31st, 2024. Onchain 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.

Sequencer failureState validationData availabilityExit windowProposer failure

Sequencer failure

Self sequence

In the event of a sequencer failure, users can force transactions to be included in the project’s chain by sending them to L1. Proposing new blocks requires creating ZK proofs.

State validation

Validity proofs (SN)

SNARKs are succinct zero knowledge proofs that ensure state correctness, but require trusted setup.

Data availability

Onchain

All of the data needed for proof construction is published on Ethereum L1.

Exit window

∞

Users can exit funds at any time because contracts are not upgradeable.

Proposer failure

Self propose

If the Proposer fails, users can leverage the source available prover to submit proofs to the L1 bridge.

Stage

Zk.Money v2 (Aztec Connect) is a

Stage 2

ZK Rollup.

Learn more about Stages

Please keep in mind that these stages do not reflect project security, this is an opinionated assessment of project maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.

Data availability

All data required for proofs is published onchain

Since EOL this is only true if the user themself runs the rollup locally and publishes the data.

RollupProcessorV3.sol#L686 - Etherscan source code

Learn more about the DA layer here:

Ethereum

State derivation

Node software

The entire stack’s source code is housed in a single monorepo, which can be found here. For instructions on running the node, please refer to this readme. Since EOL the aztec-connect-ejector can be used to run a rollup instance and withdraw.

Compression scheme

No compression is used.

Genesis state

The genesis file is available here, and it includes accounts from zk.money as well.

Data format

The code to decode onchain data can be found here

State validation

Validity proofs

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.

RollupProcessorV3.sol#L706 - Etherscan source code

Upgrades & Governance

Past upgrades

The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.

Count of upgrades

Last upgrade

2y 2mo ago

Avg upgrade interval

1y 4mo

Updates

2024 May 01, 07:44 UTC

11changes

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.

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"
	}

2024 April 10, 11:32 UTC

High severity

12changes

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.

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.

-	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.

2024 February 28, 12:54 UTC

4changes

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) {
	}

2023 October 13, 08:09 UTC

4changes

Verification keys update.

-	Status: DELETED
	contract Verifier28x32 (0xB656f4219f565b93DF57D531B574E17FE0F25939) {
	}

	contract RollupProcessorV2 (0xFF1F2B4ADb9dF6FC8eAFecDcbF96A2B351680455) {
	values.verifier:
-	"0xB656f4219f565b93DF57D531B574E17FE0F25939"
+	"0x71c0Ab7dF00F00E4ec2990D4F1C8302c1D178f69"
	}

+	Status: CREATED
	contract Verifier28x32 (0x71c0Ab7dF00F00E4ec2990D4F1C8302c1D178f69) {
	}

Operator

No operator

Only specific addresses appointed by the owner were permitted to propose new blocks during regular rollup operation. Now that the system is EOL, the rollup can only be processed locally by volunteers.

Users can force any transaction

Because the block production is open to anyone if users experience censorship from the operator they can propose their own blocks which would include their transactions.

Withdrawals

EOL: Manual withdrawal using Aztec Connect Ejector

EOL: Aztec team announced they are going to shut down the 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.

Aztec Connect Ejector - Codespace template for running the Aztec Connect rollup.

Regular withdraw (disabled)

The user initiates the withdrawal by submitting a transaction on L2. When the block containing that transaction is proven on L1 the assets are automatically withdrawn to the user.

Other considerations