Zk.Money v1 (Aztec v1)
About
Zk.Money v1 is an open source layer 2 network that aims to enable affordable, private crypto payments via zero-knowledge proofs.
$4.03 M
6.30%
About
Zk.Money v1 is an open source layer 2 network that aims to enable affordable, private crypto payments via zero-knowledge proofs.
...
Choose token
![](https://assets.coingecko.com/coins/images/279/large/ethereum.png?1595348880)
![](https://assets.coingecko.com/coins/images/9956/large/Badge_Dai.png?1696509996)
![](https://assets.coingecko.com/coins/images/11370/large/Bitcoin.jpg?1696511287)
![](https://assets.coingecko.com/coins/images/325/large/Tether.png?1696501661)
Funds can be stolen if
State validation
ZK proofs (SN)zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.
Exit window
∞Users can exit funds at any time because contracts are not upgradeable.
Sequencer failure
Self sequence![Zk.Money v1 (Aztec v1)](/icons/aztecv1.png)
- The project calls itself a rollup.
- L2 state roots are posted to Ethereum L1.
- Inputs for the state transition function are posted to L1.
- A source-available node exists that can recreate the state from L1 data. Please note that the L2BEAT team has not verified the validity of the node source code. View code
- A complete and functional proof system is deployed.
- Users are able to exit without the help of the permissioned operators.
- In case of an unwanted upgrade by actors more centralized than a Security Council, users have at least 7d to exit.
- Users can exit through the escape hatch mechanism and the rollup contract is immutable.
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. These proofs are then verified on Ethereum by a smart contract.
Zero knowledge SNARK cryptography is used
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 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.
There are three ways to run a node and use the escape hatch: By running the Aztec v2 Ejector during the escape hatch window, 2) by running falafel, 3) by running the SDK in escape hatch mode and connecting to an escape hatch server. The two latter methods are no longer recommended by the aztec team.
No compression scheme is used.
No genesis state is used.
The data format used can be found here
No operator
Only specific addresses appointed by the owner were permitted to propose new blocks during regular rollup operation. Since EOL, these operators are not processing the rollup anymore. Periodically a special window (escape hatch) is open during which anyone can propose new blocks.
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 (escape hatch) 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.
EOL: Manual withdrawal using Aztec v2 Ejector
EOL: Ownership of the rollup contract is irrevocably renounced and operators are not processing the rollup. Assets in the escrow can be manually withdrawn with the Aztec v2 Ejector.
Regular withdraw (deprecated)
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.
The system uses the following set of permissioned addresses:
The system consists of the following smart contracts on the host chain (Ethereum):
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.
Turbo Plonk zkSNARK Verifier.