[Request for Comment] Deploy a HOP bridge on zkSync V2

Summary

Hello Hop community! We are reaching out to propose supporting zkSync V2 bridging. We will be going live on mainnet in less than 60 days and would be great to have Hop as one of our launch partners.

  • zkSync ecosystem has over 200 projects committed to launching on mainnet, including top DeFi protocols, infrastructure, on/off ramps
  • Deploying on zkSync can onboard new users & increase user activity
  • ZK-rollups rely purely on math to fully inherit the security of Ethereum L1; users can always retrieve funds from the smart contract with no trust involved
  • EVM compatibility increases ecosystem network effect
  • zkSync shares Ethereum ethos with a commitment to decentralization, opensource, and permissive licensing

Proposal

We would like Hop to support fast bridging between zkSync V2 and other chains, particular the other chains in the Ethereum ecosystem.

zkSync, as a zkEVM Layer 2, natively maintains a bridge between Etherium and zkSync. However, we would like to direct users to Hop for bridging between zkSync and the rest of the blockchain ecosystems.

With over 200 projects committed to launching on mainnet we expect to have a significantly robust ecosystem from day 1. This provides a huge economic value to Hop as there will be significant market demand for bridging to and from zkSync.

About zkSync

zkSync is a layer-2 network that eliminates scaling constraints and high transaction costs on Ethereum using zero-knowledge rollup technology (ZK-rollups). It’s an EVM-compatible rollup, meaning existing, battle-tested smart contracts written in Solidity and Vyper can deploy to zkSync with little to no modifications or reaudits while leveraging existing Ethereum tooling and infrastructure.

All funds are held by a smart contract on the mainchain, while computation and storage are performed off-chain. The main idea is that instead of verifying each transaction separately, transactions are rolled up to a single item, which is then verified, approving all them simultaneously.

This SNARK verification is much cheaper than verifying every transaction individually, and storing the off-chain is significantly cheaper than storing it on EVM. Hence enabling a huge boost of scalability (100-200x mainnet capacity) and tx cost savings.

ZK-rollups can offer up to 2000 TPS at peak load and will be extended in the future with off-chain data availability.

Roughly 1/50th of the costs on L1 because it requires the least amount of data to be posted on-chain. Savings could be an order of magnitude more significant as only the final changes to state need to be published. zkSync V1 is has been out for two years and is consistently one of the cheapest Layer 2s for swaps and transfers as measured by https://l2fees.info/

We believe zero-knowledge rollups are the most promising scaling solution for public blockchains, and EVM-compatibility will accelerate developer and retail adoption.

zkSync v2 is expected to be the first zkEVM-compatible rollup to go live on mainnet in less than 60 days.

18 Likes

This would be very good for the ecosystem and community!

4 Likes

having the full range of L2 scaling solutions enables a level playing field for competition. Has my vote

7 Likes

太好了 我支持 我特别需要 zkSync V2 上部署 HOP 桥接器

1 Like

zkSync was one of the first L2s I personally truly used at scale. Gitcoin donations made it realy popular and I know many people who got into crypto through it.

rotki does part of its payments through zksync. Getting in an out of it is at the moment quite annoying.
Deploying a HOP bridge there would be a win for both HOP and for zkSync users.

I am definitely voting for this proposal.

3 Likes

This is a no brainer for me (i.e. voting yes). Although I understand some of the controversy around whether this is truly a “zkEVM,” the same controversy can be extended to whether certain optimistic rollups that Hop already supports are truly optimistic rollups. In other words, zkSync v2 is clearly an EVM, Ethereum aligned roll-up that Hop should support. I imagine it will onboard a significant amount of TVL and if Hop isn’t deployed on zkSync, that TVL will find another way to route over there.

1 Like

Deploying a bridge to zkSync V2 seems like a great way to diversify within the rollup space with Optimism and Arbitrum’s top competitor. I also voted in favor of this proposal.

1 Like

LFG i agree on this proposal

1 Like

I am definitely voting for this proposal.

1 Like

I believe this is a faithful project.

1 Like

This proposal passed Snapshot with an overwhelming majority. The next step would be for a delegate with 1 million + HOP to sponsor this proposal for an on-chain vote.

3 Likes

This proposal has advanced to an on-chain vote. The poll will close on Nov 28.

If you hold HOP, and have an opinion, please consider voting here.

1 Like

This on-chain vote succeeded with 99 addresses providing ~99.98% approval. Thank you to everyone who voted.

Attn: @cwhinfrey @lito.coen et al

3 Likes

Voted yes on this proposal, I believe that HOP expanding to zkSync would not only be beneficial for the zkSync ecosystem as a whole but also for Hop itself - there are alternatives, such as Orbiter, that already have this integration in place. In favour of this proposal.

excellent for all of us as community