# OIP-2: Multi-chain Deployment of levx.io

- Space: [OhGeez DAO](https://snapshot.box/s:levx.eth.md)
- Author: 0x612ef87bfcd858687160294b0eFFACA0CBA342E2
- State: Closed
- Voting type: Quadratic
- Start: 2022-11-17 08:39 UTC
- End: 2022-11-20 08:39 UTC
- Votes: 15
- Quorum: 10,000 voting power
- Discussion: https://agora.ohgeez.org/proposals/p/multi-chain-deployment-of-levxio
- Open in Snapshot: https://snapshot.box/#/s:levx.eth/proposal/0x620900fc63c9a2bbb98f343842912a9085581cc88e2b072e925c292e30ec2947

## Results

- Only on Ethereum (no L2 deploy): 8.06 voting power, 0.1%
- zkSync as the hub chain: 7,206.73 voting power, 71.6%
- Optimism as the hub chain: 1,306.73 voting power, 13.0%
- Arbitrum as the hub chain: 1,526.24 voting power, 15.2%
- BNB Chains as the hub chain: 12.01 voting power, 0.1%
- Avalanche as the hub chain: 0 voting power, 0.0%
- Fantom as the hub chain: 9.4 voting power, 0.1%

## Proposal

# Motivation
L2 wars seem to have already begun and the public release of zkSync will inflame it. So, levx.io is going to expend to L2s as well not only Ethereum.

# Specification
The protocol is designed for multi-chain support and in the beginning, it'll be deployed on 2 chains:  Ethereum and zkSync. We'll call zkSync the hub chain.
By the way, contracts deployed on two chains are not identical and they have different usages. The hub chain is where [GaugeController](https://github.com/ohgeez-dao/levx-protocol/blob/dev/contracts/GaugeController.sol) resides, which means actual voting happens here and it records all the weights of voted users on each NFTs.
[NFTGaugeFactory](https://github.com/ohgeez-dao/levx-protocol/blob/dev/contracts/NFTGaugeFactory.sol) will be deployed on multi chains so NFT holders can stake it on their own chain, without moving the assets. Ethereum NFTs will be staked only on Ethereum and zkSync ones only on zkSync, etc.
But voting works a little bit differently. Since [GaugeController](https://github.com/ohgeez-dao/levx-protocol/blob/dev/contracts/GaugeController.sol) only exists on the hub chain, users vote for a specific [NFTGauge](https://github.com/ohgeez-dao/levx-protocol/blob/dev/contracts/NFTGauge.sol) on their own chain, then the voting result is automatically sent to the hub chain to finally get recorded on GaugeController. We use [LayerZero](https://layerzero.network/) technology for inter-chain communication.
[Minter](https://github.com/ohgeez-dao/levx-protocol/blob/dev/contracts/Minter.sol) is only on the hub chain as well and new OGZ will only be minted on this chain. For votes happened outside of the hub chain, the rewards(OGZ) will be sent to the voter's wallet on their own chain.
[VotingEscrow](https://github.com/ohgeez-dao/levx-protocol/blob/dev/contracts/VotingEscrow.sol) will be deployed on each chain as well so in any chain, you can lock up your OGZ and receive voting power. Even though contracts are separated on different chains, voting power of 1 veOGZ is equivalent in any chain. From whichever chain you are on, if you vote 1 veOGZ then it'll be recorded as the same 1 veOGZ on the hub chain.

# Expectated Result
1. Voters can save gas to almost 1/100 because voting happens on L2
2. Users of new NFTs on zkSync can onboarded easily
3. We can ride the waves of zkSync in terms of marketing

# Conclusion
I believe zkSync will be the best choice if we deploy to another L2 and that's why I call it the hub chain so that heavy computation happens there.
We could also deploy it on Arbitrum, Optimism, BNB chain, Avalanche, Fantom, etc.

Most voted chain will become the hub chain and will also deployed on other chains voted over 10%.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

