LibraryInteroperability2024Design paperCorpus record
LayerZero v2: endpoint, message libraries, and decentralised verifier networks
LayerZero. LayerZero Labs.
LayerZero v2 splits an endpoint that applications call from the message libraries and verifier sets that actually attest a remote event.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
LayerZero v2 splits an endpoint that applications call from the message libraries and verifier sets that actually attest a remote event.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 4
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
An omnichain message that hides who verifies the remote chain is a bridge with an unnamed signer.
Claim 02 · Paper model
The proposal
LayerZero v2 splits an endpoint that applications call from the message libraries and verifier sets that actually attest a remote event.
Claim 03 · Paper model
The mechanism
The endpoint is the interface. The security stack is the verifier set the application configures. Those are different objects, and the docs say the application chooses.
Claim 04 · Paper model
The bound
This note names no volume of messages and no chain count as a performance claim.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
An omnichain message that hides who verifies the remote chain is a bridge with an unnamed signer.
Model
What has to hold
You are reading the v2 documentation. A v1 diagram is a different protocol.
Falsifier
What would retire it
Which verifier set does the application you are reading actually configure?
02 The proposal
Observation
What the study says
LayerZero v2 splits an endpoint that applications call from the message libraries and verifier sets that actually attest a remote event.
Model
What has to hold
The document is the one at the source URL. A marketing page with the same brand is not this text.
Falsifier
What would retire it
Which verifier set does the application you are reading actually configure?
03 The mechanism
Observation
What the study says
The endpoint is the interface. The security stack is the verifier set the application configures. Those are different objects, and the docs say the application chooses.
Model
What has to hold
You are reading the v2 documentation. A v1 diagram is a different protocol.
Falsifier
What would retire it
Which verifier set does the application you are reading actually configure?
04 The bound
Observation
What the study says
This note names no volume of messages and no chain count as a performance claim.
Model
What has to hold
You are reading the v2 documentation. A v1 diagram is a different protocol.
Falsifier
What would retire it
Which verifier set does the application you are reading actually configure?
03 Sequence
One action, as an operating tape
- 01The endpoint is the interface. The security stack is the verifier set the application configures. Those are different objects, and the docs say the application chooses.
- 02A message is delivered if the configured verifiers agree, under the library's rule. Agreement is not a light-client proof unless the library is a light client.
- 03v1's oracle-and-relayer pairing is a different design. Do not describe v2 with v1's diagram.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
LayerZero v2 splits an endpoint that applications call from the message libraries and verifier sets that actually attest a remote event.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A verifier set of one is a trusted signer. Configuration can choose that, and the design allows it.
What actually moves
The cut
A message is delivered if the configured verifiers agree, under the library's rule. Agreement is not a light-client proof unless the library is a light client.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
Delivery of a message is not atomic settlement of assets unless the application builds that on top.
What a later deployment may change
The cut
v1's oracle-and-relayer pairing is a different design. Do not describe v2 with v1's diagram.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A verifier set of one is a trusted signer. Configuration can choose that, and the design allows it.
05 Register
What has to be true
Model · Not re-measured
You are reading the v2 documentation. A v1 diagram is a different protocol.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
Delivery of a message is not atomic settlement of assets unless the application builds that on top.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
An omnichain message that hides who verifies the remote chain is a bridge with an unnamed signer.
What the design proposes
- The endpoint is the interface. The security stack is the verifier set the application configures. Those are different objects, and the docs say the application chooses.
- A message is delivered if the configured verifiers agree, under the library's rule. Agreement is not a light-client proof unless the library is a light client.
- v1's oracle-and-relayer pairing is a different design. Do not describe v2 with v1's diagram.
How the mechanism is specified
- The endpoint is the interface. The security stack is the verifier set the application configures. Those are different objects, and the docs say the application chooses.
- A message is delivered if the configured verifiers agree, under the library's rule. Agreement is not a light-client proof unless the library is a light client.
- v1's oracle-and-relayer pairing is a different design. Do not describe v2 with v1's diagram.
What this page does not treat as proven
- This note names no volume of messages and no chain count as a performance claim.
- A verifier set of one is a trusted signer. Configuration can choose that, and the design allows it.
- Delivery of a message is not atomic settlement of assets unless the application builds that on top.
Why the desk still reads it
LayerZero v2 splits an endpoint that applications call from the message libraries and verifier sets that actually attest a remote event.
09 Lexicon
Terms, opened into the record
- Endpoint
- The contract applications call. It is not the verifier.
- Verifier network
- The set configured to attest a remote event. The set is the trust assumption.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.