Search for projects by name or address
LayerZero OFT (omnichain fungible token) is a multichain token framework built on the modular, highly customizable LayerZero messaging protocol. While it theoretically supports any form of validation, ~100% of messages are validated by multisig-like smart... contracts called DVNs ("Decentralized" Validator Networks). The protocol supports a vast set of EVM and non-EVM destinations.



LayerZero OFT (omnichain fungible token) is a multichain token framework built on the modular, highly customizable LayerZero messaging protocol. While it theoretically supports any form of validation, ~100% of messages are validated by multisig-like smart... contracts called DVNs ("Decentralized" Validator Networks). The protocol supports a vast set of EVM and non-EVM destinations.

LayerZero OFT (omnichain fungible token) is a multichain token framework built on the modular, highly customizable LayerZero messaging protocol. While it theoretically supports any form of validation, ~100% of messages are validated by multisig-like smart contracts called DVNs (“Decentralized” Validator Networks). The protocol supports a vast set of EVM and non-EVM destinations.
LayerZero deploys a single Endpoint contract on each supported chain. This contract serves as the chain-central registry for omnichain apps (OApps) and their owners and delegates. An Oapp is a smart contract that interacts with the LayerZero protocol through a standardized messaging interface. The most popular OApp flavor is the omnichain fungible token (OFT) standard, which enables the transport of tokens across LayerZero-supported chains. Token owners can deploy OFT Adapter smart contracts (OApps themselves) that connect traditional tokens to the LayerZero protocol. New tokens can be directly bound to LayerZero by deploying them as a native OFT smart contract, which is automatically an OApp on LayerZero.
The modular LayerZero messaging protocol supports any smart contract logic as its validation mechanism. In practice and by default, multisignature wallets and EOAs validate and deliver crosschain messages, called packets in LZ terms. OApp owner addresses or their onchain delegates can override the default security config for their OApp in each local Endpoint contract. Each library or setting that is not explicitly configured falls back to the default config. Security configs consist of a validation library (smart contract) and its various settings (like the actual validating multisigs and their threshold) and importantly can be set on each chain separately and then for each peer chain from/to that chain. For example, a single OFT that is live on 20 chains can have 20x20=400 security configs, counting incoming configs only. A misconfiguration or exploit in any single one of those 400 validation configs can compromise the example OFT.
Core protocol contract code forms a framework that points at security-critical contracts. Although the core framework contract code is immutable, the security config and its implementation contracts can be changed by permissioned actors like the LayerZero team and the OApp owners, which effectively results in system upgrades. Application-level contracts like OApps have custom upgradeability.
LayerZero provides a block explorer which is mostly intended for users and researchers tracking crosschain transactions and for aggregate metrics. There currently is no security or monitoring related tooling for OApp owners like global OFT accounting or global security config tracking.
Symbol | Last 24h
Volume | Last 24h
transfer count | Last 24h avg.
transfer time | Last 24h avg.
transfer value | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Timestamp | Tokens | Value | Transfer time | Chains | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
A Multisig with 3/5 threshold. Custom multisignature contract allowing offchain signing and execution on multiple target chains.
A Multisig with 3/6 threshold.
Defines the logic that validates LayerZero Packets for this DVN.
Defines the logic that validates LayerZero Packets for this DVN.
Defines the logic that validates LayerZero Packets for this DVN.
Defines the logic that validates LayerZero Packets for this DVN.
Contract that can be used to execute LayerZero message payloads at the destination. Also manages fee logic, gas drop and permissioned addresses who can call this contract.
Part of the LayerZero messaging protocol. OApp owners or their delegates can configure custom verification- (message libraries) and execution settings here.
LayerZero-deployed receive library, defining the validation of received messages.
An OApp in the LayerZero protocol that adapts an existing ERC20 token into the OFT standard. Its owner can configure peers and LayerZero security settings for connected routes.
Simple LayerZero library that blocks all messages if selected.
LayerZero library used to read state from remote blockchains.
Send Library used by LayerZero, defining the protocol/execution of sent messages.
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).