# Multichain Expansion

**URL:** <https://gov.gmx.io/t/multichain-expansion/454>\
**Category:** Proposals\
**Created:** [July 24, 2022, 8:57pm UTC](https://gov.gmx.io/t/multichain-expansion/454 "2022-07-24T20:57:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gkatala](https://sea2.discourse-cdn.com/flex020/user_avatar/gov.gmx.io/gkatala/32/146_2.png) [@Gkatala](https://gov.gmx.io/u/Gkatala)\
**Post date:** [July 24, 2022, 8:57pm UTC](https://gov.gmx.io/t/multichain-expansion/454/1 "2022-07-24T20:57:37Z")

</div>

It is only natural that after succeeding in the Avax C-chain and Arbitrum that GMX expands to other networks such as Aurora network and Polygon that way the protocol can attract more users easily because these are EVM compatible blockchains.

---

<div class="post-metadata">

**Author:** ![Tano](https://sea2.discourse-cdn.com/flex020/user_avatar/gov.gmx.io/tano/32/66_2.png) [@Tano](https://gov.gmx.io/u/Tano)\
**Post date:** [July 25, 2022, 8:02pm UTC](https://gov.gmx.io/t/multichain-expansion/454/2 "2022-07-25T20:02:46Z")

</div>

Team already said PvP AMM was probably gonna be on a new chain, because they don’t want to go to another chain without another product.

---

<div class="post-metadata">

**Author:** ![randomishwalk](https://sea2.discourse-cdn.com/flex020/user_avatar/gov.gmx.io/randomishwalk/32/128_2.png) [@randomishwalk](https://gov.gmx.io/u/randomishwalk)\
**Post date:** [July 26, 2022, 3:20am UTC](https://gov.gmx.io/t/multichain-expansion/454/3 "2022-07-26T03:20:19Z")

</div>

If you look at most protocols that operate across chains, the activity + protocol economics tend to be heavily skewed towards one or two chains. See curve and sushiswap for example: [https://cryptofees.info/](https://cryptofees.info/)

Also I don’t think it’s as simple as “press a button” and _poof_ you deploy to any EVM-chain. There’s operational overhead + incremental marketing (aka token emissions) spend that comes with operating across different chains that I think doesn’t make this a no-brainer type of decision.

That said, I think the team has expressed interest in deploying to ZKRs down the line given some of the unique latency/composability/scalability/privacy properties that may be unique to these types of execution environments.