Aztec Connect

Validity proofs ensure state correctness

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. Once the proof is processed on the Ethereum blockchain the L2 block is instantly finalized.

1. RollupProcessorV2.sol#L706 - Etherscan source code

Zero knowledge SNARK cryptography is used

Despite their production use ZK-SNARKs are still new and experimental cryptography. Cryptography has made a lot of advancements in the recent years but all cryptographic solutions rely on time to prove their security. In addition ZK-SNARKs require a trusted setup to operate.

• Funds can be stolen if the cryptography is broken or implemented incorrectly.

1. Verifier28x32.sol#L150 - Etherscan source code

All data required for proofs is published on chain

All the data that is used to construct the system state is published on chain in the form of cheap calldata. This ensures that it will always be available when needed.

1. RollupProcessorV2.sol#L686 - Etherscan source code

The system has a centralized operator

Only specific addresses appointed by the owner are permitted to propose new blocks during regular rollup operation. Periodically a special window is open during which anyone can propose new blocks.

• MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

1. RollupProcessorV2.sol#L692 - Etherscan source code

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. Periodically the rollup opens a special window during which anyone can propose new blocks.

• Users can be censored if the operator refuses to include their transactions and users lack resources to propose blocks themselves.

1. RollupProcessorV2.sol#L697 - Etherscan source code
2. RollupProcessorV2.sol#L697 - Etherscan source code

Regular withdraw

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.

1. RollupProcessorV2.sol#L1042 - Etherscan source code
2. RollupProcessorV2.sol#L1206 - Etherscan source code

Payments are private

Balances and identities for all tokens on the Aztec rollup are encrypted. Each transaction is encoded as a zkSNARK, protecting user data.

1. Fast Privacy, Now - Aztec Medium Blog