# Continue the Uniswap V3 deployment on Gnosis Chain with different bridge provider

**URL:** <https://gov.uniswap.org/t/continue-the-uniswap-v3-deployment-on-gnosis-chain-with-different-bridge-provider/20724>\
**Category:** Requests for Comment\
**Created:** [March 13, 2023, 11:41am UTC](https://gov.uniswap.org/t/continue-the-uniswap-v3-deployment-on-gnosis-chain-with-different-bridge-provider/20724 "2023-03-13T11:41:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![eek637](https://sea2.discourse-cdn.com/flex016/user_avatar/gov.uniswap.org/eek637/32/7037_2.png) [@eek637](https://gov.uniswap.org/u/eek637)\
**Post date:** [March 13, 2023, 8:08pm UTC](https://gov.uniswap.org/t/continue-the-uniswap-v3-deployment-on-gnosis-chain-with-different-bridge-provider/20724/4 "2023-03-13T20:08:30Z")

</div>

The Kava vote is not tied to a bridge provider per the latest [update](https://gov.uniswap.org/t/deploy-uniswap-v3-on-kava-chain/20449/5) in that thread. I’d suggest going the same route post-assessment. We just voted against Avalanche for the same reason.

At this point, rushing to deploy before the results of the bridge assessment committee come back yields zero benefit to Uniswap, marginal benefit to the destination chain, and tangible benefits to the bridge provider.

---

_[View the full topic](https://gov.uniswap.org/t/continue-the-uniswap-v3-deployment-on-gnosis-chain-with-different-bridge-provider/20724)._