Author: Joe Andrews
Aztec2.0 has been online for 6 months. Our system has transferred $5.5M in value since launch, making private transfers an affordable option. Our system has sent more than 21,000 transactions, but we set a maximum transfer limit of 1 eth for a single transaction, because this technology is experimental after all, and we want to give users more protection.
Today, we are proud to announce the next set of upgrades for the Aztec network. These upgrades mean that the first privacy rollup on Ethereum has passed the experimental stage and has reached the actual combat stage.
Validator upgrades and bug fixes
Increase transfer amount
Private key change for zk.money
UI upgrades
Validator upgrades and bug fixes
Since launch, Aztec has retained control of the rollup smart contract in order to upgrade validator contracts in case of bugs.
Our approach is to continually audit the protocol internally and publicly issue bug bounties. As a result, we have fixed 5 issues with our ZK-SNARK circuit. More details can be found here. Thanks to this escalation control, all bugs were mitigated without any loss of funds.
The hard work during this period has increased our confidence in the security of this system, and we sincerely thank all users who used this system in the early stages. Creating an environment where the code can be publicly audited and investing real money brings increased security for all users.
Raise the limit - $100,000 per trade!
We're increasing the transfer limit to $100,000 per transaction! Our team is very confident in our cryptography and contracts, and is ready to make this system carry a larger volume. Aztec 2.0 now supports three types of assets, and the transfer amount has been increased:
30 ETH
10 0000 DAI
2 renBTC
private key change
We are improving the user interface of zk.money to reflect the increase in transfer amounts. Our goal is to better protect the safety of users' funds
Change user's signature message
Previously, zk.money required users to sign a hexadecimal string to generate an Aztec private key. This is a bad practice. Many thanks to Franziska Heintel for calling us on EthCC and pointing out this issue.
image description
- New signature message on zk.money -
Do not store payment keys in the browser
Before that, zk.money would store Aztec payment keys in the browser. Now, for security, the payment key is derived before every transaction is sent. It is much safer to derive a key for each transaction, which can prevent the risk of device loss and malicious access, although the user experience will be worse.
For the next six months, your Aztec payment key will become your Ethereum private key, significantly improving user experience.
To assist with this change, all zk.money users will migrate their accounts. Both previous and private transactions will be free for the next three weeks.
UI upgrade - zk.money
Based on the common feedback we gathered in our Discord channel, we have made some adjustments to the function of sending L1 payments on zk.money.
The Aztec network has internal transactions, so the private set of unmasked transactions sent to L1 is the collection of hidden transactions and the source of unmasked transactions. In order to facilitate user operations, users will now be unblocked into a convenient privacy set - any amount can be used, but privacy may be reduced.
Original link:
Original link:
https://medium.com/aztec-protocol/aztec-2-0-updates-100-000-transaction-limits-more-e55c17c0ecf8
