FinancialsVoteDocsDAO GraphExplore
← All proposals
    ←Previous#30#32Next→

    #31 Deploy Uniswap V3 on BNB Chain

    executed

    Payment Status

    Description

    Deploy Uniswap V3 on BNB Chain

    Description

    0xPlasma Labs is submitting a Governance Proposal to deploy Uniswap v3 to BNB Chain on behalf of the Uniswap Community. The temperature check passed with 20M (80.28%) YES votes and 4.9M (19.72%) NO votes. Here is a link to the Proposal Discussion on Uniswap Governance Forum.

    Proposal

    This proposal will authorize 0xPlasma Labs to deploy the Uniswap v3 protocol to the BNB PoS Chain on behalf of the community. We believe this is the best moment for Uniswap v3 to deploy on BNB PoS Chain, for many reasons (one of them is License expiration).

    About BNB Chain

    BNB Chain is a decentralized, public blockchain that operates using a proof-of-stake (PoS) consensus mechanism. It is designed to support the development and deployment of decentralized applications (dApps) and decentralized finance (DeFi) projects and is powered by the Binance Coin (BNB) token. BNB Chain is operated by Binance, a leading cryptocurrency exchange and blockchain technology company, but is open to participation and contributions from a global community of developers, users, and stakeholders.

    1. BNB Chain has a large and growing user base, providing a potential new market for Uniswap v3.
    2. BNB Chain offers high transaction speeds and low fees, making it a suitable platform for Uniswap’s decentralized exchange services.
    3. Deploying to BNB Chain could help Uniswap to tap into the growing popularity of DeFi in the Binance ecosystem.
    4. BNB Chain offers unique features such as staking and cross-chain support that could enhance Uniswap v3’s functionality.
    5. BNB Chain’s strong governance model and active community could provide valuable support and feedback for the development of Uniswap v3.
    6. Binance, the company behind BNB Chain, has a strong track record of supporting and promoting high-quality projects, potentially providing valuable exposure for Uniswap v3.
    7. Binance has a global presence and a strong brand, which could help increase awareness and adoption of Uniswap v3 among retail and institutional investors.
    8. Binance offers a range of products and services that could be integrated with Uniswap v3, such as the Binance Smart Chain and Binance DEX.
    9. Deploying to BNB Chain could provide opportunities for collaboration and partnerships with other projects on the Binance ecosystem.
    10. BNB Chain strongly focuses on security and compliance, providing a safe and trusted environment for Uniswap v3 to operate.
    11. BNB Chain has a robust ecosystem of dApps and DeFi projects, providing potential opportunities for collaboration and co-development.
    12. BNB Chain’s support for on-chain governance could enable Uniswap v3 to adopt a more decentralized and community-driven development model.
    13. BNB Chain’s support for decentralized autonomous organizations (DAOs) could enable Uniswap v3 to adopt a more decentralized and community-driven business model.
    14. BNB Chain’s strong emphasis on community engagement and participation could provide valuable support and feedback for Uniswap v3.
    15. BNB Chain’s commitment to regulatory compliance could provide valuable support for Uniswap v3 as it seeks to expand into new markets and jurisdictions.
    16. BNB Chain’s support for tokenization and digital asset management could enable Uniswap v3 to offer new services and features for users.
    17. BNB Chain’s a fast-developing ecosystem of decentralized finance dapps and assets.

    DeFi Llama has the overall TVL of DeFi at $49B, of which $29B is on Ethereum. The second largest is BSC at $5B. Pancake Swap has $2.35B in TVL. Dune reports BSC as having 753k weekly users. It is a significant number of users Uniswap should be pursuing.

    Security & Bridges

    Since the Temperature Check, we have discussed with stakeholders within the Uniswap ecosystem, who have expressed a desire to see trust-minimized bridges used for governance for the new Uniswap v3 deployment on BNB Chain. On the Governance Forum, teams presented several bridge solutions: DeBridge, Celer, Wormhole, Layer Zero. Based on the technical assessment of presented bridges by 0xPlasma Labs, GFXLabs, Uniswap Foundation and Uniswap community discussion, we've decided to move forward with another Temperature Check regarding Bridge Infrastructure for BNB Chain, where we listed all four candidates.

    As a result of a very complex discussion and voting on the Snapshot, the community chose the Wormhole bridge for the Uniswap v3 deployment on BNB Chain (with 28M votes), the second place in the vote was taken by the solution from the Layer Zero team (17M votes).

    Here is some major security characteristic of Wormhole bridge:

    1. Does the bridge support arbitrary message passing? Yes, Wormhole is one of the first and longest-serving arbitrary messaging protocols. Since launching on mainnet in August 2021, 185 million messages have been transmitted, with 2 million messages currently generated daily between asset transfers and messaging through organic usage.
    2. Is the bridge secured by a trusted entity, by a multi-sig, or a protocol/set of incentivized nodes? Wormhole is secured by 19 validators (aka: Guardians) who jointly attest to messages. Each message must be attested by at least 13 of the 19 Guardians. Our Guardian set comprises the leading PoS validators, including Staked, Figment, Chorus One, P2P, and more. The complete set of current validators can be found here. As mentioned above Wormhole is making significant progress in developing ZK-based light clients to facilitate completely trustless message-passing.
    3. Does the bridge leverage the security of the source chain (e.g. Ethereum L1) or destination chain, or is the security provided by another third-party entity? Wormhole message security waits for both consensuses to be reached on the source chain as well as additional safety features provided by the bridge. Additionally, Guardians run full nodes to protect the protocol against consensus-level exploits in the connected chains and further reduce contagion risk.
    4. Is it possible for a fraudulent message to be passed to the destination chain? If so, are there any recall mechanisms? All messages passing through Wormhole require a minimum of observation and signing by a majority of the Wormhole Guardian set (13 of 19). While there is currently no out-of-the-box recall mechanism for messages, a minority (7 of 19) Guardians may refuse to sign a fraudulent message and thwart an attack. Simple yet customized message recall functions can be built by individual integrators. An integrator would build “edge contracts” to introduce a time delay on message acceptance, providing an integrator with an opportunity to recall the message before it becomes effective.
    5. What are the ramifications of fraud to the malicious actor? Wormhole’s Guardians are leading PoS validators and some of the most respected names within the validator community. They collectively represent tens of billions in value staked and carry valuable reputations in the communities where they serve. Should they act maliciously (such as a sign or forge fraudulent messages), they risk reputational consequences, external PoS businesses, and ejection from the Wormhole Guardian set. There is little incentive for an individual Guardian to act maliciously. Even if a Guardian were to succeed in forging a fraudulent message, it would not affect the network state because a single signature isn’t enough to establish the super-majority required to gain a quorum. Finally, a fraudulent message would be immediately attributable to the offending Guardian to the rest of the Guardian network.
    6. Has the bridge code been audited? By a third party? What attack vectors and vulnerabilities were identified, if any? Have the identified vulnerabilities been remedied? The bridge has been audited 25+ times by leading audit firms, including Certik, Trail of Bits, and OtterSec, and the cohort of auditors continues to grow. You can see the complete list of auditors and publicized findings here. Those 25 audits are in addition to Wormhole’s already rigorous internal auditing standards, where a team of 6 experienced security engineers regularly perform reviews of the protocol’s security.

    Bridge Infrastructure has a significant part in the multi-chain future of Uniswap v3. We received multiple offers from the biggest bridge providers during the proposal discussion. Uniswap Foundation launched a discussion topic on the forum for technical bridge assessments (The tentative deadline to provide feedback on the process below is Friday, February 17th.), while Celer Team has developed and provided a multi-bridge contract with the support of multiple bridges (Celer, DeBridge, Wormhole). The summary of the current governance proposal progress.

    After the current Governance Proposal passes the voting and deployment on BNB Chain, we plan to continue our research and bridge assessment. As we will find out a new solution we will start a new proposal for updating the current bridge infrastructure.

    License Exemption

    We are requesting an exemption via an Additional Use Grant (license change enacted via the ENS domain uniswap.eth) that would allow the 0xPlasma Labs to use the Licensed Work to deploy it on BNB Chain, a layer 1 EVM compatible blockchain, provided that the deployment is subject to Ethereum layer 1 Uniswap Protocol governance and control. Uniswap V3 will be deployed on BNB Chain by the 0xPlasma Labs through the “Deploy Uniswap V3 Script” 0xPlasma Labs would be permitted to use subcontractors to do this work.

    Timeline

    Following the Governance Proposal, 0xPlasma Labs will be ready to move forward with the Uniswap V3 deployment on BNB Chain immediately, using Wormhole bridge infrastructure for cross-chain governance messaging.

    For55,880,027 66%
    Against28,466,755 34%
    Abstain450,009 1%
    Quorumreached

    Timeline

    1. Pending
    2. Active
       
      block 16,558,461 → 16,598,781
    3. Succeeded
       
    4. Queued
       
    5. Executed
       

    Votes (1,686)

    0x2B1A…5fF4Against · 15,001,526 UNI
    0xe792…Cc2bAgainst · 8,000,024 UNI
    0x8962…d429For · 7,032,880 UNI
    0x88FB…3981For · 5,755,634 UNI
    0x212B…6DB5For · 5,000,000 UNI
    0xa6e8…Eef6For · 4,918,755 UNI
    0x47C1…4770Against · 4,500,000 UNI
    0x13BD…8548For · 3,499,999 UNI
    0x8d07…A265For · 3,301,126 UNI
    0x5d89…9e68For · 3,243,728 UNI
    0x067b…4A76For · 3,100,045 UNI
    0x0703…961bFor · 3,000,109 UNI
    0xB777…E1a5For · 2,500,400 UNI
    0xed11…bb04For · 2,500,005 UNI
    0x553F…2Ac2For · 2,500,004 UNI
    0xB49f…7948For · 2,500,002 UNI
    0x7AE1…E585For · 2,500,000 UNI
    0xdC1F…E432For · 2,500,000 UNI
    0x6fE5…eBf7For · 1,000,000 UNI
    0x6554…1EA3Against · 774,543 UNI
    0xE093…49f8For · 500,000 UNI
    0x5B3b…7c98For · 500,000 UNI
    0xeD2A…aeAFAbstain · 250,000 UNI

    The outcome is already set, voting Abstain.

    0x1E49…1103Abstain · 200,000 UNI
    0x47A1…D080Against · 125,418 UNI
    0x8085…38bdAgainst · 50,000 UNI
    0x0ae2…4281For · 14,714 UNI
    0x314C…6D40Against · 10,007 UNI
    0x48A9…FeB7Against · 2,731 UNI
    0xf1b1…D093For · 2,064 UNI
    0xF484…b4FcFor · 800 UNI

    don't like a16z putting their interests ahead of protocol's more than i dislike BNB, so count me in!

    0x39c7…3Fe2For · 703 UNI
    0x7Eaf…3555Against · 505 UNI
    0x96Ea…C6A4For · 490 UNI
    0xD105…95b2For · 408 UNI
    0x3CfC…5fe9For · 320 UNI
    0x3c00…8Cb5Against · 309 UNI
    0x4053…4f15For · 300 UNI
    0xEf19…58f8For · 288 UNI
    0x4029…7E3FFor · 245 UNI
    0x44c8…3811For · 238 UNI
    0x9D32…2462For · 200 UNI
    0xbe35…072eFor · 200 UNI
    0x2475…38d8For · 197 UNI
    0x6C10…2a11For · 173 UNI
    0xfDC4…352cFor · 165 UNI
    0x7db3…6087For · 124 UNI
    0x5315…5750For · 119 UNI
    0xB0B9…7a4BFor · 119 UNI
    0xde91…07C1For · 109 UNI

    Voting timeline

    Proposal actions

    Caller
    Timelock
    0x1a9C…35BC
    →
    setText→
    PublicResolver
    0x4976…Ba41
    ▶node, key, value
    nodebytes32
    0xa35d592ec6e5289a387cba1d5f82be794f495bd5a361a1fb314687c6aefea1f4
    keystring
    0xPlasma Labs. Uni v3 Additional Use Grant.
    valuestring
    The 0xPlasma Labs (Plasma Alliance OU) is grante… (769 chars)
    The 0xPlasma Labs (Plasma Alliance OU) is granted an additional use grant to use the Uniswap V3 Core software code (which is made available to the 0xPlasma Labs (0xPlasma.eth) subject to license available at https://github.com/Uniswap/v3-core/blob/main/LICENSE (the “Uniswap Code”). As part of this additional use grant, the 0xPlasma Labs (Plasma Alliance OU) receives license to use the Uniswap Code for the purposes of a full deployment of the Uniswap Protocol v3 onto the BNB Chain blockchain. The 0xPlasma Labs (Plasma Alliance OU) is permitted to use subcontractors to do this work. This license is conditional on the 0xPlasma Labs complying with the terms of the Business Source License 1.1, made available at https://github.com/Uniswap/v3-core/blob/main/LICENSE.