ZERO Application for Canonical Uniswap V3 Deployment

Proposal Summary

  • The purpose of this post is to apply for canonical Uniswap V3 deployment on ZERϴ
  • All of the Uni v3 contracts have already been deployed
  • No further actions need to be taken by the DAO

About Zerion

Zerion is a leading wallet & infrastructure provider:

  • The wallet of choice for 450k MAU
  • User-friendly design, extensive functionality, and safe navigation
  • An infrastructure provider for 200+ products (Uniswap, Rainbow, SAFE, LIFi, WalletConnect)
  • Top 5 wallets for beginners by Ethereum.org

The biggest PFP collection (Zerion DNA) on mainnet with 350k unique owners.

About ZERO

ZERϴ is a Layer 2 Rollup on ZK Stack with no network fees for Zerion users. It pioneers the concept of a “walletchain” to set a new standard for onchain UX.

ZERϴ does not require users to pay gas which means that dApps can offer new experiences where more interactions are onchain and yet feel as smooth as Web2 ones.

This proposal seeks to verify this Uniswap V3 deployment on ZERO as the canonical version.

Proposal Stakeholders

Proposer: Zerion

Deployer: Reservoir

Bridge Provider: ZERϴ Native Bridge

Target Chain: ZERϴ

Deployment Details

As is the case with all official v3 deployments, this deployment is governed by the Uniswap DAO via ZERϴ’s native bridge. Per the governance process, the UAC will review the deployment and update the text record to include the ZERϴ deployment.

ZERϴ is a ZK-Sync based chain, meaning that calls from L1 route through an “alias” address on the L2. The alias address for the L1 DAO Timelock contract is 0x2BAD8182C09F50c8318d769245beA52C32Be46CD, and this is configured as the owner, exactly the same as ZK-Sync.

Relevant Uni v3 Contracts

v3CoreFactoryAddress: 0xA1160e73B63F322ae88cC2d8E700833e71D0b2a1

multicall2Address: 0x9CA4dcb2505fbf536F6c54AA0a77C79f4fBC35C0

proxyAdminAddress: 0x76d539e3c8bc2A565D22De95B0671A963667C4aD

tickLensAddress: 0x9c7d30F93812f143b6Efa673DB8448EfCB9f747E

nftDescriptorLibraryAddressV1_3_0: 0x30cF3266240021f101e388D9b80959c42c068C7C

nonfungibleTokenPositionDescriptorAddressV1_3_0: 0x8036Aa360D66D15eBf3E9a310393e8E7C92BDcf4

descriptorProxyAddress: 0xB0AB2d31642262F6bF68bF6E2C4FC05bb2C2db6d

nonfungibleTokenPositionManagerAddress: 0x5b15468dFD83cF9192082d4510034c9431bb05eB

quoterV2Address: 0x22B98c8Bdfea8D928101eEC40Af634ff37804997

swapRouter02: 0xD936711eABD2Ce52747d7122757316C7DFe3599b

permit2: 0x6b4420f66De496D18A6c36367cf7f1440fd9289f

universalrouter: 0xF93Ce7C55073aE244f4a5C810924D790C65F742E

Timeline

Uniswap V3 has already been deployed on ZERϴ.

5 Likes

This proposal has successfully completed the 7-day optimistic approval period, confirming the associated contracts as the official v3 deployment on ZERϴ. The UAC will update the v3-deployments.uniswap.eth registry to reflect this addition.

1 Like