After consulting with @avalabsofficial, we @UMichBlockchain have released a proposal on the Uni forums describing why this deployment is important
Let’s break down the proposal step by step👇
The urgency behind this proposal is due to the impending license expiration
After April 1st, anyone can legally fork Uni v3 code and use it for commercial purposes
Large chains like Avalanche will see a rapid influx of v3 copycats
This will dilute the market on those chains
So it’s paramount for Uniswap v3 to get ahead of the competitors by launching on large chains before duplicates arise
On Avalanche specifically, we know that duplicate chains will spring quickly because it already has lots of liquidity ($950M TVL) and innovation (281+ protocols)
One of the reasons for Avalanche’s continual growth is its novel architecture
It is broken into three parts: P-Chain, C-Chain, & X-Chain
This 3-pronged setup optimizes for scalability and interoperability
The three chains compose a consortium of validators called the Primary Network
It is responsible for Avalanche’s security
Plus, the security easily compounds because increasing the # of validators does not sacrifice block time
This allows for higher decentralization over time
In Q4 2022, Avalanche’s Nakamoto coefficient increased from 30 to 32
This surpass most other L1s
Plus, the chain currently touts a whopping 1,226 validators & over 233M AVAX tokens staked
These are all signs of a robust L1
Avalanche also permits high scalability via its ecosystem of subnets
Like Ethereum’s L2s, subnets allow for outsourcing blockspace from the Primary Network to alternative blockchains
As congestion increases on the EVM-compatible C-Chain, projects will create their own subnet
The beauty of subnets is that they enable launching application-specific blockchains w/t full customizability
This grants builders control over their dev stack
All subnets can specify their own execution logic, fee regime, state, networking, and security
Large protocols that initially relied on the C-Chain are now migrating to their individualized subnets
But it may take some time for this approach to garner adoption and be fully vetted
The Uni DAO can decide to opt into a multi-bridge system in the future
But for an agile deployment, we believe that LayerZero is the best solution
Another reason for using LayerZero is their existing relationship with Avalanche
The first use case of Omnichain Fungible Token (OFT) transfer has been active for nearly 4 months on Avalanche, enabling a composable, unified liquidity system for BTC
The LayerZero-Avalanche relationship is in part why @LayerZero_Labs has volunteered to take care of the technical deployment of v3 on Avalanche
Again, our goal is for this process to take the path of least resistance due to the timely nature of the proposal
But is LayerZero safe to use?
In short, yes.
- LZ is supported by thousands of cross-chain builders w/t over 2k contracts deployed on mainnet
- Has ~700 unique apps
- ~2M total messages
- ~$5B txn volume
- And billions of dollars in TVL
The two main components for LZ messaging are the Oracle and the Relayer
The Oracle sends block headers from the source chain to the destination chain
The Relayer sends txn proofs from the source chain to the destination chain
The Oracle and Relayer work together to pass messages between chains
But the underlying assumption behind this model is that the two entities don’t collude
If they do, then the entire system falls apart
So what makes sure that they don’t collude?
Unlike other bridges, LZ doesn’t pose an economic stake or bond to punish malicious actors via a slashing mechanism
Instead, if the default oracle-relayer configuration is compromised, then there is a reputational backlash for those running the Oracle and Relayer
With a default configuration, LZ runs the Relayer
And Chainlink runs the Oracle
The Chainlink DON would have to actively collude with the LayerZero Labs Relayer at the same time to enable passing of a malicious message
If LZ and Chainlink collude, then both will take an enormous hit to their reputations
This makes the incentive of collusion minimal
Plus, if Uniswap does not want LZ or Chainlink to run either one or both of the Relayer or Oracle, Uniswap can do so itself
LZ code is also set in stone
The smart contracts are not upgradable
This is a big deal since most exploits occur due to bugs in code–not due to malicious actors colluding
And the easiest way to introduce new bugs is to upgrade the baseline code
It’s therefore important for the current code to be pristine
How do we judge code to be bug free?
Audits.
LZ has been audited over 35 times AND reviewed numerous times internally by the @LayerZero_Labs team
Plus, LZ’s current track record is very clean
They’re the only major cross-chain messaging protocol with billions in TVL to not be exploited
And as a further safeguard, LZ has the largest live bug bounty program in the industry ($15M)
So, because of Avalanche’s continual expansion and growing DeFi ecosystem, along with LZ’s robust cross-chain messaging architecture, we believe that it’s finally time for @Uniswap to deploy on Avalanche
Let’s break down the politics behind the recent proposal👇
It all started in December
@ILIA_0x released a proposal draft about launching Uniswap v3 on @BNBCHAIN
The reason behind this proposal was to ensure that Uniswap became the de facto DEX on BNB Chain prior to Uniswap’s license expiration–even taking over @PancakeSwap
What is the Uniswap license?
In short, Uniswap put in place a Business Source License in 2021 to prevent others from forking their source code
The license expires this April
After April, anyone can copy and paste Uni v3 code onto BNB Chain (or any other chain) and make $$$
General-purpose L2s w/o major differentiation leads to an oversaturated market
We have seen this previously with L1s. Every new L1 claims to be an “Ethereum killer”…but to no avail…we all know who is king
The same principle of avoiding market saturation applies to L2s
Although we will see one or two successful general-purpose L2s, it is more likely that L2s as a category will truly succeed if they aim to provide unique, special-purpose features