[{"data":1,"prerenderedAt":19},["ShallowReactive",2],{"blog-content-en-what-is-layerzero":3},{"slug":4,"title":5,"excerpt":6,"description":7,"bodyHtml":8,"faqItems":9},"what-is-layerzero","What Is LayerZero? The Omnichain Protocol Behind Cross-Chain Tokens","A plain-English explainer of LayerZero, the omnichain messaging protocol that lets a single token exist natively across many chains without wrapped or bridged copies.","What LayerZero is, how its endpoints, DVNs and executors move messages between chains, and how OFTs replace wrapped, bridged tokens. A neutral 2026 explainer.","\u003Ch2>The cross-chain problem\u003C\u002Fh2>\n\u003Cp>Crypto is not one network. It is dozens of chains — Ethereum and its rollups, Solana, TON, and many more — each with its own state, its own validators, and no built-in way to talk to the others. For years the standard workaround was the bridge: lock a token on chain A, mint a stand-in for it on chain B. That stand-in is a \u003Cem>wrapped\u003C\u002Fem> or \u003Cem>bridged\u003C\u002Fem> token, and it is not the original asset. It is an IOU issued by the bridge.\u003C\u002Fp>\n\u003Cp>This design fragments liquidity. The same underlying token ends up living as five or six incompatible representations, each with its own pool, its own price drift, and its own trust assumptions. It also concentrates risk: the locked collateral sits in a bridge contract, and the largest exploits in the industry's history have drained exactly those contracts. If you want the mechanics, our explainer on \u003Ca href=\"\u002Fblog\u002Fhow-to-bridge-crypto-across-chains\">how to bridge crypto across chains\u003C\u002Fa> walks through the lock-and-mint flow step by step.\u003C\u002Fp>\n\n\u003Ch2>What LayerZero is\u003C\u002Fh2>\n\u003Cp>LayerZero is an \u003Cem>omnichain interoperability protocol\u003C\u002Fem>: a standard for passing arbitrary messages from a contract on one chain to a contract on another. It does not custody your funds and it is not itself a bridge in the classic sense. It is closer to a messaging layer — a way for an application deployed on many chains to send a verified instruction from one deployment to another. \"Move 100 tokens,\" \"this NFT now lives here,\" \"execute this call\" are all just messages.\u003C\u002Fp>\n\u003Cp>The important shift is conceptual. Instead of an asset being \u003Cem>locked here and copied there\u003C\u002Fem>, an application can be deployed natively on every chain and coordinate its own state through messages. The token is one thing with many endpoints, not many things pretending to be one.\u003C\u002Fp>\n\n\u003Ch2>How messages move, at a high level\u003C\u002Fh2>\n\u003Cp>Every supported chain runs a LayerZero \u003Cem>Endpoint\u003C\u002Fem> — an on-chain contract that applications send to and receive from. When an app emits a message, two roles carry it across the gap. First, one or more \u003Cem>DVNs\u003C\u002Fem> (Decentralized Verifier Networks) independently attest that the message really was emitted on the source chain and was not tampered with. Then an \u003Cem>Executor\u003C\u002Fem> delivers the verified message to the destination endpoint and pays to run the receiving logic, so the end user does not have to hold gas on the far chain.\u003C\u002Fp>\n\u003Cp>The design point worth remembering is that verification is \u003Cem>configurable\u003C\u002Fem>. As of 2026, an application chooses which DVNs it trusts and how many must agree before a message is accepted. LayerZero supplies the plumbing; the app sets the security policy. We will come back to what that means.\u003C\u002Fp>\n\n\u003Ch2>What it enables: OFT, ONFT and omnichain apps\u003C\u002Fh2>\n\u003Cp>The headline standard built on top of this is the \u003Cem>OFT — Omnichain Fungible Token\u003C\u002Fem>. An OFT is a token contract deployed on every chain it supports, wired together through LayerZero messaging. Moving an OFT between chains burns the amount on the source chain and mints the exact same amount on the destination, coordinated by a verified message. There is no third-party wrapper and no locked collateral pool — the token's own contracts are the counterparties. The result is a single, canonical asset with one balance semantics everywhere it lives. Our deep dive on \u003Ca href=\"\u002Fblog\u002Fwhat-is-an-oft-omnichain-fungible-token\">what an OFT is\u003C\u002Fa> covers the burn-and-mint flow in detail.\u003C\u002Fp>\n\u003Cp>The same pattern extends to NFTs (ONFTs) and to fully omnichain applications — governance, lending, or gaming logic that reads and writes state across chains as if the boundaries were not there.\u003C\u002Fp>\n\n\u003Ch2>LayerZero vs classic lock-and-mint bridges\u003C\u002Fh2>\n\u003Cp>A classic bridge answers \"how do I get a copy of this asset onto another chain.\" An OFT answers \"how does this asset exist on many chains at once.\" The distinction is not cosmetic. With lock-and-mint, the bridged version is only as sound as the bridge holding the collateral, and every route you add spawns another wrapped variant that fragments liquidity further. With an OFT, supply moves rather than duplicates — the total across all chains stays constant because a transfer burns on one side and mints on the other.\u003C\u002Fp>\n\u003Cp>That is why \"omnichain\" and \"bridged\" are genuinely different categories rather than synonyms. We compare them directly in \u003Ca href=\"\u002Fblog\u002Fomnichain-vs-wrapped-bridged-tokens\">omnichain vs wrapped and bridged tokens\u003C\u002Fa> if you want the side-by-side.\u003C\u002Fp>\n\n\u003Ch2>The security model is configurable, not automatic\u003C\u002Fh2>\n\u003Cp>It is worth being precise here, because \"omnichain\" is sometimes marketed as if it removed trust entirely. It does not. LayerZero moves the trust assumption from a single bridge operator to a configurable set of verifiers. An application that chooses many independent DVNs and a high agreement threshold has a very different risk profile from one that relies on a single verifier. As of 2026 the protocol is neutral on this — it is a framework, and the safety of any particular OFT depends on how its issuer configured verification and how well the token contracts themselves are written. Omnichain design removes the wrapped-IOU problem; it does not remove the need to evaluate who is verifying your messages.\u003C\u002Fp>\n\n\u003Ch2>How WATS uses this\u003C\u002Fh2>\n\u003Cp>WATS's fee token, ATS, is a LayerZero OFT, which means one ATS balance works natively across EVM, Solana and TON — no wrapped copies, no bridged IOUs, and nothing to unwrap when you move between chains. In the \u003Ca href=\"\u002Fhot-wallet\">WATS Hot Wallet\u003C\u002Fa>, that single balance is what pays for every action — transfers, swaps and staking are all charged in ATS instead of each chain's native gas, and the ATS collected as fees is burned, reducing supply from 100,000,000 toward a 30,000,000 floor. WATS is non-custodial throughout: you hold your keys and WATS never holds one. You can read more about the fee model on the \u003Ca href=\"\u002Fats-fee\">ATS fee page\u003C\u002Fa>.\u003C\u002Fp>",[10,13,16],{"q":11,"a":12},"Is a LayerZero OFT the same as a wrapped or bridged token?","No. A wrapped token is a stand-in minted by a bridge that locks the original asset elsewhere, so it depends on that bridge's collateral. An OFT is the real token deployed natively on every chain it supports; moving it burns the amount on the source chain and mints the same amount on the destination, keeping total supply constant with no locked pool or IOU.",{"q":14,"a":15},"Does LayerZero hold my funds or take custody?","No. LayerZero is a messaging protocol, not a custodian or a classic bridge. It passes verified messages between endpoint contracts on each chain, while the application's own contracts hold and move assets. As of 2026, the trust involved lies in the configurable set of verifiers (DVNs) an application selects, not in LayerZero holding your tokens.",{"q":17,"a":18},"What are DVNs and executors in LayerZero?","DVNs, or Decentralized Verifier Networks, independently confirm that a message genuinely originated on the source chain and was not altered. An executor then delivers the verified message to the destination chain and pays to run the receiving logic. An application chooses which DVNs it trusts and how many must agree, which is why LayerZero's security is described as configurable rather than fixed.",1784634269030]