Deploy Sushiswap on Polygon zkEVM Mainnet

Deploy Sushiswap on Polygon zkEVM Mainnet

Point of Contact: Jack Melnick, TG: @jackmelnick, email:

Overview of proposal

We propose Sushiswap to deploy Sushiswap’s protocol to the Polygon Zero Knowledge Ethereum Virtual Machine rollup known as “zkEVM” on behalf of the community.

We believe this is the right moment for Sushiswap to deploy on Polygon zkEVM, for several major reasons:

· Polygon zkEVM is a new zk-rollup that provides Ethereum Virtual Machine (EVM) equivalence (opcode-level compatibility) for a transparent user experience and existing Ethereum ecosystem and tooling compatibility. Additionally, speed of fraud proofs allows for near instant bridging of funds via the native smart-contract bridge (rather than waiting seven days).

· An Ethereum L2 scalability solution utilizing cryptographic zero-knowledge technology to provide validation and fast finality of off-chain transaction computations.

· A new set of tools and technologies were created and engineered and are contained in this organization, to address the required recreation of all EVM opcodes for transparent deployment and transactions with existing Ethereum smart contracts.

· Polygon is aligned with Ethereum and its values.

· Sushiswap is already deployed on PoS with good success

· Sushiswap can gain market-share through early mover advantage

About Polygon Labs

Polygon Labs is the leader in Ethereum scaling and infrastructure development. It is rapidly helping build a suite of protocols that will offer developers easy access to all major scaling and infrastructure solutions:

· L2 solutions/rollups (Polygon zkEVM, Polygon Miden 1); and

· Sidechains (Polygon PoS).

The Polygon PoS network is by far the most adopted scaling effort in the Ethereum ecosystem, with 3,000+ applications hosted, 1B+ transactions processed, 100M+ unique user addresses and ~$5B+ in assets secured.


There’s significant value in Sushiswap being available on an EVM equivalent ZK rollup. Deploying early on zkEVM helps solidify Sushiswap’s place as a leading DEX and a thought leader.

Importantly, it will help grow a large list of projects that can be built on Sushiswap.

Additionally, given the community and user uptake Sushiswap has seen on Polygon PoS, it’s only natural to make its deployment on Polygon zkEVM a priority.

Partner Details

Polygon Labs

This proposal is being made by Hamzah Khan, Head of DeFi, an employee of Polygon Labs. Polygon Labs is a legal entity focused on the ecosystem growth and maintenance of the suite of Polygon networks.

Partner Legal

The legal entity that is supporting this proposal is Polygon Labs Services (Switzerland) AG, a Swiss corporation known as “Polygon Labs”.

Delegate Sponsor

There is no delegate co-authoring or sponsoring this proposal. Instead, this is a proposal submitted by Hamzah Khan of Polygon Labs to support the growth of Polygon as part of the overall Polygon community.

Conflict of Interest Declaration

There are no existing financial or contractual relationships between Polygon Labs and any of Sushiswap’s legal entities, including Sushiswap , SUSHI tokens, nor investments of Sushiswap.

What potential risks are there for this project’s success? How could they be mitigated?

Risk Profile

Deploying on zkEVM should pose minimal risks, relative to deploying on alternate blockchains. As an Ethereum Layer Two, it uses Zero Knowledge proofs to inherit Ethereum’s core safety, while allowing developers to easily deploy existing EVM codebases. The bridge has been disintermediated, and Sushiswap can expect reputable Oracle providers to be available as data providers from Day One. Polygon’s zkEVM testnet has been running for the past six months. Additionally, the deployment has been audited multiple times, by auditors including Spearbit and Hexens. Risks are outlined in detail here: Welcome to zkEVM | Polygon Wiki.

Protocol security

Does the bridge support arbitrary message passing? Yes

Is the bridge secured by a trusted entity, by a multi sig, or a protocol/set of incentivized nodes? No trusted entity, multi-sig, or a protocol/set of incentivized nodes, only L1 and L2 security. Pure smart contract interactions only.

Does the bridge leverage the security of the source chain (e.g. Ethereum L1) or destination chain, or is security provided by another third party entity? All based on L1 and L2. L2 security is based on the L1.

Is it possible for a fraudulent message to be passed to the destination chain? If so, are there any recall mechanisms? There are two ways to use the bridge, which do not allow for a fraudulent message to be passed to the destination chain:

· Native supported messages: Allow only bridging of ERC-20 and ETH. There is no fraudulent message that can be passed.

· Custom Messages: Custom receiver logic on the other side of the bridge. When you send a message, the message needs to be received by a smart contract, so you have to build the receiver smart contract, which is specific to the logic of that smart contract. The security is up to the person building the receiver smart contract. These custom messages do not take custody of any funds. All that is known is that the message will pass the bridge if implemented correctly. The bridge is just the message carrier.

What are the ramifications of fraud to the malicious actor? There is no ramification to contemplate due to there being no possibility of passing a fraudulent message to the destination chain, as described above.

Has the bridge code been audited? As part of the main zkEVM audits, the bridge code was audited.


Launch Sushiswap on Polygon zkEVM


Do Nothing


  • For
  • Against

0 voters