Search
Search for projects by name or address
LayerZeroLayerZero
About
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.
About
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” ValidatorIn the context of L2s, a Validator is an actor that validates the correctness of state transitions. For optimistic rollups this corresponds to challengers, and for ZK rollups this corresponds to the onchain verifier Networks). The protocol supports a vast set of EVM and non-EVM destinations.
Architecture
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.
Crosschain oracle and validation
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.
UpgradeabilityThe ability for rollup smart contracts and parameters used in a rollup to be updated by holders of an admin key. Upgradeability represents a vector of risk for users, and should be decentralized and combined with time delays for greater security guarantees.
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.
Monitoring
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Symbol | Last 24h
Volume | Last 24h
transfer count | Last 24h avg.
transfer time | Last 24h avg.
transfer value | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Symbol | Last 24h
Volume | Last 24h
transfer count | Last 24h avg.
transfer time | Last 24h avg.
transfer value | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Timestamp | Tokens | Value | Bridge | Transfer time | Chains | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Timestamp | Tokens | Value | Bridge | Transfer time | Chains | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Timestamp | Tokens | Value | Bridge | Transfer time | Chains | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2026 October 12, 07:19 UTCHigh severity17changesThe Ethereum executor upgraded to an unverified implementation. Executor diff.
The Ethereum executor upgraded to an unverified implementation.
| contract Executor (eth:0x173272739Bd7Aa6e4e214714048a9fE699453059) [N/A] { | |
| +++ description: Upgradeable contract referenced as an executor by LayerZero message libraries. Its current implementation is unverified, so execution and fee handling cannot be checked against source. | |
| template: | |
| - | "layerzero/LayerZeroExecutor" |
| sourceHashes: | |
| - | ["0x4a43bdaa7c21f911802bc9e3457cf5fef469f43b372ea6944d53823caf2f53f2","0x914fbceaba4b6418a09bd2104433bfcb47eed119a783154a8f7f6301c06a6d2b"] |
| values.$implementation: | |
| - | "eth:0xfE9AB78eD4f9f3DbB168d9f5E5213d78605C9805" |
| + | "eth:0x1Ed8E51E8AB2A00B2805aEcf2C6aC0BB6521eaE0" |
| values.$pastUpgrades.3: | |
| + | ["2026-10-02T00:08:11.000Z","0x682248f5070d80b5c52e90030913f204331e1f0516ed6a0e5d471e6417c3fb52",["eth:0x1Ed8E51E8AB2A00B2805aEcf2C6aC0BB6521eaE0"]] |
| values.$upgradeCount: | |
| - | 3 |
| + | 4 |
| values.allowlistSize: | |
| - | 0 |
| values.DEFAULT_ADMIN_ROLE: | |
| - | "0x0000000000000000000000000000000000000000000000000000000000000000" |
| values.defaultMultiplierBps: | |
| - | 12000 |
| values.endpoint: | |
| - | "eth:0x1a44076050125825900e736c501f859c50fE728c" |
| values.localEidV2: | |
| - | 30101 |
| values.paused: | |
| - | false |
| values.priceFeed: | |
| - | "eth:0xC03f31fD86a9077785b7bCf6598Ce3598Fa91113" |
| values.receiveUln301: | |
| - | "eth:0x245B6e8FFE9ea5Fc301e32d16F66bD4C2123eEfC" |
| values.workerFeeLib: | |
| - | "eth:0x4e9C57FD2Bd0f47C43F2D62642C1b05894fb9ed0" |
| implementationNames.eth:0xfE9AB78eD4f9f3DbB168d9f5E5213d78605C9805: | |
| - | "Executor" |
| implementationNames.eth:0x1Ed8E51E8AB2A00B2805aEcf2C6aC0BB6521eaE0: | |
| + | "" |
| unverified: | |
| + | true |
| } | |
2026 August 10, 09:01 UTC4changesMultisig member change.
Multisig member change.
| contract LayerZero Multisig (eth:0xBe010A7e3686FdF65E93344ab664D065A0B02478) [layerzero/OneSigMultisig] { | |
| +++ description: Custom multisignature contract allowing offchain signing and execution on multiple target chains. | |
| values.$members.5: | |
| + | "eth:0xdFE4027209C795B84d39FfBfF86bf73572571BAd" |
| values.$members.6: | |
| + | "eth:0x2be094F1C9AaF76aD3A789EA4f047BBE7D1DB552" |
| values.$threshold: | |
| - | 3 |
| + | 5 |
| values.totalSigners: | |
| - | 5 |
| + | 7 |
| } | |
2026 July 23, 13:55 UTC1changeOne Safe signer was rotated.
One Safe signer was rotated.
| contract GnosisSafe (eth:0xCbcdd778AA25476F203814214dD3E9b9c46829A1) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.3: | |
| - | "eth:0x86CbBAEB08861D005fD2147A5123E43e558db167" |
| + | "eth:0xb859DD2Cb50F19a53Ad25b279750ba5DEC76D306" |
| } | |
2026 July 17, 07:48 UTC1changeSingle signer change.
Single signer change.
| contract GnosisSafe (eth:0xCbcdd778AA25476F203814214dD3E9b9c46829A1) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.5: | |
| - | "eth:0xFbF8084Fb81da2e24f9EdD821172efef1b74F218" |
| + | "eth:0xa85B57bD7433dCC4679d638b87d80F155A689Fc1" |
| } | |
2026 June 16, 09:59 UTC1changeUnichain peer blocked in ethereum rsETH OApp.
Unichain peer blocked in ethereum rsETH OApp.
| contract RsETHOFTAdapter (eth:0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3) [layerzero/OFTAdapter] { | |
| +++ description: 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. | |
| +++ description: The configured peer for the rsETH OFT route from Unichain. | |
| values.peerUnichain: | |
| - | "unichain:0xc3eACf0612346366Db554C991D7858716db09f58" |
| + | "unichain:0x0000000000000000000000000000000000000000" |
| } | |
Ethereum
Actors:
A Multisig with 5/7 threshold. Custom multisignature contract allowing offchain signing and execution on multiple target chains.
- Can interact with EndpointV2
- configure the default send/receive libraries used for verification, affecting all OApps that have not set up a custom security config
- Can interact with ReadLib1002
- configure the settings of this library, affecting all OApps that have not set up a custom security config
- Can interact with SendUln302
- configure the settings of this library, affecting all OApps that have not set up a custom security config
- Can interact with ReceiveUln302
- configure the settings of this library, affecting all OApps that have not set up a custom security config
A Multisig with 3/6 threshold.
- Can interact with EndpointV2
- manage all settings of the LZ crosschain security stack for the respective OApp: change libraries, DVN configs etc
- Can interact with RsETHOFTAdapter
- can configure the OFT adapter, including LayerZero peer and delegate settings
Defines the logic that validates LayerZero Packets for this DVN.
- Can interact with SendUln302
- receive validation fees for rsETH OFT messages sent to Unichain through LayerZero (the incoming vaidating DVN is defined on Unichain)
- Can interact with ReceiveUln302
- verify rsETH OFT messages sent from Unichain through LayerZero
Defines the logic that validates LayerZero Packets for this DVN.
- Can interact with SendUln302
- receive validation fees for rsETH OFT messages sent to Unichain through LayerZero (the incoming vaidating DVN is defined on Unichain)
- Can interact with ReceiveUln302
- verify rsETH OFT messages sent from Unichain through LayerZero
Defines the logic that validates LayerZero Packets for this DVN.
- Can interact with SendUln302
- receive validation fees for rsETH OFT messages sent to Unichain through LayerZero (the incoming vaidating DVN is defined on Unichain)
- Can interact with ReceiveUln302
- verify rsETH OFT messages sent from Unichain through LayerZero
Defines the logic that validates LayerZero Packets for this DVN.
- Can interact with SendUln302
- receive validation fees for rsETH OFT messages sent to Unichain through LayerZero (the incoming vaidating DVN is defined on Unichain)
- Can interact with ReceiveUln302
- verify rsETH OFT messages sent from Unichain through LayerZero
Upgradeable contract referenced as an executor by LayerZero message libraries. Its current implementation is unverified, so execution and fee handling cannot be checked against source.
- Can interact with SendUln302
- receive execution fees for rsETH OFT messages sent to Unichain through LayerZero
- Can upgrade with no delay
- Executor ProxyAdmin
Ethereum
Part of the LayerZero messaging protocol. OApp owners or their delegates can configure custom verification- (message libraries) and execution settings here.
- Roles:
- owner: LayerZero Multisig
- rsETHAdapterDelegate: GnosisSafe
LayerZero-deployed receive library, defining the validation of received messages.
- Roles:
- getUlnConfig: Canary DVN, Horizen DVN, LayerZero DVN, Netherming DVN
- owner: LayerZero Multisig
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.
- Roles:
- owner: GnosisSafe
Simple LayerZero library that blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. all messages if selected.
LayerZero library used to read state from remote blockchains.
- Roles:
- owner: LayerZero Multisig
- Roles:
- owner: EOA 1
Send Library used by LayerZero, defining the protocol/execution of sent messages.
- Roles:
- getExecutorConfig: Executor
- getUlnConfig: Canary DVN, Horizen DVN, LayerZero DVN, Netherming DVN
- owner: LayerZero Multisig
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).