A Decentralized Verifier Network (DVN) is an independent verifier that checks a cross-chain message, such as a token transfer, before the destination chain accepts it. On LayerZero, each application chooses its own DVNs. For a token, the owner of the token's contracts, usually the issuer, picks which DVNs must sign and how many must agree.
Last updated: November 9, 2026.
Why does a cross-chain transfer need a verifier?
Blockchains cannot read each other's ledgers. When a holder moves a stablecoin from one chain to another, the destination chain cannot see on its own that the tokens left the source chain. Something has to confirm that event before the destination credits the same amount.
A DVN plays the role an auditor plays for a set of accounts. It is an independent party that attests a record is genuine before anyone relies on it. The original DVN explainer covers how DVNs fit into LayerZero V2.
How does a security stack work?
An application's chosen DVNs and its rule for how many must agree form its security stack. The stack has two kinds of DVNs.
| Setting | What it means |
|---|---|
| Required DVNs | Every one of them must verify the message |
| Optional DVNs | A pool of additional DVNs the application trusts |
| Optional threshold | How many DVNs from the optional pool must also verify |
| Per-pathway setting | The stack is set for each pathway, on both the sending and the receiving chain, and the two settings must match |
A message is verified only when all required DVNs and the threshold of optional DVNs have attested to it. The model works like a payment approval policy, where a large payment needs one named officer plus any two of three others.
What changes for an asset issuer?
Because the application owner sets the stack, an issuer decides who verifies its asset.
That control maps onto three choices:
- Who signs. The issuer can pick verifiers it already knows and trusts.
- Where verification happens. The issuer can pick verifiers that operate inside a given jurisdiction.
- How verification works. The issuer can mix verifiers that check messages in different ways, such as institutional operators, cryptographic proofs, hardware-attested signing, or threat screening.
An issuer can also run its own DVN and set it as required on each pathway, so no transfer of its asset on those pathways completes without its signature.
Who can run a DVN?
Any organization that can attest to a message can run a DVN, and any application can choose from the DVNs deployed on the chains it connects. Operators include enterprises, security firms, infrastructure providers, and issuers that verify their own assets. A DVN must be deployed on both chains of a pathway to verify messages between them.
Applications built on LayerZero already move most of the value that crosses chains.
85%+
of Cross-chain USD Volume, Last 30 Days
$300B+
Lifetime Volume
Questions we get asked
Who can change an application's DVN configuration?
The application's owner, or the delegate address the owner sets. By default the owner is the delegate. For a token, that is whoever controls the token's contracts.
Is a DVN the same as an Executor?
No. DVNs verify that a message is genuine. An Executor delivers a verified message on the destination chain. Verification and execution are separate steps.
Can a DVN refuse to verify a message?
Yes. A DVN attests only to messages that pass its checks. If a required DVN does not sign, the message is not verified on the destination chain.
Choose who verifies your asset
To discuss how a security stack can be set up for an asset, request a custom briefing.