LayerZero (Project)

From CryptoWiki

From their docs (2-2022):

"LayerZero is an Omnichain Interoperability Protocol designed for lightweight message passing across chains. LayerZero provides authentic and guaranteed message delivery with configurable trustlessness. The protocol is implemented as a set of gas-efficient, non-upgradable smart contracts."

Basics

"LayerZero bills itself as “an omnichain interoperability protocol” that aims to connect all chains in a seamless way."

History

Audits & Exploits

Bugs/Exploits

Governance

Admin Keys

DAO

Treasury

Token

Launch

Token Allocation

Utility

Other Details

Stablecoin

Coin Distribution

Technology

Implementations

"We’re live on Ethereum, Avalanche, Polygon, BNB Chain, Fantom, Arbitrum and Optimism. In 6–8 weeks consider Solana, Terra, Cosmos Hub and Osmosis slam dunks and LayerZero to be everywhere in 4–6 months."

  • Programming language used:

Transaction Details

How it works

"A LayerZero transaction/message only requires source gas in a single call. A transaction begins with a User Application (UA) starting a transaction (aka doing something on-chain). This transaction is then broken up into multiple parts (proof and block header) via the Oracle and Relayer in a flow that is facilitated by a LayerZero Endpoint. Once the Oracle and Relayer send their respective information from the source chain and the LayerZero Endpoint validates that the information is correct, the message is translated and executed on the destination chain.

  1. A User Application packages and transmits the data on Chain A to LayerZero’s endpoint on Chain A.
  2. LayerZero’s Endpoints on Chain A send the transaction’s information to LayerZero’s reference Relayer, whereas the block ID of the transaction is sent to the Oracle
  3. The Relayer and the Oracle receive the transaction proof and block header, respectively, from Chain A.
  4. LayerZero’s Endpoint on Chain B obtains the information initiated by the User Application on Chain A using the block header and emits it to the User Application on Chain B."

"LayerZero is a lightweight universal messaging interface that allows developers to seamlessly interact with contracts across dozens of blockchains. LayerZero Endpoints rely on an innovative Relayer and Oracle architecture to trustlessly relay messages between chains. This unique messaging structure and security model is the only solution available today that does not rely on wrapped assets, middle-chains, or vulnerable upgradeable contracts."

  • From Alphapls (28-3-2022):

"LayerZero is not a blockchain, it is a protocol, largely operating off chain with ‘ultralight client end points’ which are smart contracts built on chains it is aiming to connect. Chains will include L2s, as well as L1s; and later non-EVM, as well as EVM. LayerZero Endpoint exists on each (supported) chain, and any chain with a LayerZero Endpoint can conduct cross-chain transactions involving any other chain with a LayerZero Endpoint. In essence, this creates a fully connected network where every node has a direct connection to every other node. With minor boilerplate code, any blockchain is supported.

LayerZero refer to their light onchain clients as ‘LayerZero Endpoints’. They are made up of smart contracts which have three main functions:

  1. communicator
  2. validator
  3. network

For simplification, I’m going to refer to all of the above as ‘endpoint’ and run a simple example.

  1. Cross-chain action committed on chain A (e.g. against a deposited asset in a lending protocol on ETH, borrow USDC from the same lending protocol on Polygon) and sent to the endpoint.
  2. The endpoint sends information to the Relayer and Oracle - both separate entities and both off chain.
  3. The Oracle confirms the block header (the Oracle on testnet was Chainlink).
  4. The Relayer confirms the transaction on chain A (it’s function is similar to an Oracle but looking for a different bit of data).
  5. Presuming everything is in order, the rest of the action stated on chain A is committed on chain B (USDC is received in wallet on Polygon).

If there is any contention between the Relayer or Oracle as to information being passed on, the smart contract is paused and not committed to chain B. To ensure valid delivery, the only requirement is that for any given message sent using the LayerZero protocol, the Oracle and Relayer must be independent of each other. The protocol itself does not require any specific implementation of a Relayer, and in theory the users of LayerZero could even implement their own Relayer service. This design allows users to be sure that the Relayer cannot collude with the Oracle, and this independence is what allows us to implement trustless validated delivery."

Fees

Upgrades

Staking

Validator Stats

Liquidity Mining

Scaling

Interoperability

"As of September 2022, LayerZero supports 11 chains: Ethereum, BNB Chain, Avalanche, Polygon, Arbitrum, Optimism, Fantom, Swimmer, DFK, Harmony, and Moonbeam."

Other Details

Oracle Method

Their Other Projects

Stargate

"Stargate, the first bridge to solve the Bridging Trilemma, launches on top of LayerZero (and all 7 chains) in two days. Learn about how to participate in liquidity generation event that starts in two days here."

Roadmap

  • Can be found [Insert link here].

Usage

"LayerZero users have sent over 300K messages across supported chains. Going deeper, BNB users are leading in terms of cross-chain messages sent. LayerZero recently surpassed 1000 connected contracts live on the LayerZero Mainnet."

Projects that use or built on it

"dApps like Stargate have already built cross-chain applications on top of LayerZero. Other examples include Radiant, which is building a multi-chain lending protocol, and SushiSwap, which recently launched a cross-chain AMM. You can find the growing list of LayerZero-based dApps here."

Competition

"CCIP will include all the functions [of] LayerZero, including a programmable token bridge to allow similar dApps to Stargate Finance to be built out.

The additional innovation with CCIP is the creation of ‘Hybrid Smart Contracts’ which will enable both on-chain and off-chain smart contracts to work together, in conjunction with cross-chain execution."

Pros and Cons

Pros

  1. "Simplicity — The goal for LayerZero is to put developers first. User applications building with LayerZero simply need to implement two functions — send and receive. If it can be written in Solidity, Rust, etc., then an application can be built on-chain right now. Furthermore, as there is no middleman in the system, two high-throughput chains can interact without constraint.
  2. Lightweight Clients — running smart contracts on Layer 1 can be extremely expensive. Therefore, LayerZero exports storage and fetching of transaction data to Oracles and Relayers, the two off-chain entities whose relationship ensures valid transactions, allowing the Ultra Light Node endpoints to be small and cost-effective. Furthermore, its lightweight clients’ low operating costs allow for the quick incorporation of new chains.
  3. Potential — LayerZero, as its name suggests, is a ground-level piece of infrastructure that can be utilized by liquidity networks, multi-chain yield aggregators, multi-chain lending protocols, and many other dApps to build out super interesting and uniquely multi-chain crypto use-cases.
  4. LayerZero Scan — Cross-chain transactions are now tied together in a single database via LayerZero Scan, which allows users and developers to easily pull state, status, and timing of transactions."

Cons

Team, Funding and Partners

Team

  • Full team can be found [here].
  • LayerZero is the child of Primo and Ryan Zarick with input from well known ex-Sushi developer (and Tokemak advisor) 0xMaki.
  • 0xMaki; full time bizdev

Funding

Partners

(:

Knowledge empowers all and will help us get closer to the decentralized world we all want to live in!

Making these free wiki pages is fun but takes a lot of effort and time.

If you have enjoyed reading, tips are appreciated :) This will help us to keep expanding this archive of information.

ETH tip address: 0x83460bE5F218b1520B69D702cE60A1DE37dD8E31