HackMD
Aztec Connect Rollup Deployment Transactions
Deploying the Rollup Contract and Upgradable Proxy
Deployment Address:
https://etherscan.io/address/0xa173bddf4953c1e8be2ca0695cfc07502ff3b1e7
Initial deployment was triggered at Jun-07-2022 09:42:26 PM +UTC in block 14923076. https://etherscan.io/tx/0xbff53984293bee6219735143c495dea6aa190e4ba22b4788914ebd0094ecff0e
Deployment run completes with:
https://etherscan.io/tx/0x0390a1c617aa9f47677b91fac4097fbd47ab75122ed439e99293beb73a5f99a6
Deploying the 28x32 verifier.
As the MockVerifier was deployed, the 28x32 verifier was deployed in following txs:
VerificationKey28x32:
https://etherscan.io/tx/0xf15609b001d239d1a0d78538a37033696bb6f87b3c9dd440591a7456e3c027a9
StandardVerifier: https://etherscan.io/tx/0x9c9128c14cd208780a79853664346fa2d6a7f8e6171b75d996ebf1637d742e04
Resulting in the following deployed contracts:
VerificationKey28x32: https://etherscan.io/address/0x8c3b53f450e53ff14d8c9449465f79ff40668966/advanced#code
StandardVerifier: https://etherscan.io/address/0x07528c46a34d16e4fb7cfa9db7333c521bec8ea2/advanced#code
Note: The verifier looks odd in etherscan because of the linking of internal libraries.
Setting the StandardVerifier with 28x32 Verfication Key Linked
Updating the verifier from MockVerifier to the correct Standard Linked Verifier in block: 14923330 at Jun-07-2022 10:42:45 PM +UTC
https://etherscan.io/tx/0x006f2778f47a4879db80e563ef35aa9de8a038d30ef5b8ee7f8f1706216cbf45
For further clarity you can see that the 28x32 key is indeed used every rollup on Tenderly.
