With the Snapshot vote live, the NEW summed up some advantages and considerations for different voting options.
Disclaimer
All of the proposals meet baseline expectations and requirements (e.g. avoiding vendor lock-in and minimizing centralization risks).
The following list of advantages and considerations is opinionated, highlights various aspects, and constitutes/attempts to proclaim neither the best nor the worst possible options.
—
LayerZero
Proposal link:
Advantages:
- Commitment to trustless ZK technology for validation
- The Pre-Crime module for monitoring and alerting
- The world’s largest bug bounty program
- Proven track record (2 years, $30B+ value transferred)
- Clear improvement from both the previous assessment by Uniswap and the previous proposal for Lido
- A member of BNB Chain DeFi League
Considerations:
- Recently proposed LayerZero V2 addressing centralization concerns about Oracles and Relayers appeared quite recently for in-depth analysis and production trail
- The Pre-Crime module is proprietary and might introduce additional exposure to censorship risks
- Mentioned zk technology is green or hasn’t developed yet (e.g. zkOracle by the =nil; Foundation)
- OFT impl and Endpoints introduce a dependency on the LZ code licensed with LZBL-1.2 (not an open-source license)
Wormhole x Axelar
Proposal link:
Advantages:
-
Experience with Lido-related bridging projects (bETH, Neutron, Solana, cross-chain liquidity hops, etc.)
-
Both providers were recommended by the Uniswap Bridge Assessment Committee (UBAC)
-
Open-source Apache 2 license
-
Abstracts away endpoints making it possible to onboard new bridge providers through adapters, starting with two bridge providers
-
Commitment to the Lido DAO governance plug-ins and forwarding
-
Collaboration between the two bridge providers, rather than competition
Considerations:
- Newly developed and to-be-audited interface contracts
- Doesn’t follow any of the proposed cross-chain token standards (e.g. xERC-20)
- The governance forwarding implementation isn’t presented
Chainlink CCIP
Proposal link:
Advantages:
- Re-using battle-tested DON for the validation layer having the strongest DeFi integration case
- Experience with Lido-related bridging projects (exchange rate feeds and price feeds)
- Clearly defined architecture and roadmap
- A member of BNB Chain DeFi League
- Trusted by Circle’s CCTP for USDC cross-chain transfers
Considerations:
-
Limited exposure to 3rd parties research — reports haven’t been published yet, e.g. hasn’t been assessed yet by the UBAC
-
Dependency on the BSL License in the code and legal disclaimers
-
BugBounty terms are not usual ‘Unlike other bug bounty programs on Immunefi, all bug report submissions, including associated vulnerabilities, become the exclusive property of Chainlink Labs‘
-
Unusual fees model with LINK token, surcharge for other assets, and subject to change
Hyperlane & HadronLabs
Proposal link:
Advantages:
- Compatibility with the upcoming multibridge wstETH on Neutron design
- Experience with Lido on X projects
- Bridge aggregation focused approach
Considerations:
- The mentioned wstETH on Neutron design hasn’t shipped yet on mainnet
- Hyperlane endpoints might pose vendor lock-in risks
- A few development artifacts presented: not possible to assess license and code quality
- It was recommended that Hyperlane become more battle-tested for further aggregated evaluation