$3.72 M
5.46%
...
zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.
All of the data needed for proof construction is published on chain.
1/2 MSig can change Validator.
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.
If the Proposer fails, users can leverage the source available prover to submit proofs to the L1 bridge.
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.
Despite their production use zkSNARKs 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 zkSNARKs require a trusted setup to operate.
Funds can be stolen if the cryptography is broken or implemented incorrectly.
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.
There are two ways to run a node and use the escape hatch: by running falafel, or by running the SDK in escape hatch mode and connecting to an escape hatch server.
No compression scheme is used.
No genesis state is used.
The data format used can be found here
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.
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.
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.
Balances and identities for all tokens on the Aztec rollup are encrypted. Each transaction is encoded as a zkSNARK, protecting user data.
Owner of RollupProcessor and AztecFeeDistributor contracts. Can add or delete rollup providers. Can change the verifier contract. This is a Gnosis Safe with 1 / 2 threshold.
Those are the participants of the Aztec Multisig.
Addresses that can propose new blocks during regular rollup operation.
Main Rollup contract responsible for deposits, withdrawals and accepting transaction batches alongside a ZK proof. This contract stores the following tokens: ETH, DAI, renBTC, USDT.
Contract responsible for distributing fees and reimbursing gas to Rollup Providers.
Turbo Plonk zkSNARK Verifier.
Can be upgraded by: Aztec Multisig
Upgrade delay: No delay
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).