# Deploy Uniswap V3 to zkSync

**URL:** <https://gov.uniswap.org/t/deploy-uniswap-v3-to-zksync/17649>\
**Category:** Requests for Comment\
**Created:** [September 13, 2022, 2:58pm UTC](https://gov.uniswap.org/t/deploy-uniswap-v3-to-zksync/17649 "2022-09-13T14:58:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![devinwalsh](https://sea2.discourse-cdn.com/flex016/user_avatar/gov.uniswap.org/devinwalsh/32/9640_2.png) [@devinwalsh](https://gov.uniswap.org/u/devinwalsh)\
**Post date:** [September 13, 2022, 4:25pm UTC](https://gov.uniswap.org/t/deploy-uniswap-v3-to-zksync/17649/2 "2022-09-13T16:25:05Z")

</div>

Thanks for this write up!

A few clarifying questions on the bridge:

- There are two default trustless bridges, one for ETH and one for ERC20 tokens. Do both of these bridges support arbitrary message passing? Which would be used for governance?
- Can you include the proposed language for the License Exemption? And, could the License Exemption include stating bridge which would be approved in the proposal?
- To restate your bridge security summary in other terms, the zkSync bridge inherits Ethereum’s base layer security, confirmed?

And for the sake of beginning to standardize cross-chain deployment proposals, would you mind answering the questions posed in this template [here](https://gov.uniswap.org/t/proposed-template-for-future-cross-chain-deployment-proposals/16611)? At minimum for the bridge questions would be appreciated.

Thank you!

---

_[View the full topic](https://gov.uniswap.org/t/deploy-uniswap-v3-to-zksync/17649)._