<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[LayerZero Official - Medium]]></title>
        <description><![CDATA[We’re building LayerZero, an omnichain interoperability protocol. - Medium]]></description>
        <link>https://medium.com/layerzero-official?source=rss----86a3a7f3e9a7---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>LayerZero Official - Medium</title>
            <link>https://medium.com/layerzero-official?source=rss----86a3a7f3e9a7---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:34:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/layerzero-official" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[lzRead: Power Your App with Omnichain Data]]></title>
            <link>https://medium.com/layerzero-official/lzread-power-your-app-with-omnichain-data-cdd341eeeaf7?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/cdd341eeeaf7</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[layer-zero]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[LayerZero]]></dc:creator>
            <pubDate>Wed, 13 Nov 2024 20:04:19 GMT</pubDate>
            <atom:updated>2024-11-14T02:33:10.630Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GpyEHHRqTfRYfjdsM1aC8g.png" /></figure><p><em>Request, transform, and rely on data from any chain, wherever you are.</em></p><p>Introducing <strong>lzRead</strong>, a new data primitive within the LayerZero protocol. Built for smart contract developers, lzRead allows seamless access to onchain data from any supported network with a single function call.</p><blockquote>Any Data. On Any Chain. Over any period of time.</blockquote><h3>Why lzRead?</h3><p>Traditionally, smart contracts were designed to only access the current state on their own blockchain. But with the proliferation of blockchains, valuable data is now fragmented, creating a need for a unified solution to access data across chains.</p><p>lzRead gives developers a new way to think about building applications. It unlocks the possibility for smart contracts to efficiently compose with any external data from many chains across any period of time — all in a single function call.</p><p>Benefits of the lzRead include:</p><ul><li><strong>Comprehensive:</strong> Retrieve data across chains using standardized methods that simplify workflows and reduce development complexity.</li><li><strong>Configurable: </strong>Applications maintain complete control over security, what chains to utilize, and what entities retrieve, transform, and validate data.</li><li><strong>Simple: </strong>Developers can integrate lzRead with just a few lines of code, accessing any supported chain’s data directly.</li><li><strong>Cost-Effective: </strong>A pay-as-you-go model ensures fees are only incurred when making data requests, keeping operational costs low and scalable.</li></ul><h3>What is lzRead?</h3><p>Using any standard smart contract language, developers can retrieve and compute data from one or multiple chains with a single function call, leveraging the full historical data of each chain.</p><p>Developers only need to understand a few components before using lzRead. These include: Messaging Channels, Decentralized Verifier Networks (DVNs), and ReadLib.</p><ul><li><strong>Message Channels: </strong>A channel is the medium in which a developer will send and receive data. These are parallel messaging streams that developers can configure for different requests. These can be used to optimize requests for number of chains, data redundancy, cost, speed, and security. Channels can be set up as single-source, multi-source, or multi-channel queries, offering flexibility depending on application needs.</li><li><strong>Infrastructure: </strong>Just like with the core LayerZero protocol, applications configure a set of <a href="https://medium.com/layerzero-official/layerzero-v2-explaining-dvns-02e08cce4e80">DVNs</a> to fetch requested data and transform it (i.e. perform computing tasks) according to the application’s specifications.</li><li><strong>Immutable Contract: </strong>An immutable Message Library called ReadLib securely processes data requests from applications and directs them to the designated DVNs. After the DVNs retrieve the requested data, ReadLib validates it, ensuring accuracy and integrity before the data is sent to the application.</li></ul><h3>How Does lzRead Work?</h3><p>To start, developers deploy an lzRead-compatible <a href="https://docs.layerzero.network/v2/home/token-standards/oapp-standard">Omnichain Application (OApp)</a>, configure DVNs, (set up channels), and begin building <em>Read Requests</em>.</p><p>A Read Request includes the blockchain(s) to read from, the specific data needed (including time parameters), and any transformations (i.e., compute) the DVNs must apply before the data is sent back to an application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Jc7GWSF1HBtF9yo" /></figure><p><strong>lzRead Request Lifecycle:</strong></p><ol><li><strong>Request: </strong>The <a href="https://docs.layerzero.network/v2/home/token-standards/oapp-standard">Omnichain application (OApp) </a>sends the Read Request to the LayerZero Endpoint. From there, the request is securely passed to ReadLib, where the designated DVNs can access it.</li><li><strong>Fetch:</strong> DVNs gather the requested data from the specified chain(s),</li><li><strong>Compute (Optional)</strong>: If the request includes Compute (Map and/or Reduce functions), the DVNs will transform the data as specified and combine it into a single, unified result.</li><li><strong>Verify</strong>: Each DVN returns the data to ReadLib, where it is validated according to the application’s DVN threshold.</li><li><strong>Return</strong>: The validated data is returned to the OApp by an <a href="https://docs.layerzero.network/v2/home/permissionless-execution/executors">Executor</a>.</li></ol><p>This flow supports a wide range of configurations, making lzRead adaptable to a number of use cases like synchronizing state, verifying asset ownership, and custom pricing calculations (e.g., TWAP, VWAP, etc.). Several of these use cases are already being designed and tested with our Day 1 Builders.</p><h3><strong>lzRead in Practice</strong></h3><p>By making cross-chain and historical data accessible, lzRead opens up a variety of powerful applications for crypto-native development.</p><p>Here’s how Day 1 Builders are using lzRead:</p><ul><li><strong>Cross-Chain Governance (Agora)</strong>: Agora uses lzRead to gather votes from token holders across chains, enabling seamless governance for DAOs without needing to bridge assets.</li><li><strong>Asset Verification (ApeChain)</strong>: ApeChain leverages lzRead to verify BAYC NFT ownership on Ethereum, creating “shadow tokens” that reflect mainnet ownership across chains without requiring users to bridge NFTs.</li><li><strong>Proof of Reserves (Ambient)</strong>: Ambient integrates lzRead to fetch Total Value Locked (TVL) across multiple chains, enabling a zero-trust model for reserves verification in real-time.</li><li><strong>Cross-Chain Price Feeds (Gelato)</strong>: Gelato aggregates token prices across chains with lzRead, providing reliable price feeds for liquidity management and automated DeFi operations.</li><li><strong>Election Resolution (Wintermute)</strong>: Wintermute relies on lzRead to access real-time, cross-chain data from Ethereum, Arbitrum, and Base for election prediction markets, ensuring unbiased, transparent outcomes.</li></ul><p>Additional builders like <strong>EigenLayer</strong>, <strong>Stargate</strong>,<strong> Ethena,</strong> and <strong>Plume</strong> are actively researching and developing unique use cases with lzRead. Others like AltLayer will provide services that make leveraging LayerZero with lzRead even easier for builders, further expanding its impact across DeFi, governance, and beyond.</p><h3><strong>Product Specs and Performance</strong></h3><ul><li><strong>Supported Origin Chains</strong>: lzRead can be initiated on all EVM chains supported by LayerZero, with new connections added regularly.</li><li><strong>Supported Data Chains</strong>: Current and historical data is available for lzRead developers to access from Ethereum, Base, Polygon, Avalanche, BNB Chain, Optimism, and Arbitrum. Interested in another chain? <a href="https://layerzeronetwork.typeform.com/to/YaeE8T71">Reach out here</a>.</li><li><strong>DVNs</strong>: Day 1 DVN partners include BCW, Nethermind, LayerZero Labs, Animoca/Blockdaemon, and Nocturnal, with Gelato and AltLayer also developing DVNs. Each data chain has at least two DVNs for security and redundancy.</li></ul><p>For detailed documentation and support for lzRead, visit the LayerZero <a href="https://layerzero.network/lz-read">website</a>, check out the <a href="https://docs.layerzero.network/">docs</a>, or <a href="https://x.com/LayerZero_Core/status/1856872776709067019">watch the launch video</a>. You can also reach out <a href="https://layerzeronetwork.typeform.com/to/YaeE8T71">here</a>.</p><h3><strong>About LayerZero</strong></h3><p>LayerZero is an immutable, permissionless, and censorship-resistant interoperability protocol that seamlessly connects the onchain economy. With the addition of lzRead, it now also provides a powerful primitive to access data anywhere.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdd341eeeaf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/lzread-power-your-app-with-omnichain-data-cdd341eeeaf7">lzRead: Power Your App with Omnichain Data</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LayerZero x EigenLayer: The CryptoEconomic DVN Framework]]></title>
            <link>https://medium.com/layerzero-official/layerzero-x-eigenlayer-the-cryptoeconomic-dvn-framework-68af27ca2040?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/68af27ca2040</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[layer-zero]]></category>
            <dc:creator><![CDATA[LayerZero]]></dc:creator>
            <pubDate>Wed, 02 Oct 2024 13:55:37 GMT</pubDate>
            <atom:updated>2024-10-22T16:57:46.181Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ES_qEzA_--pYLtBsMCezQ.png" /></figure><p>LayerZero Labs, in partnership with Eigen Labs, is introducing a framework for CryptoEconomic Decentralized Verifier Networks (DVNs).</p><p><strong>The CryptoEconomic DVN Framework </strong>brings cryptoeconomic security to omnichain messaging, ensuring that verifiers are not only technically sound but also financially incentivized to act honestly. This framework allows projects to easily bootstrap a DVN on EigenLayer using ANY tokens, operators, and slashing rules.</p><p>The first DVN to utilize this Framework is the LayerZero Labs DVN, which accepts ETH, ZRO, and EIGEN as staking assets.</p><p><strong><em>This article outlines the CryptoEconomic DVN Framework.</em></strong></p><h3>LayerZero DVNs and EigenLayer’s CryptoEconomic Security</h3><p><strong>LayerZero</strong> is an omnichain interoperability protocol that transmits secure messages (i.e., data packets) across 80+ blockchains, enabling the development of applications that exist on many chains at once. Applications using LayerZero can send and receive data between blockchains while having the freedom to choose their own security setup. This includes the selection of <a href="https://medium.com/layerzero-official/layerzero-v2-explaining-dvns-02e08cce4e80"><strong>Decentralized Verifier Networks (DVNs)</strong></a>, which are off-chain infrastructure that verify messages. Currently, 35 entities, including zk-proof teams like Polyhedra and oracles like Google Cloud, operate DVNs, forming a marketplace of verifiers for applications to choose from.</p><p><strong>EigenLayer</strong> introduces<strong> cryptoeconomic security</strong>, a primitive built on Ethereum designed to enhance security by using existing staked assets (e.g., stETH) to secure additional services, applications, and verification systems. By creating a decentralized security marketplace, EigenLayer enables applications and infrastructure to leverage cryptoeconomic guarantees for security, without requiring developers to build it from scratch.</p><p>The combination of LayerZero’s DVN marketplace and EigenLayer’s economic security marketplace led to the creation of the CryptoEconomic DVN Framework.</p><h3>Why CryptoEconomic DVNs Matter</h3><p>With CryptoEconomic DVNs, applications gain guarantees via restaked assets and slashing conditions that backstop the trust previously placed in a DVN’s verification methodology.</p><p>Here’s how CryptoEconomic DVNs transform omnichain security:</p><ol><li><strong>Cryptoeconomic Security:</strong> The core innovation in CryptoEconomic DVNs is the introduction of <strong>slashing mechanisms</strong>. If a DVN acts maliciously or incorrectly, its staked assets are slashed. This shifts trust away from subjective beliefs in verifier integrity toward a quantifiable, economically secured system. Slashing ensures that DVNs have “skin in the game,” making bad behavior costly and, therefore, deterring it.</li><li><strong>AVS-Defined Security:</strong> Each <strong>Actively Validated Service (AVS)</strong> defines which assets can be staked and the conditions for when the stake can be slashed. This flexibility allows for the economic backing of any DVN, whether it uses zk-proofs, middlechains, POA, or any other mechanism. For example, a zk-proof-based DVN can further strengthen its security by adding restaked collateral that’s visible on-chain, providing an additional layer of economic deterrence to prevent bad behavior.</li><li><strong>Permissionless Security:</strong> CryptoEconomic DVNs allow anyone to contribute to the security of LayerZero messages by staking assets into the DVN’s AVS. The DVN can choose whichever assets it wants to back its network, like ZRO, EIGEN, ETH, or any other asset.</li></ol><h3><strong>How CryptoEconomic DVNs Work</strong></h3><p><em>This open-source framework is available for any third-party DVN to adopt, allowing the DVN to enhance security by incorporating CryptoEconomic security via any tokens.</em></p><p>The <strong>CryptoEconomic DVN Framework</strong> introduces four essential mechanisms to secure LayerZero’s omnichain messaging: <strong>stake</strong>, <strong>verify, veto, </strong>and <strong>slash</strong>.</p><ul><li><strong>Stake:</strong> Stakers lock up assets, such as ZRO, EIGEN, or ETH, into a DVN’s AVS. These assets serve as a financial backstop, ensuring that the DVN acts in the best interest of the applications it serves. The economic collateral is held in smart contracts, and these assets are at risk of slashing if the DVN is found to act maliciously or incorrectly during verification.</li><li><strong>Verify: </strong>A user or application can trigger a permissionless round-trip message that travels from Ethereum → Source Chain → Destination Chain → Ethereum. This verifies whether the packet hash transmitted and verified by the DVN matches the packet hash recorded on-chain. If there is no mismatch then the veto process never takes place (step 3).</li><li><strong>Veto: </strong>If a discrepancy is found in message verification, a separate veto contract is triggered on Ethereum, where token holders vote on whether the offending DVN’s stake should be slashed. Vetoing is essential to this process since a blockchain reorg could cause a packet mismatch (i.e., indicate malicious activity), even though the DVN was acting honestly and should not be slashed. If the veto determines there is no malicious behavior conducted by the DVN (e.g., reorg which impacts the message packets) the staked assets remain unaffected.</li><li><strong>Slash:</strong> If the veto confirms a packet mismatch, then the assets staked in the DVN’s AVS are slashed.</li></ul><p>The diagram and steps outlined below illustrate the verification, vetoing, and slashing processes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TqV-XVI7P8C6OeRc" /></figure><h4><strong>Phase 1: Verification</strong></h4><p>1. <strong>Trigger Verification: </strong>user or application can trigger a permissionless round-trip message that travels from Ethereum → Source Chain → Destination Chain → Ethereum. Multiple DVNs will be selected, which are different from the DVN in question, to verify the round-trip message. Since the DVNs handling the verification are separate from the DVN being evaluated, that DVN cannot participate in its own “evaluation,” which reduces the risk of collusion and an improper outcome.</p><p>2. <strong>Ethereum Endpoint</strong>: The process begins with a user or application that triggers a round-trip verification message starting with an endpoint on the Ethereum blockchain.</p><p>3. <strong>Source Chain Endpoint</strong>: The verification message is transmitted and interacts with the source chain endpoint to collect and verify data.</p><p>4. <strong>Destination Chain Endpoint</strong>: After processing on the source chain, the message travels to the destination chain, where similar interactions occur at another endpoint.</p><p>5.<strong> Return to Ethereum</strong>: The message returns to the Ethereum blockchain, carrying the source chain and destination chain data packets back for comparison. If a discrepancy between the packets is not found, then the slashing veto contract is not triggered (step 6).</p><h4><strong>Phase 2: Vetoing</strong></h4><p>6. <strong>Trigger Slashing Veto Contract</strong>: If discrepancies are found (e.g., a mismatched packet hash), the slashing veto contract is triggered on Ethereum for voting on whether to slash the DVN. Staked funds are locked for 7 days during the veto process.</p><p>7. <strong>Veto</strong>: Token holders can veto the slashing event. Again, this step is critical because unexpected situations, like a blockchain reorg event, may result in a packet mismatch and indicate malicious activity when in reality the DVN was acting honestly. If a veto is invoked, it means no malicious behavior was found by the DVN, and the staked assets remain unaffected.</p><h4><strong>Phase 3: Slashing</strong></h4><p>8. <strong>Slashing: </strong>If the veto is not invoked, it confirms that the DVN either made an incorrect packet verification or acted maliciously, leading to the staked assets in the AVS contract being slashed.</p><h3>LayerZero Labs x Eigen Labs DVN</h3><p>The LayerZero Labs DVN is the first CryptoEconomic DVN to use this Framework and was co-developed by LayerZero Labs and Eigen Labs.</p><p>Anyone can stake ZRO, EIGEN, and ETH into the LayerZero Labs DVN AVS staking contract. If a packet discrepancy is detected, ZRO holders can vote on whether staked assets should be slashed.</p><p>This setup adds an additional layer of security for applications that rely on this DVN to verify LayerZero messages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a2K0jdpatp9ThL3U" /></figure><p><em>For those interested in using the cryptoeconomically secured LayerZero Labs DVN as part of your application’s security stack, reach out for developer assistance </em><a href="https://layerzero.network/"><em>here</em></a><em>.</em></p><h3>The Future of Omnichain Security</h3><p>This partnership marks a pivotal step toward building the next generation of omnichain messaging, where <strong>cryptoeconomic security</strong> and <strong>interoperability</strong> merge seamlessly.</p><p>The significance of this integration can be best viewed from the lens of the internet (built on protocols like TCP/IP) which enabled the standardization of digital communication, but lacked a robust commitment mechanism. Messages could be sent, but there were no strong guarantees of their delivery or integrity.</p><p>Blockchains, by contrast, serve as a substrate for global coordination, where decentralized consensus mechanisms ensure the integrity of data. EigenLayer leverages Ethereum’s decentralized trust model to create a credible commitment mechanism for applications. By integrating with LayerZero’s omnichain messaging framework, we are entering an era where the<strong> next internet</strong> — one where data can flow seamlessly between blockchains — is defined not only by interoperability but by robust commitments.</p><h3>Conclusion</h3><p>The LayerZero x EigenLayer collaboration and the CryptoEconomic DVN Framework sets a new standard for cross-chain security by merging omnichain communication with cryptoeconomic guarantees.</p><p>Through the CryptoEconomic DVN Framework, LayerZero provides a system where verifiers are incentivized to act honestly, backed by real financial stake. As this Framework is adopted, the future of blockchain communication will be defined by trust, transparency, and accountability — bringing us closer to a world where every message across blockchains is secured by cryptoeconomics.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68af27ca2040" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/layerzero-x-eigenlayer-the-cryptoeconomic-dvn-framework-68af27ca2040">LayerZero x EigenLayer: The CryptoEconomic DVN Framework</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LayerZero Labs x Initia Labs]]></title>
            <link>https://medium.com/layerzero-official/layerzero-labs-x-initia-labs-6f9eca12659c?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f9eca12659c</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[layer-zero]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[LayerZero]]></dc:creator>
            <pubDate>Wed, 10 Jul 2024 14:52:40 GMT</pubDate>
            <atom:updated>2024-07-10T14:56:04.662Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uc99DMsSyNSFFoMTgczLwQ.png" /></figure><p><em>LayerZero and Initia are developing an interoperability standard for Cosmos that enables Cosmos SDK based chains to connect to LayerZero-enabled chains, allowing for omnichain interoperability.</em></p><h4><strong>Why Cosmos?</strong></h4><p>LayerZero is an omnichain interoperability protocol that has facilitated over 135 million messages across 80+ blockchain networks, with over 200+ applications using it for messaging. LayerZero allows these applications to send and receive arbitrary data between chains that cannot natively communicate with each other.</p><p>The Cosmos SDK enables developers to create tailored blockchains known as appchains. Adding support for Cosmos is the next logical step for LayerZero in fully becoming an omnichain interoperability protocol — a full mesh network of every chain in crypto.</p><p>Initia Labs and LayerZero Labs are developing an interoperability standard for Cosmos, enabling developers to extend existing and new applications to and from Cosmos chains using any chain supported by LayerZero. This interoperability solution is in the form of a Cosmos SDK Module rather than a smart contract. It allows LayerZero to support Cosmos chains with various VMs or those without any.</p><h4><strong>Initia Labs and Initia</strong></h4><p>Initia Labs, the team behind Initia, has developed a network for interwoven rollups by fusing an L1 with a system of application-specific L2s.</p><p>Initia’s tech stack allows teams to build scalable and sovereign Cosmos SDK-based L2s in multiple VMs, simplifying the user experience for developers and end users in a new multi-chain universe.</p><p>LayerZero Labs appreciates Initia Labs’ role in the development of an interop standard for Cosmos.</p><h4><strong>Conclusion</strong></h4><p>The Cosmos vision of creating an “Internet of Blockchains,” combined with Initia Labs’ concept of “interwoven” chains, aligns seamlessly with LayerZero’s goal of omnichain interoperability across all blockchains in crypto.</p><p>LayerZero Labs is excited about the development of an interoperability standard for Cosmos with Initia Labs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f9eca12659c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/layerzero-labs-x-initia-labs-6f9eca12659c">LayerZero Labs x Initia Labs</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Addressing Sybil Activity]]></title>
            <link>https://medium.com/layerzero-official/addressing-sybil-activity-a2f92218ddd3?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/a2f92218ddd3</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[layer-zero]]></category>
            <dc:creator><![CDATA[LayerZero]]></dc:creator>
            <pubDate>Fri, 03 May 2024 15:50:12 GMT</pubDate>
            <atom:updated>2024-05-14T19:54:31.648Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wujneHGcnU5U3oOaCqffDg.jpeg" /></figure><p>Almost 6 million unique wallet addresses have interacted with LayerZero since its initial launch over two years ago. As we consider token distribution, a critical point is identifying the optimal set of users to bootstrap the network. Our conclusion is that it should be the most durable users, where durability is defined as those users most likely to continue to use the protocol or repeat past actions in the future.</p><h4><strong>Addressing Sybil Activity</strong></h4><p>A key challenge in achieving a healthy distribution is detecting <strong><em>sybil </em></strong>activities.</p><p>Examples of what we view as sybil activity within LayerZero are as follows:</p><ul><li><em>If you are a single entity with tens, hundreds, or thousands of addresses participating in industrial farming.</em></li><li><em>If you minted a “valueless” NFT for the sole purpose of moving it around chains.</em></li><li><em>If you have used popular “sybil farming” applications such as Merkly, L2Pass, L2Marathon, etc. For more information, read </em><a href="https://twitter.com/PrimordialAA/status/1786445773552439644"><em>this tweet</em></a><em>.</em></li><li><em>If you bridged $0.01 back and forth across chains for the sake of having touched a chain.</em></li><li><em>If you think you are a sybil, you are most likely a sybil.</em></li></ul><p>We are giving all sybil users an opportunity to <strong>self-report within the next</strong> <strong><em>14 days</em></strong> <strong>in return for 15% of their intended allocation, no questions asked</strong>.</p><p>If a sybil user does not self-report by the end of the 14-day period (May 17th 23:59 UTC), we will move into the following 2 phases:</p><ul><li>Phase 1: We will release our own list of all identified sybil users — those who are identified and did not self-report will receive nothing.</li><li>Phase 2: We will open a bounty where users can submit detailed reports of sybil activity. A successful report will result in the sybil user receiving nothing, and the bounty hunter receiving 10% of the sybil’s intended allocation.</li></ul><h4><strong>How to Self-Report Sybil Activity</strong></h4><p>If you are a sybil user and would like to self-report, here’s how:</p><ol><li>Visit <a href="https://sybil.layerzero.network/">sybil.layerzero.network</a></li><li>Connect a wallet associated with sybil activity</li><li>Sign message to prove ownership of address</li><li>Repeat for all sybil addresses</li></ol><p>For industrial sybil activities, we are also providing an API for mass reporting.</p><p><em>Note: All allocation eligibility will be subject to any legal or geographic requirements and each transaction is signed on-chain and should be considered permanent.</em></p><h4><strong>Conclusion</strong></h4><p>Our goal is to reward the durable users — protocols, users, and community members — who helped LayerZero succeed thus far and who will help the protocol expand in the future.</p><p>To everyone who has been part of this journey, thank you. This is only the beginning.</p><p>Stay tuned for more updates soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2f92218ddd3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/addressing-sybil-activity-a2f92218ddd3">Addressing Sybil Activity</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explaining the OFT Standard]]></title>
            <link>https://medium.com/layerzero-official/explaining-the-oft-standard-310de5e84052?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/310de5e84052</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[layerzero-labs]]></category>
            <dc:creator><![CDATA[Mark Murdock]]></dc:creator>
            <pubDate>Wed, 21 Feb 2024 22:42:06 GMT</pubDate>
            <atom:updated>2024-04-21T23:01:30.661Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZeYYv8fSHFUBI-F_" /></figure><p><em>OFTs are tokens that move across blockchains just like data packets move across the Internet.</em></p><p>This article is about OFTs, how they work, key properties, and who is using the OFT Standard.</p><p>Let’s dive in.</p><h3>What is the OFT Standard?</h3><blockquote>OFT stands for “Omnichain Fungible Token.”</blockquote><p>You can think of OFT as a <strong><em>universal token standard</em></strong> used to send, receive, and compose assets across all blockchains.</p><p>The <a href="https://docs.layerzero.network/v2/home/protocol/contract-standards#oft">OFT Standard</a> is a contract for creating and tracking tokens across many chains at the same time. It is available to anyone building on LayerZero. The OFT Standard extends fungible tokens, like ERC20, to all the chains LayerZero supports.</p><p>Projects deploying a token using the OFT Standard maintain complete ownership of their contracts, may select what chains to deploy on (now and in the future), and have the option to choose how messages are verified by configuring a unique Security Stack.</p><p>The OFT Standard has been live and in production for 21 months, securing over $4.5 billion in transfer volume across 45+ chains.</p><h3>How Do OFTs Work?</h3><blockquote>On OFT transfers and adapting existing tokens into the OFT Standard…</blockquote><h4>OFT Transfers</h4><p>OFTs operate through a mint-and-burn mechanism that works the same on every type of blockchain.</p><p><em>Transferring an OFT between blockchains involves two steps:</em></p><ul><li>First, the token is ‘burned’ (or destroyed) on the original blockchain.</li><li>Second, an equal amount of the token is ‘minted’ (or created) on the new blockchain.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dTYWDwKLVxi0dQId" /></figure><p>LayerZero facilitates this accounting process by sending a message from the source to the destination blockchain, instructing it to mint the same number of tokens that were burned. This keeps the token’s total amount the same across all networks, ensuring its value stays stable during the move and that the OFT retains a unified, global supply count.</p><h4>OFT Adapter</h4><p>For projects that have already minted a token on a single chain, the <a href="https://docs.layerzero.network/v2/developers/evm/oft/adapter">OFT Adapter</a> is available to extend that token across every LayerZero-supported blockchain. This process involves an intermediary contract that handles sending and receiving tokens that have already been deployed.</p><p>For example, when transferring an ERC20 from the source chain (Chain A), the token will lock in the OFT Adapter, triggering a new token to mint on the selected destination chain (Chain B) via the paired OFT Contract. From there, the OFT can be moved across any LayerZero-supported blockchain the project wants to enable using the burn and mint mechanism described above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ANxEk49AewlorMQW" /></figure><h3>Key Properties of the OFT Standard</h3><blockquote>Any project creating an OFT inherits the following characteristics:</blockquote><h4><strong><em>Contract Ownership</em></strong></h4><p>Inherently non-custodial, the OFT Standard allows developers to retain ownership and control over their token contracts, managing the token supply directly across each blockchain. LayerZero is intentionally designed to be an immutable protocol that has no ability to custody assets or alter the security settings or chain support of integrated contracts. <strong><em>LayerZero can never take custody of an OFT, make security decisions that would alter how an OFT transfer is verified, or disable support for a chain that an OFT is enabled on</em></strong>.</p><p>The non-custodial nature of the OFT Standard ensures that tokens remain under a project’s control, eliminating counterparty risks that are prevalent in other cross-chain solutions. Furthermore, OFT deployers may customize an optional fee structure on top of OFT transfers should they wish to generate revenue for their project.</p><h4><strong><em>Flexible Security</em></strong></h4><p>Any entity capable of verifying cross-chain messages may permissionlessly participate in LayerZero as a Decentralized Verifier Network (DVN), including native bridges, third-party bridges, oracles, etc. Applications building on LayerZero may select a combination of DVNs to attest to the validity of a cross-chain message before it is executed on the destination chain. An application’s selection of DVNs is called its Security Stack.</p><p><strong><em>LayerZero empowers token developers to select their own set of DVNs for verifying OFT transfers.</em></strong> This flexibility allows token deployers to configure <a href="https://docs.layerzero.network/v2/developers/evm/configuration/configure-dvns">customized Security Stacks</a> that align with the specific requirements of their tokens.</p><p>On top of choosing what entities verify token transfers, token issuers may also choose what chains the token is deployed on, how many blocks a DVN must wait to verify a message, and how a message is executed on the destination chain. Application owners can update configurations when new technologies emerge and expand their OFT to new chains at any time.</p><p>Additionally, the Pre-Crime module functions as an advanced security layer, proactively scrutinizing transactions for potential threats or irregularities before they are executed, thus bolstering the protocol’s defense against exploits.</p><h4><strong><em>Universal Semantics</em></strong></h4><p>OFTs bring standardization to token operations across different blockchain networks. Traditional tokens are often bound by the rules and standards of their native blockchain, leading to a fragmented experience when interacting with multiple chains. OFTs, however, maintain a consistent standard across all chains they operate on.</p><p><strong><em>This uniformity simplifies the user and developer experience, as the token behaves identically regardless of the blockchain and </em></strong><a href="https://docs.layerzero.network/v2/developers/evm/oapp/message-design-patterns#composed-pattern"><strong><em>can be composed</em></strong></a><strong><em> via a wide variety of contracts.</em></strong> Such standardization is invaluable for developers and users alike, as it reduces the complexity and learning curve associated with managing assets on multiple chains. Furthermore, developers deploying an OFT using the <a href="https://docs.layerzero.network/v2/developers/evm/configuration/configure-executor">LayerZero Executor </a>can take advantage of full gas abstraction, allowing users to pay only a single gas fee from the source chain to execute an entire cross-chain flow.</p><h4><strong><em>Unified Token Supply</em></strong></h4><p>OFTs unify liquidity across networks through swift and secure communication between contracts via burn and mint. This eliminates the need for wrapped assets (<a href="https://rekt.news/leaderboard/">4/5 largest exploits have occurred with wrapped assets, including $326M Wormhole hack in 2022</a>) and liquidity on multiple chains for bridging via standalone asset pools, paving the way for scalable liquidity across numerous L2s and L1s.</p><p><strong><em>In terms of efficiency, OFTs exist as native tokens on each chain, requiring only gas fees for transfer, devoid of additional costs associated with wrapping, bridging, or slippage.</em></strong> OFTs can be natively transferred across any LayerZero supported chains (currently 55+ chains) in a point-to-point flow, without ever needing to redeem on any one base chain.</p><h3>OFT Standard Adoption</h3><blockquote>Any type of project can utilize the OFT Standard.</blockquote><p>Over 100 projects have adopted the OFT Standard, ranging from stablecoins to gas tokens to LSTs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blRFJXyDFFuVRuCR1Dxtcw.png" /></figure><p>For the sake of brevity, we will only list a few specific examples below…</p><h4>Stablecoins</h4><ul><li><strong><em>Angle (agEUR):</em></strong> agEUR is the largest decentralized stablecoin pegged to the EURO. agEUR is available on 11 different chains. The coin has been moved<a href="https://twitter.com/AngleProtocol/status/1737892617638011116"> 7.6 million times</a> since it was launched 18 months ago.</li><li><strong><em>Abracadabra (MIM):</em></strong> Abracadabra was one of the first stablecoin projects to make their token omnichain. MIM is currently available on 11 chains.</li></ul><h4>Blockchain Tokens</h4><ul><li><strong><em>Bitcoin (BTC.b):</em></strong> <a href="https://bitcoinbridge.network/">Borderless Bitcoin</a> leverages the LayerZero Omnichain Fungible Token (OFT) standard to seamlessly integrate Bitcoin across all LayerZero-supported networks.</li><li><strong><em>Metis (METIS):</em></strong> By leveraging OFTs, Metis enhanced the movement and utility of their native tokens across various blockchain environments.</li></ul><h4>DeFi Tokens</h4><ul><li><strong><em>Trader Joe (JOE): </em></strong>The Avalanche-founded dApp Trader Joe opted into the OFT Standards in February of 2023.</li><li><strong><em>Radiant (RDNT):</em></strong> Radiant Finance uses OFTs to enhance the liquidity and transferability of its governance token across various networks.</li></ul><h4>Liquid Staking Tokens</h4><ul><li><strong><em>StakeStone (STONE): </em></strong>StakeStone native LST, $STONE, is available on Ethereum and Manta as an OFT. As of January 2024, StakeStone’s TVL is above $750 million.</li><li><strong><em>unshETH (unshETH):</em></strong> unshETH<a href="https://mirror.xyz/0x749Dc728A68265e74754Ad8e6cc2649BD42a8f8a/t7vYrWdiqPycEhm956mqEDbPa8F6tNxeKCcxFP11_AQ"> expanded</a> to BNB Chain from Ethereum by making its LST $unshETH an OFT in April 2023.</li></ul><h3>Conclusion</h3><p>The OFT Standard represents a unified, secure, and user-friendly approach to tokenization.</p><p>OFT is one token standard for many chains that can use any type of verification method to approve token transfers.</p><p>As the industry continues to expand to 1000s of chains, the OFT Standard is here to enable unified token supply and liquidity while empowering token issuers to control the security specifications protecting asset transfers.</p><p><em>For more information on OFTs, listen to the LayerZero Lounge, where our DevRel team broke down many of the topics above in </em><a href="https://twitter.com/LayerZero_Labs/status/1758189865110552889"><em>audio format</em></a><em>.</em></p><h3>Contact</h3><p>If you’re considering bringing your token cross-chain or have questions about how to implement the OFT Standard for your project, reach out to bd@layerzerolabs.org. The team can offer solutions and next steps on how to deploy an OFT.</p><ul><li>For specific OFT inquiries, fill out this<a href="https://layerzeronetwork.typeform.com/to/U9hMgxf1"> form</a>!</li></ul><p>For more information on LayerZero, check out this<a href="https://twitter.com/LayerZero_Labs/status/1752014702287437907"> thread</a>, read this<a href="https://www.notboring.co/p/layerzero-the-language-of-the-omnnichain"> article</a>, check out our<a href="https://docs.layerzero.network/"> docs</a>, or visit the<a href="https://layerzero.network/"> website</a>. For additional information, the LayerZero Labs team is available to answer general questions on<a href="https://discord-layerzero.netlify.app/discord"> Discord</a> and<a href="https://t.me/joinchat/VcqxYkStIDsyN2Rh"> Telegram</a>. You can also follow LayerZero Labs on<a href="https://twitter.com/LayerZero_Labs"> X</a> to receive the most up-to-date information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=310de5e84052" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/explaining-the-oft-standard-310de5e84052">Explaining the OFT Standard</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LayerZero V2: Explaining DVNs]]></title>
            <link>https://medium.com/layerzero-official/layerzero-v2-explaining-dvns-02e08cce4e80?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/02e08cce4e80</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[layer-zero]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Mark Murdock]]></dc:creator>
            <pubDate>Fri, 09 Feb 2024 17:58:15 GMT</pubDate>
            <atom:updated>2024-04-22T21:54:01.896Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jFqPT0Gax7rlUXaV" /></figure><p>This article focuses on the verification of messages sent across LayerZero, which is accomplished by entities called Decentralized Verifier Networks (DVNs).</p><p><em>Looking for a complete deep dive into LayerZero V2? Read it</em><a href="https://medium.com/layerzero-official/layerzero-v2-deep-dive-869f93e09850"><em> here</em></a><em>.</em></p><p><em>You can also listen to a recent Twitter space LayerZero Labs hosted that</em><a href="https://twitter.com/LayerZero_Labs/status/1753116163863920910"><em> explains</em></a><em> DVNs from the perspective of the teams that run them.</em></p><h3>What is a Decentralized Verifier Network (DVN)?</h3><p>Every application built on LayerZero can <a href="https://docs.layerzero.network/v2/developers/evm/configuration/configure-dvns">Configure a Security Stack</a> comprised of a number of required and optional Decentralized Verifier Networks (DVNs) to check the payloadHash emitted for message integrity, specifying an optional threshold for when a message nonce can be committed as Verified.</p><p>In other words, DVNs are the entities responsible for verifying messages sent across chains by applications that use LayerZero.</p><h3>Who Can Run a DVN?</h3><p>LayerZero is permissionless.</p><p>Therefore, any entity can <a href="https://docs.layerzero.network/v2/developers/evm/off-chain/build-dvns">build a DVN</a> or develop a <a href="https://docs.layerzero.network/v2/home/modular-security/security-stack-dvns#dvn-adapters">DVN Adapter</a> as long as its verification schema can confirm the integrity of a message’s payloadHash.</p><p>This leads to a wide array of DVN options for application developers to select from, spanning multiple client types, validation methods, validation sets, and proving techniques.</p><p>For example, a single DVN may require the participation of 20 validators spread across multiple continents and be run by a crypto-native Ethereum research organization. Another DVN may involve a handful of signers from a curated group of enterprises. More novel DVNs may leverage a re-staking protocol and implement economic security or slashing mechanics.</p><p>Over 30 DVNs are currently available to applications building on LayerZero, spanning verification methods that use zk-technology, middlechains, consortium signers, and third-party bridges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GK--WYy5lWmJ8EFJ" /><figcaption>Example DVNs</figcaption></figure><p>A full list of DVNs available can be found <a href="https://docs.layerzero.network/v2/developers/evm/technical-reference/dvn-addresses">here</a>.</p><p>DVNs coming soon include native bridges, more third-party bridges, restaking services, zkOracles, and MPC wallets.</p><h3>Why are DVNs Important?</h3><p>Applications built on LayerZero may choose any DVN (or combination of DVNs) to verify messages going between chains. The selected configuration of DVNs is part of an application’s Security Stack.</p><p>The LayerZero protocol was deliberately designed to take an unbiased stance on how messages are verified. Rather than enforcing one fixed security approach, LayerZero hands ownership of security over to the applications themselves.</p><p>We believe developers should choose the verification methodology that fits their project’s needs and that it<em> can</em> and <em>should</em> evolve over time with research and project growth without any compromise to long term security.</p><p>This is a design choice that differs from most messaging protocols and services, which instead offer only a single shared security configuration, continually updating a single, monolithic end-to-end security model (i.e. validator set, oracle, middlechain, etc) to include new chains.</p><p>A one-size-fits-all approach to security often leads to applications either under or overpaying for security. For example, an omnichain NFT project has much lower security needs than an omnichain money market. One project secures &lt; 0.5 ETH value transfers, while another may secure $1B+. However, if both are built on a shared security cross-chain protocol, their projects — and user base — pay the same amount for security (shown below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GRCh71C3i0nrXY46" /><figcaption>Monolithic Security</figcaption></figure><p>In contrast, with a diverse and growing set of DVNs, LayerZero developers can configure security parameters to best suit their application rather than being forced to fit their application into a rigid, monolithic architecture. This not only allows for more immediate flexibility, but it also future-proofs applications. For instance, without writing any additional code, an application can swap an optimistic oracle DVN for a battle-tested zkOracle as new technologies become available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wNwtJCzuGcVdGS2i" /><figcaption>Modular Security</figcaption></figure><p>Research and time will introduce safer and more sophisticated methods of securing information delivered between chains. LayerZero V2 enables such advancements to be leveraged in the future.</p><h3>How are DVNs Used in Practice?</h3><p>An application’s “Security Stack” refers to its unique configuration of DVNs, Executors, and other security preferences. This includes choices such as enabled chains and the number of block confirmations DVNs must wait for message verification.</p><p><em>For the purpose of this article, we will only focus on the DVN aspect of the Security Stack.</em></p><p>The concept called “X of Y of N” is the core of the Security Stack. It is the configuration of DVNs inside a Security Stack, describing how applications select and/or remove DVNs to verify messages. (<em>Editor’s note: video explanation</em><a href="https://twitter.com/LayerZero_Labs/status/1737514025062432837"><em> here</em></a><em>.</em>)</p><p>X of Y of N allows applications to combine DVNs however they like. Application developers can designate a quorum of DVNs to check the integrity of a cross-chain message before signing off on its validity.</p><p>For instance, a “1 of 3 of 5” combination of DVNs would include one required DVN and two arbitrary DVNs out of a total of five to verify a message before moving on to execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m8MIYjAR21o9mbsU" /><figcaption>Example of a DVN setup!</figcaption></figure><p>When building a strong Security Stack, applications should combine DVNs that minimize collusion and/or hack risk. For example, a DVN setup of Google Cloud and the Axelar DVN Adapter is a very hard Security Stack, as it includes verification from a centralized and a decentralized entity, minimizing collusion risk (and more DVNs can be added to this setup later on).</p><p>To minimize risk, applications can run their own DVN, reach out to DVN teams to perform due diligence, and/or choose a DVN combination where it is impossible to collude.</p><h3>Conclusion</h3><p>V2 is about connecting blockchains, universal development, and <strong>application-owned security</strong>.</p><p>With V2, LayerZero is the antithesis of vendor lock-in, allowing developers to choose, modify, and combine different types of verification methods based on a specific use case.</p><p>Eliminate silos. Build everywhere.<strong> Own security.</strong></p><p><strong><em>Thank you to</em></strong><a href="https://twitter.com/IreneWu27"><strong><em> Irene</em></strong></a><strong><em> for co-writing this article.</em></strong></p><h3>Contact</h3><p>For more information on V2, check out this<a href="https://twitter.com/LayerZero_Labs/status/1752014702287437907"> thread</a>, read this<a href="https://www.notboring.co/p/layerzero-the-language-of-the-omnnichain"> article</a>, or check out our<a href="https://docs.layerzero.network/"> docs</a>. To learn more about LayerZero in general, check out the<a href="https://layerzero.network/"> website</a>. For additional information, the LayerZero Labs team is available to answer general questions on<a href="https://discord-layerzero.netlify.app/discord"> Discord</a> and<a href="https://t.me/joinchat/VcqxYkStIDsyN2Rh"> Telegram</a>. You can also follow LayerZero Labs on<a href="https://twitter.com/LayerZero_Labs"> X</a> to receive the most up-to-date information.</p><ul><li>For specific DVN inquiries, fill out this<a href="https://layerzeronetwork.typeform.com/to/U9hMgxf1"> form</a>!</li></ul><h4>About LayerZero</h4><p>LayerZero is a permissionless, censorship-resistant, and immutable protocol that connects blockchains. Using LayerZero, developers can send and compose arbitrary messages across chains while preserving full control over their application’s security.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02e08cce4e80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/layerzero-v2-explaining-dvns-02e08cce4e80">LayerZero V2: Explaining DVNs</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LayerZero V2 Deep Dive]]></title>
            <link>https://medium.com/layerzero-official/layerzero-v2-deep-dive-869f93e09850?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/869f93e09850</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Mark Murdock]]></dc:creator>
            <pubDate>Tue, 30 Jan 2024 18:31:14 GMT</pubDate>
            <atom:updated>2024-04-21T22:55:53.123Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rkjUuh8qnv44NtKM" /></figure><p>This article broadly explains LayerZero in the context of <a href="https://twitter.com/LayerZero_Labs/status/1752014702287437907">V2 going live</a>. From a technical standpoint, it will explore the “what” of LayerZero V2, including its design, security, and trust assumptions. From a discussion standpoint, it will also attempt to rationalize the “why” of LayerZero through a general analysis of the core principles of the protocol and an exploration of the ramifications of V2 on other interop solutions.</p><p>Here is an outline of the article:</p><p><em>What Is LayerZero?</em></p><ul><li>Explaining LayerZero — a definition that everyone can understand</li><li>Core Principles — immutable, permissionless, censorship-resistant</li></ul><p><em>How Does V2 Work?</em></p><ul><li>V2 Architecture — protocol, standards, infrastructure</li><li>V2 vs V1 — key highlights comparing the two, with a focus on Security Stacks</li><li>V2 Transaction Lifecycle — how to send a message in four steps</li><li>Use Cases — identity, stablecoins, and lending markets</li><li>V2 Trust Assumptions — endpoint deployments, collusion risk, 2/2 multisig, and more</li></ul><p><em>LayerZero and the Market</em></p><ul><li>Bridges — how V2 inhales the bridge industry (messaging and liquidity)</li><li>OApp and OFT — why everyone should use V2 contract standards</li></ul><p><em>Closing Thoughts</em></p><h3>What Is LayerZero?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OMTx_5yPpqLG1viF" /><figcaption>What is LayerZero?</figcaption></figure><h4><strong>Explaining LayerZero</strong></h4><p>Depending on who you are — your job, your portfolio, your education, your predilection for memes — how you understand LayerZero will likely differ. It’s the same way with most crypto primitives. For instance, a financial manager, an Uber driver, and your grandmother will likely have different definitions for what Bitcoin is. In that example, Bitcoin is probably something akin to digital gold, an investment, or darknet money that is used by criminals, respectively.</p><p>With that in mind, having a single definition for LayerZero seemingly defeats the purpose. Here are a few different ways to explain LayerZero, curated to a few of the most likely readers of this piece:</p><p><strong><em>For the whitepaper enthusiasts:</em></strong></p><p>Utilizing an immutable endpoint, append-only verification modules, and fully configurable verification infrastructure, LayerZero provides the security, configurability, and extensibility necessary to achieve omnichain interoperability. LayerZero enforces strict application-exclusive ownership of protocol security and costs through its novel trust-minimized modular security framework designed to support all blockchains and use cases universally. Omnichain applications (OApps) built on the LayerZero protocol achieve frictionless blockchain-agnostic interoperation through LayerZero’s universal network semantics.</p><p><strong><em>For the nerds:</em></strong></p><p>LayerZero is a verification agnostic transport layer that enables smart contracts on different blockchains to interoperate. It is a fully connected mesh network not bound to any infrastructure or blockchain. LayerZero is an “omnichain” protocol enabling developers to build unified applications with modular security parameters.</p><p><strong><em>For the web3 developers:</em></strong></p><p>LayerZero is an immutable, permissionless, and censorship-resistant protocol connecting previously siloed blockchains. Using LayerZero, developers can send arbitrary messages across chains while preserving complete control over their application’s security. LayerZero enables developers to create and configure unified applications, tokens, and data primitives, regardless of chain. This concept of unified cross-chain development is encapsulated in the word “omnichain” and is what LayerZero envisions the future of crypto moving towards.</p><p><strong><em>For the technology enthusiasts:</em></strong></p><p>LayerZero is to blockchains what TCP/IP is to the internet. Where TCP/IP allows different computers running different operating systems on different networks to communicate (resulting in a connected internet), LayerZero enables smart contracts coded in different languages on different blockchains to communicate. This allows developers to create applications that exist universally across blockchains.</p><p><strong><em>For your TradFi friend who you thought understood but clearly didn’t:</em></strong></p><p>Imagine your Windows computer couldn’t send an email to your boss’s Mac, or your Android phone couldn’t send a text message to your mother’s iPhone. We take this for granted, but it’s all powered by a communication protocol named TCP/IP that glues the Internet together. LayerZero is that communication protocol, but for blockchains. Before LayerZero, Ethereum couldn’t communicate with Bitcoin, and neither blockchain could communicate with Solana. With LayerZero, developers and users can interact with applications and tokens that exist on many blockchains through a single protocol, similar to how Mac, Linux, and Windows users can all communicate across the same Internet (early alpha: LZ + Solana, coming in 2024).</p><p><strong><em>For the dinner table at Thanksgiving:</em></strong></p><p>LayerZero is like the Internet, which opened up communication to the world — email, social media, zoom calls, etc. LayerZero will do that, but for crypto — meaning finance will be open, with anybody able to move value, take out loans, trade assets, etc, without going through an intermediary like a bank or a potential censor like a government.</p><h4><strong>Core Principles</strong></h4><p>It is important to remember why we are here — to build an open and just digital economy for all people, for all time. Crypto is a space that should be permissionless, allowing anyone to interact with applications. Crypto should be censorship-resistant, facilitating the movement of data packets without judgment. Crypto should exist forever, leaving behind systems that are immutable and provable, unchanging. In general, it is pertinent that the protocol to connect crypto is designed to combat corruption so that whatever we are building in this space may stay parallel to the legacy system rather than become part of it.</p><p>LayerZero’s design mirrors these core principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fj7rFLYIeveStAKX" /><figcaption>LayerZero core principles.</figcaption></figure><ul><li><strong>Immutable</strong></li></ul><p>Endpoints (the interface for interacting with LayerZero) exist as immutable smart contracts on each chain LayerZero supports. These are non-upgradeable and cannot be changed by any party, providing a safe and predictable interface to interact with. Every piece of core protocol code is non-upgradable. Neither LayerZero Labs nor anyone else besides the owner of the omnichain application has the ability to change an application’s security configuration (unless Defaults or a delegate is selected to do so).</p><ul><li><strong>Censorship-Resistant</strong></li></ul><p>Individual messages can only be executed once all previous messages have been verified, meaning no individual message can ever be censored on any pathway. There is no ability for the LayerZero protocol to selectively deliver messages once they’re successfully submitted on the source chain. If a transaction is successfully submitted on the source chain, it is guaranteed to be delivered to the destination chain.</p><ul><li><strong>Permissionless</strong></li></ul><p>LayerZero is a pure protocol. Anyone can run the infrastructure that verifies and executes messages sent via LayerZero. If every developer and infrastructure provider stopped performing services, anybody could come in to join the protocol and pick up right where they left off. Furthermore, anyone may build on top of LayerZero and interact with those applications.</p><h3>How Does LayerZero Work?</h3><h4><strong>V2 Architecture</strong></h4><p>The core design of LayerZero V2 can be bucketed into three categories: protocol, standards, and infrastructure.</p><p><strong>Protocol →</strong> These aspects of LayerZero protocol remain the same across every supported blockchain. In the <a href="https://layerzero.network/publications/LayerZero_Whitepaper_V2.0.pdf">V2 whitepaper</a>, the protocol of LayerZero is what is deemed “intrinsic” — these are the contracts that will last forever (immutable), that anybody may build on top of (permissionless) and that enforces how transactions are ordered (censorship-resistant). The protocol comprises two entities, Endpoints and MessageLibs.</p><ul><li><a href="https://docs.layerzero.network/v2/home/protocol/layerzero-endpoint">Endpoints</a>: These are immutable smart contracts on each chain LayerZero supports. The Endpoint is the core of the LayerZero protocol. Once implemented, no entity cannot change endpoints, as they are immutable and non-upgradable. Endpoints offer a standardized interface for applications to manage security configurations and send/receive messages — the two most important things an application will want to control when building on top of LayerZero.</li><li><a href="https://docs.layerzero.network/v2/home/protocol/message-library">Message Libraries</a>: Each MessageLib is registered to an Endpoint and is how an application’s security configuration and data packet sending/receiving process is enforced. In other words, the MessageLib is how an Endpoint is fed information about the message being sent between blockchains — it is where the verification and communication of messages occurs. Notably, MessageLibs are append-only additions to Endpoints. This means they cannot be removed (still immutable) while allowing the protocol to upgrade verification methods when necessary. Developers building on LayerZero will never be forced to accept or update to a new MessageLib. To analogize here, consider LayerZero Endpoints as a blockchain and new MessageLibs as smart contracts. Just like how Uniswap updates its contracts through new product releases (UniswapV1, UniswapV2 and UniswapV3) and people can still use the old contracts, LayerZero may publish new MessageLibs, and people may still choose to use the older libraries.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ulOnytTGCiIOTPEP" /><figcaption>Depiction of a LayerZero Endpoint.</figcaption></figure><p><strong>Standards → </strong>These enable the concept of “unified semantics” — where an application/token works the same across every LayerZero-supported blockchain. Unified semantics enable developers to easily build interfaces that interact with applications across tens of blockchains without having to rewrite code for new environments. LayerZero standards include how omnichain smart contracts are written, how data packets are structured, and how logic is composed. Anything a developer might need to launch an omnichain product from scratch can be found as audited, reusable, and battle-tested standards.</p><ul><li><a href="https://docs.layerzero.network/v2/developers/evm/overview">Contract Standards: </a>LayerZero offers developers out-of-the-box message handling and configuration for applications (<a href="https://docs.layerzero.network/contracts/oapp">OApp</a>) and tokens (<a href="https://docs.layerzero.network/contracts/oft">OFT</a>). OApp and OFT are extensions of existing contract standards — for example, OFT extends ERC-20s — and maximally cut down development time for building cool things. In the case of OApp and OFT, both contract standards allow developers to create universal applications and tokens that work the same across all LayerZero-supported chains. <a href="https://layerzero.gitbook.io/docs/evm-guides/contract-standards/onft-overview">ONFT</a> contract standards are already available in V1 and will be available in V2 later this year.</li><li><a href="https://docs.layerzero.network/v2/home/protocol/packet">Message Packets</a>: This is how information is passed between chains. Each cross-chain message requires information to be formatted in a specific manner so that destination-chain activities may occur without issue. The Message Packet for LayerZero requires a nonce, source ID, sender address, destination ID, receiving address, a unique identifier, and the message payload. The nonce, source/destination IDs and unique identifier prevent replay attacks and misrouting, while also helping track the message across chains. The payload field carries the actual information or command that needs to be carried out on the destination chain. With this information correctly formatted, any generic message can be passed between chains, allowing for the transfer of data, assets, and/or external contract calls. This Message Packet format extends across any blockchain environment (EVM and non-EVM, public chains and private chains). Most of this formatting relating to packet data, such as nonce management, is handled directly by Endpoints.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oAZQGHL__AiHs1MI" /><figcaption>LayerZero message packet.</figcaption></figure><ul><li><a href="https://docs.layerzero.network/v2/developers/evm/oapp/message-design-patterns">Design Patterns</a>: LayerZero comes with a built-in set of design patterns, which can be thought of as omnichain building blocks. Developers building on LayerZero can use these design patterns to create almost anything they want. At the moment, there are four basic design patterns:</li></ul><blockquote>AB: a one-way data transfer from source to destination.</blockquote><blockquote>ABA: a nested send call from Chain A to Chain B back to Chain A.</blockquote><blockquote>Composed AB: a message is transferred from Chain A to Chain B and calls an external contract on Chain B.</blockquote><blockquote>Composed ABA: moves data from source to destination, executes a contract call, and then sends it back to the source chain. (shown below.)</blockquote><blockquote>Composed ABC: moves data from source to destination, executes a contract call, and sends information to a third chain.</blockquote><blockquote>Batch Send: a single call that goes out to multiple destination chains.</blockquote><p>While these design patterns may not seem like a big deal, design patterns are the legos for building omnichain applications and help developers create slick user experiences. For example, tokens can be bridged and swapped through a composed AB in a single transaction that only requires gas on the source chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2yvYBxfQcVJNod-P" /><figcaption>Composed ABA design pattern.</figcaption></figure><p><strong>Infrastructure →</strong> The infrastructure layer of LayerZero is built to be permissionless: anybody can run the entities necessary to both verify and execute transactions. The infrastructure stack is also built to be completely modular — applications can choose what type of verification method it wants to use, along with what entities they want to pay for execution.</p><ul><li><a href="https://docs.layerzero.network/v2/home/modular-security/security-stack-dvns">Decentralized Verifier Networks (DVNs)</a>: DVNs verify cross-chain messages. This permissionless role empowers any entity capable of verifying cross-chain data packets to join LayerZero as a DVN. Any native bridge, third-party bridge, middle chain, oracle, or other verification method may be used as a DVN inside V2, thereby avoiding vendor lock-in at the security level. As V2 has a modular design, application owners can combine DVNs to maximize verification for characteristics like security, cost, speed, or any parameter an application might want. Currently, 15+ DVNs are available, including DVNs run by Google Cloud and Polyhedra’s zklight client running DVNs and adapter DVNs for Axelar and CCIP. Again, as this is a permissionless role, any entity may set up a DVN and/or create an Adapter for a third-party bridge.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0Ru8qFkWuwbMzVha" /><figcaption>Where DVNs reside in the V2 architecture.</figcaption></figure><ul><li><a href="https://docs.layerzero.network/v2/home/permissionless-execution/executors">Executors:</a> Any entity can run an Executor, as it is an entirely permissionless role. The Executor ensures the smooth execution of a message on the destination chain by offering gas abstraction to the end-user. Executors do this by quoting end-users on the source chain in the source chain gas token while executing the transaction automatically on the destination chain. Much like applications can select a DVN set, they can also configure their application to choose a certain Executor or group of Executors. Applications also have the ability to build and run their own executor (as they can for DVNs) or operate without an Executor and have end-users manually invoke lzReceive via <a href="https://layerzeroscan.com/">LayerZero Scan</a>.</li><li><a href="https://docs.layerzero.network/v2/developers/evm/configuration/configure-dvns">Security Stack</a>: An application’s “Security Stack” references its unique configuration of DVNs, Executors, and other security preferences (like what chains are enabled and how many block confirmations DVNs must wait to verify a message). The Security Stack enables “application-owned security” and differentiates LayerZero from many other interop solutions. Instead of locking developers into a single shared security model or a single set of validators, Security Stacks allow developers to select how their cross-chain messages are verified and change that configuration if a new DVN comes to market or a certain DVN hits liveness obstacles.</li></ul><h4><strong>V2 vs V1</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wCTi6CaLHS0Kg3CS" /></figure><p>The goal of V2 is not to completely overhaul a system. Instead, it is to take the V1 design and emphasize focus on the core principles of LayerZero: permissionless, censorship-resistant, and immutable.</p><p>The following five changes from V1 to V2 improve the developer experience and harden LayerZero’s core principles.</p><p><strong><em>V2 vs V1 </em>highlights<em>:</em></strong></p><ul><li><em>Decoupling Execution from Verification:</em> Previously, the Relayer was accountable for verification and execution. In V2, the Executor is separated from the verification process. Where the Relayer entity was a <em>hypothetical</em> bottleneck in V1 if it were to experience downtime (as of now, this has not been an issue), in V2, there will be no liveness issues. In V2, execution is a permissionless role outside the protocol and verification process.</li><li><em>X of Y of N:</em> This modular approach to verification empowers applications to neither overpay nor underpay for security, depending on their use case. X of Y of N allows applications to combine DVNs however they like. For instance, a “1 of 3 of 5” combination of DVNs would include one required DVN and two arbitrary DVNs out of a total of five to verify a message before moving on to execution. This means that if two DVNs outside the required DVN were unresponsive out of five, message flow could continue, greatly aiding liveness. (<em>Editor’s note: The 2/2 multisig meme put forward around V1 by critics is wrong, as the Oracle is modular. However, with X of Y of N, that meme can be declared officially dead.)</em></li><li><em>Horizontal Composability</em>: Previously, applications were forced to compose omnichain transactions vertically, leading to transactions failing in their entirety if the final leg of a transaction failed. With horizontal composability, each leg of a transaction is saved locally on the destination chain. For example, only once the swap from source to destination is successful is the composed logic on the destination side executed (for example, logging the swap details on a separate contract). If that logging failed, it wouldn’t break the transaction, and the swap would still be successful, whereas the entire swap would have reverted with vertical composability.</li><li><em>Unordered Delivery:</em> Previously, all messages were verified and executed in order. V2 allows developers to choose whether to execute transactions in or out of order. With out-of-order transaction execution, LayerZero’s throughput matches the destination chain while maintaining censorship resistance.</li><li><em>Enhanced Programmability</em>: V2’s improved protocol contract interfaces, path-specific libraries, new design patterns, and horizontal composability redefine application interaction, fostering flexibility and uninterrupted cross-chain transactions.</li></ul><p>Let’s expand on X/Y/N and Security Stacks, as these are probably the most important concepts to understand when building on V2.</p><p>X of Y of N allows an application developer to designate a quorum of DVNs to check the integrity of a cross-chain message before signing off on a message’s validity. For example, “1 of 9 of 15” requires consensus from the following DVNs for a message to be verified:</p><ul><li>9 from a selected pool of 15 DVNs, and</li><li>1 required DVN</li></ul><p>Regarding the required signer aspect of X of Y of N — this allows applications to harden their verification significantly by running their own DVN and requiring themselves to sign off on each transaction. That way, even if other DVNs collude to sign a malicious transaction, their application would be safe.</p><p>X of Y of N is the core of the Security Stack, allowing applications to select, combine, and/or remove DVNs to verify messages however they deem fit. This lets applications improve security as new verification methods enter the market or reconfigure DVNs if risks arise.</p><p>Security Stacks should generally be configured based on a project’s use case. For example, a cross-chain lending dApp may configure its Security Stack to the most decentralized set of DVNs possible and set a high number of blocks for confirmation, while a financial institution building an ecosystem of subnets may choose to run its own DVNs in its Security Stack with very minimal confirmation time. For inexpensive use cases or testing, developers can set a 1/1/1 quorum. However, if someone were to build an application that moved millions in value across chains sporadically, a quorum of 5/20/25 DVNs might be used.</p><p>Security Stack flexibility benefits the developer because it future-proofs an OApp by not locking it into a single verification method. If, for example, a DVN were to go down due to a hack or government subpoena, an OApp could change its Security Stack to require a signature from a different DVN.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QLwLLMEVEcEVJuv_" /><figcaption>Applications using LayerZero</figcaption></figure><p>This unbiased stance on verification is a design choice that differs from most other messaging protocols, which often offer only a single security configuration. Outside of IBC, Hyperlane, and a few others… most cross-chain protocols adopt a shared approach to security, continually updating a single, monolithic end-to-end security model (like a validator set, oracle, middlechain, etc) to include new chains.</p><p>A one-size-fits-all approach to security will often lead to applications under or overpaying for security. For example, an omnichain NFT project has much lower security needs than an omnichain money market. However, if both are built on a middle-chain-enabled cross-chain protocol, they pay the same amount for security. In addition, using a single monolithic protocol leads to a one-size-fits-all approach to extensibility, as each verification method may only support a limited number of chains. With a modular set of DVNs, LayerZero allows developers to configure security parameters that best suit their application rather than forcing them to fit an application into a rigid, monolithic architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nD7xd7rAN2w5FLpq" /><figcaption>Applications using a shared security model protocol.</figcaption></figure><p>In building out Security Stacks, a diverse range of opinions is expected regarding the security of an application. There will be some proponents that say a Security Stack with just one DVN is enough (those would be developers currently building on single middle-chains), while others might say that anything less than a 1 required, 4/5 Security Stack is insecure. Whatever might be said, LayerZero protocol is unopinionated — it is only the transport layer and will stay verification agnostic.</p><p>With Security Stacks, LayerZero is the antithesis of vendor lock-in, as it allows developers to choose, modify, and combine different types of verification methods based on their specific use case.</p><h4><strong>V2 Transaction Lifecycle</strong></h4><p>For this example, let us assume that an application (OApp) has configured its Security Stack on the LayerZero Endpoint for both the source and destination blockchains. It has also selected its preferred version of MessageLib.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZbKOHpOuJ0FZQxGf" /><figcaption>LayerZero Tx Lifecycle</figcaption></figure><p>Step 1a: Sending the Message</p><ul><li>The source chain OApp calls `lzSend` on the source LayerZero Endpoint, providing the message payload and its unique path.</li><li>The path is designed to be secure and resistant to censorship, constructed from the sender and recipient application addresses and their respective Endpoint IDs.</li></ul><p>Step 1b: Encoding and Emitting the Packet:</p><ul><li>The source Endpoint assigns a unique, sequentially increasing nonce to the packet.</li><li>It combines the nonce with the path to create a Global Unique Identifier (GUID) for tracking the packet.</li><li>The Endpoint selects the correct source MessageLib (like ULN) based on the Security Stack to encode the packet.</li><li>The packet is encoded with necessary information, including payment for DVNs to verify the message and Executors for triggering offchain actions.</li></ul><p>Step 2: Verification by DVNs:</p><ul><li>Configured DVNs independently verify the packet on the destination side using the destination MessageLib.</li><li>After the packet is verified by the sufficient number of DVNs required by the Security Stack, it is committed to the destination Endpoint by an appropriate worker (a DVN, executor, or user).</li></ul><p>Step 3: Receipt and Execution:</p><ul><li>Endpoint ensures payload verification aligns with the OApp-configured Security Stack before committing to the channel.</li><li>An executor invokes the `lzReceive` function to process the received packet with the Receiver OApp’s logic.</li><li>This step ensures the message is delivered exactly once and without loss. If the system cannot guarantee this, the process is reverted to prevent any possibility of censorship.</li></ul><h4><strong>V2 Use Cases</strong></h4><p>LayerZero is a big idea — anything that can be programmed as a smart contract on a single chain can now be natively programmed across multiple chains (which leads to far more expressive applications being built than what currently exists on the single-chain market).</p><p>Since inception, many products have been built on LayerZero, including borrow/lend dApps, cross-chain identity dApps, bridges, NFT marketplaces, enterprise projects, NFT projects, meme tokens, and data products. Over <a href="https://layerzeroscan.com/">40,000 OApp</a> contracts are deployed on LayerZero V1, 100s of teams are using LayerZero to power OFTs, and dozens of teams have built full-scale applications as groupings of OApps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k8iiWunxYn9T3-KC" /></figure><p>For developers, LayerZero composability extends DeFi beyond single-chain limitations, paving the way for a more interconnected and versatile financial ecosystem. With LayerZero, the scope of applications built in DeFi expands as developers leverage more assets and blockchains. Furthermore, with the ability to run a DVN, application developers can harden security by decreasing reliance on other parties.</p><p>For users, V2 simplifies cross-chain transactions, allowing them to interact with multiple blockchains without even knowing — as they only have to pay for gas on the source chain. This streamlined experience can be adopted across every DeFi vertical — from DEXs to yield farms to NFT marketplaces — reducing the complexity for end-users. The endgame for retail DeFi is to completely abstract the chain away from users, and LayerZero OApp and OFT contracts are tools to facilitate this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cHLlkzaxIt1FbDXy" /></figure><p>To give a concrete idea of what can be built with V2, here are a few examples of applications leveraging LayerZero V2…</p><ul><li><a href="https://clusters.xyz/"><strong>Clusters (Identity):</strong></a><strong> </strong>Clusters is a cross-chain, multi-wallet name service protocol addressing issues like address fragmentation, wallet management complexity, and domain squatting. It serves as a unified identity layer, enabling users to maintain a consistent identity across multiple chains — very similar to what ENS does, but for many chains, natively. Clusters ensures that actions and configurations associated with a user’s identity are consistently reflected across all integrated blockchains, thereby streamlining user interaction with various decentralized applications (dApps) and services. On the backend, LayerZero is used as the messaging layer to move actions and state changes across chains to help Clusters maintain accuracy across millions of names and billions of wallet addresses. (<em>alpha 2.0</em>.)</li><li><a href="https://docs.abracadabra.money/learn/"><strong>Abracadabra (Stablecoin)</strong></a>: Magic Internet Money (MIM) introduces an omnichain “beaming” service for transferring MIM tokens across 11 blockchains. Utilizing LayerZero’s Omnichain Fungible Token (OFT) standard, MIM beaming offers fast, secure, and efficient token transfers. This service extends MIM’s functionality, enabling cross-chain interactions like borrowing from different chains, executing cross-chain liquidations, and more. A nominal beaming fee of 1 USD, charged in the native gas token of the origin chain, contributes to DAO profitability. Abracadabra also <a href="https://docs.layerzero.network/contracts/dvn-addresses#abracadabra">runs its own DVN</a> (MIMnet), which will be a required signer for MIM transfers once it transitions to V2. Since launching on V1, Abracadabra has facilitated two million transfers on LayerZero.</li><li><a href="https://docs.tapioca.xyz/tapioca/"><strong>Tapioca (Lending Market)</strong></a>: Tapioca DAO is an omnichain lending &amp; borrowing platform offering a native omnichain CDP stablecoin, USDO. The primary vision behind Tapioca is to reunify currently fragmented liquidity in DeFi by creating a natively omnichain borrowing, lending, and stablecoin protocol, where the user experience is identical to a user borrowing and lending on the same chain. Additionally, to complete the full finance stack, Tapioca users can employ cross-chain leverage with Tapioca through recursive messages. From a verification perspective, Tapioca <a href="https://docs.layerzero.network/contracts/dvn-addresses#tapioca">operates a DVN</a> that is a required signer in its own Security Stack. An example of this setup is shown below:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sn1eeHrRx4JP1DYX" /><figcaption>Tapioca’s V2 Security Stack</figcaption></figure><h4>V2 Trust Assumptions</h4><p>There is no such thing as a perfect system. Anybody claiming to have created something perfect in crypto should be met with scrutiny, as blockchains themselves are inherently limited to a core trade-off between speed, scale, and security.</p><p>This section discusses the trust assumptions, or security considerations, that a developer may encounter when building on top of LayerZero. Not all of these are protocol risks — many are practical risks that address social or application-level security. That being said, in good faith, we will address all types of trust assumptions here.</p><p>(<em>Editor’s note: No pictures from here on out. Only niche interop analysis.</em>)</p><p><strong>Smart Contract Risk:</strong> Endpoints and MessageLibs are the basis for cross-chain communication for LayerZero. If these contracts contain a bug, then the core protocol is at risk.</p><ul><li>This is the case with any protocol that utilizes smart contracts. While not a perfect measurement, looking at time-in-market for source code is usually a good indicator that a contract can be trusted. With that in mind, V1 Endpoints have been live for 1.5 years without error, facilitating over $40 billion in value transfer and over 100 million messages. With the launch of V2, these numbers are reset to existing V2 testnet volume and transactions, so it will take time to build the time-in-market trust back up, much like Uniswap upgrades take time to surpass their priors (Uniswap V2 trading quantity was <a href="https://medium.com/coinmonks/uniswap-v2-vs-v3-by-the-numbers-10b37124b087">higher</a> than V3 for roughly six months). Of course, time-in-market is not the only metric for smart contract risk. Audits are also a good indicator. With V2, all contracts have been <a href="https://github.com/LayerZero-Labs/LayerZero-v2/tree/main/audit">audited</a>, and there is a $2.5 million bug bounty for whitehats. <a href="https://layerzero.gitbook.io/docs/security/bug-bounty-program">The V1 bug bounty of $15 million</a> is currently the largest in the world.</li></ul><p><strong>Malicious Developers:</strong> Developers are responsible for setting their own Security Stacks. This allows them to point to malicious DVNs and/or change a configuration at a whim if a governance or internal security process is not set up to prevent them from doing so.</p><ul><li>Yes, developers can deploy or do malicious things on LayerZero. This is a byproduct of permissionless building and a tradeoff that’s well worth it. Ethereum, the internet, cash, etc., are all permissionless systems that allow people to do any number of things (both good and bad). To argue against this is to insult any developer’s intellect or free will. The argument that “devs can rug” is true for all applications built on permissionless blockchains. That being said, it is noted that best practice for developers is to be clear about their Security Stack and how it can be changed. For DAOs, a Security Stack could be selected and hardcoded via DAO vote, it could be time-locked and changed monthly, or a delegate could be charged with setting the Security Stack best suited to the DAO (with a time delay and with veto power from a security council). Similar setups can be used for businesses building on LayerZero. However, enterprise clients will likely want to run their own DVNs, so it should not be as big of an issue in that vertical.</li></ul><p><strong>Diversity of DVNs:</strong> While the protocol is unopinionated, the DVNs verifying messages are not. Therefore, if there is a limited set of DVNs and applications choose to not run their own DVNs, then messages sent across the network might be censored in some way, similar to how some Ethereum validators do not include OFAC-sanctioned transactions.</p><ul><li>A wide, varied group of DVNs is the goal for LayerZero. This diversity has multiple layers. DVNs should give developers a range of verification methods when building omnichain applications: bridges, oracles, chains, attestation services, restaking mechanisms, etc. For LayerZero to be a healthy protocol, a diverse group of entities needs to run DVNs: from enterprise solutions that connect to private chains to degenerate solutions that pick up any transaction in DeFi. On top of verification and entity diversification, it would also be nice to have a distributed set of DVNs running out of different jurisdictions to further harden the verification layer of LayerZero in the case of state-level attacks. At V2 launch, 15+ DVNs are live, from enterprises like Google Cloud to crypto-native solutions like Polyhedra zklightclient. This number should scale as V2 gains traction. With 60 chains and millions of messages to verify, more groups should be incentivized to run a DVN.</li></ul><p><strong>DVNs and Good Faith Attestation</strong>: Similar to the above bullet, it must be noted that there is a trust assumption that DVNs will not collude.</p><ul><li>LayerZero assumes developers will choose a Security Stack that minimizes collusion risk. LayerZero simply creates a marketplace for these ideas to be pitted against each other in terms of cost and security tradeoff (and application demand) — with the ultimate security of being able to run your own. For example, DVNs can have slashing mechanics and/or staking if it wants to, but LayerZero will not enforce this.</li><li>Understanding why DVNs act in good faith can be broken into three arguments: 1) A good reputation is worth more than colluding to confirm a malicious transaction for enterprise DVNs. 2) Some DVNs already implement a transparent mechanism for incentivizing good behaviour (slashing, etc). 3) Fees make it worth running a DVN. On the reputation side, DVNs like Google Cloud, Animoca, Blockdaemon, and Gitcoin are likely too big, too ingrained in the broader crypto ecosystem and likely carry too much reputational risk to collude. On the transparency side, decentralized DVNs, like Axelar and CCIP, have their own validator sets that can be openly audited and checked — and also natively implement slashing to punish bad actors. On the fees side, with 50+ chains to service and historical message volume recently crossing 100,000,000, DVNs should be sufficiently incentivized to run just in terms of fees.</li><li>Overall, protocols should look to use DVNs that will not collude. For example, a DVN setup of Google Cloud and Axelar is a very hard Security Stack, as it includes verification from a centralized and a decentralized entity, minimizing collision risk (and more DVNs can be added to this setup later on). Developers need to be careful in selecting their Security Stack, as it is possible that DVNs will attempt to collude at some point in the protocol’s future. Any application should consider collusion risk and plan accordingly by running their own DVN, reaching out to DVN teams to perform due diligence, and/or choosing a DVN combination where it is impossible to collude.</li></ul><p><strong>Executor x Liveness:</strong> In theory, anybody may execute transactions in V2. Liveness should never be an issue, as an end-user or application can manually execute transactions on <a href="https://layerzeroscan.com/">LayerZero Scan</a> if the configured Executor goes offline. However, if, in practice, configured Executors go down frequently, there are short-term liveness concerns for applications building on LayerZero.</p><ul><li>As already mentioned, permissionless execution should alleviate liveness concerns in theory. However, in practice, running an Executor is challenging work. As stated in the <a href="https://twitter.com/LayerZero_Labs/status/1752014720058671459">V2 launch video</a>, running an automated executor requires billions of RPC calls per month and providing gas abstraction across 50+ chains, which in and of itself requires holding 50+ gas tokens and rebalancing those gas assets as needed. That said, an app can build and configure a smaller version of an Executor that runs across a limited chain pairing (e.g. Fantom &lt;&gt; Ethereum) — though even then, it is still complex to write due to re-orders, liveness, availability, resiliency against failures, race conditions, properly pricing gas cost, among other things. Overall, ensuring that multiple Executors are available is helpful for the protocol’s long-term liveness if an OApp’s selected Executor goes down. To that end, there are now <a href="https://docs.layerzero.network/v2/developers/evm/off-chain/build-executors#mock-executor">open-source implementations</a> of Executors available in our documentation.</li></ul><p><strong>Defaults: </strong>When developers begin experimenting with LayerZero, they can opt into LayerZero Labs’ default Security Stack or set their own Security Stack. The default Security Stack is set by and can be changed by LayerZero Labs at any time. Any application that abdicates its security choice to LayerZero Labs’ defaults, therefore, abdicates its security to a centralized third party. The current <a href="https://docs.layerzero.network/v2/developers/evm/configuration/default-config">default setting</a> is Google Cloud and LayerZero Labs.</p><ul><li>Defaults in and of themselves are not bad — it is very much like holding crypto on an exchange or custodian. This may be ideal for small applications or large enterprise solutions (as something like Coinbase is for new entrants and institutional holders of BTC). However, for crypto-native applications, opting into defaults is likely not ideal because if LayerZero Labs is hacked or turns malicious, then the default Security Stack could also be changed to be malicious. <strong>Defaults are intended for developers to test LayerZero. The end-game for most applications should be to configure their own Security Stack and not to use defaults in the first place</strong> — and/or for reputable orgs (like foundations or large applications) to publish their own ‘default’ settings for applications to use.</li></ul><p><strong>Endpoint Deployments:</strong> LayerZero Labs is the only entity that can deploy canonical, socially accepted endpoints. If LayerZero Labs were to shut down, that would stop the current iteration of LayerZero from extending to new chains.</p><ul><li>Since Endpoints are immutable, any Endpoint or MessageLib deployed will stay deployed and be active in perpetuity. Applications can build on this infrastructure forever, even if no new Endpoints are created. However, to expand to new networks in lieu of LayerZero Labs shutting down, some sort of workaround would need to be put into place. To clarify, other teams can deploy Endpoints — but they are not considered socially canonical, as they do not connect to other LayerZero Endpoints (breaking the whole interoperability thesis). However, if LayerZero Labs were to go down, another team could deploy Endpoints and attempt to garner social consensus for their own mesh. One solution often floated around would be allowing permissionless endpoint deployment. This, however, is a design decision that increases complexity, introduces spam risk, and will likely be very troublesome for DAO governance (in selecting canonical bridges for assets).</li></ul><h3>LayerZero and the Market</h3><p>The cross-chain world is filled with bridges, liquidity networks, and token standards. Here’s a brief outline of where LayerZero fits.</p><h4><strong>Security Stacks: Bridges as DVNs</strong></h4><p>Much like Bitcoin is built on the idea of self-custody (ownership over the security of your commodity), LayerZero is built on the idea of Security Stacks (ownership over the security of your application).</p><p>In V2, any entity that can verify a message — be it a native bridge, third-party bridge, validator set, oracle, multisig, light client, zk prover, etc. — may be used as a DVN by an application building on top of LayerZero.</p><p>This section of the article will make the case that many of the most popular third-party bridges are actually just <strong><em>decentralized verifier networks</em></strong> (DVNs) that can be used as <a href="https://docs.layerzero.network/v2/home/modular-security/security-stack-dvns#dvn-adapters">Adapter</a> <a href="https://docs.layerzero.network/v2/home/modular-security/security-stack-dvns#dvn-adapters">DVNs</a> built by application owners to verify messages in V2.</p><p>In other words, many existing bridges will likely end up as DVNs competing to verify messages inside LayerZero.</p><p>For more context, third-party bridges are cross-chain protocols competing against each other to build the most robust, industry-trusted mechanism for verifying messages between certain subsets of chains. Examples of third-party bridges include CelerIM, Axelar, deBridge, CCIP, Synapse, Wormhole, Router, IBC, etc. The designs for third-party bridges often revolve around shared security and can be generally bucketed into three categories. Middlechains like Axelar and Synapse validate messages as a hub and emit messages to spokes. There are guardian third-party bridges that attest to the validity of messages through reputational multi-sigs — like Wormhole and Avalanche Bridge. You can think of them as oracles or attestation services that sign off on cross-chain messages for a fee. The last type of third-party bridge is of a somewhat more vague bucket, which we call trust-minimized systems. These involve either zk proofs, light clients, or optimistic proofs, which can be boiled down to only having to trust one thing: math, chain consensus, and a single honest watcher, respectively.</p><p>No third-party bridge has quite cracked the code on the “best” form of security. Middlechains compete to build the most unhackable hubs. Guardians compete to bring in the most reputable players in crypto to attest to cross-chain transactions. Trust-minimized systems use the finest tools that math, blockchains, and game theory have to offer.</p><p>While each of these entities can send/receive arbitrary data across chains, that is not what third-party bridges are exceptional at. These third-party bridges are actually excellent at verification — at proving that this message happened over here and can be sent over there.</p><p>With the new V2 design, these third-party bridges, as DVNs, get to focus on what they do best — signing off on valid cross-chain transactions — and applications select the third-party bridges they want based on use-case preferences. This design should be a win-win, as third-party bridge designers no longer need to worry about execution and/or transmission of cross-chain messaging, and applications are no longer locked into a single verification method when building something that exists on multiple blockchains.</p><p>By allowing third-party bridges to do what they do best (verify things), LayerZero can focus on the main idea: unified semantics — allowing developers to compose contracts in the same way, regardless of chain. Every data packet sent and every endpoint interacted with on the LayerZero protocol is identical. LayerZero is built to allow developers to pick and choose from every type of verification method available on the market. It is a permissionless, censorship-resistant, and immutable structure that can be filled with any type (or combination) of verification method. This is powerful, as it future-proofs LayerZero against advancements in verification techniques while allowing for universal blockchain composability through a standardized messaging design.</p><h4><strong>One Messaging Layer, Many Liquidity Networks</strong></h4><p><em>Any type of liquidity network can be recreated on LayerZero.</em></p><p>Another bucket of “bridges” are cross-chain protocols that allow for the transfer of tokens across chains. These are called liquidity networks. Examples include Across, Hop, Portal, Connext, Stargate, Allbridge, DLN, UniswapX, Hyphen, Catalyst, and cBridge, among others. Most liquidity networks are designed around a basic intent structure: a user has asset X on Chain A and wants asset X on Chain B. A liquidity network matches an intent with a solving mechanism that is either onchain (liquidity pools/wrapped assets), offchain (often dubbed relayers), or a mixture of both. These solving mechanisms essentially take the user’s token on Chain A and unlock/fill the same amount of tokens on Chain B. They charge a small fee for this service. The competition amongst liquidity networks can be found in bridge price execution, fees, number of tokens offered to users, and transfer time.</p><p>Something interesting about liquidity networks is that the verification method used underneath the liquidity network is somewhat arbitrary. Like how multiple AMMs can be built on top of Ethereum, many liquidity networks can technically be built on the same verification network. UniswapX <a href="https://uniswap.org/whitepaper-uniswapx.pdf">emphasizes</a> this point — it spent an entire whitepaper only talking about the liquidity aspects of the protocol (fillers, dutch-auction, optimistic execution, etc.) while not naming the underlying verification network it might use! All the whitepaper says is that a “settlement oracle” is necessary, which could be “a canonical bridge… light client bridge, or a third party bridge.” Anything passing a message between chains can be the settlement oracle here! This character trait is not unique to UniswapX. Other liquidity network designs like DLN and cBridge and Wormhole’s Portal and Catalyst could likely use other third-party bridges (aka DVNs) for settlement.</p><p>What these liquidity networks need is not necessarily a single third-party bridge — rather, they need a verification method they can trust depending on the chain pairing and use case. With V2, LayerZero could theoretically support each liquidity network for messaging (settlement) while allowing them to choose unique verification methods (Security Stacks).</p><p>LayerZero V2 offers a single messaging framework for many different types of liquidity networks to be built using different Security Stack configurations. This broadens the scope of what can be made and should result in fun experimentation. For example, a cross-chain AMM might select a Security Stack based on trade size, with the idea that different trade volumes will be settled by different Security Stacks (essentially bridge aggregation through Security Stack optionality).</p><h4><strong>Universal Contract Standards</strong></h4><p>The modular blockchain thesis, the L2 scaling thesis, the omnichain thesis — all of these ideas require universal token and contract standards so that the world of 1000s of chains can operate without fragmentation and context switching depending on each new chain/asset/VM pairing. Omnichain Fungible Tokens (OFTs) and Omnichain Applications (OApps) aim to be those standards — extending developer capability without compromising security.</p><ul><li>OFTs extend traditional token standards like ERC-20, empowering developers to create tokens that operate seamlessly across multiple blockchains. This universality eliminates silos, enabling tokens to move between chains. The potential adoption of OFTs as a standard means that developers no longer need to deploy separate, chain-specific tokens, which can divide liquidity and community while introducing different trust assumptions. Instead, OFTs offer a unified token presence across all LayerZero-supported blockchains, ensuring that token ecosystems remain cohesive and robust, regardless of the chain. OFTs work across multiple token standards (ERC20 being the most popular), add no fees outside those tacked on by applications, and allow for a universal supply to be tracked at all times (transparency). As with applications, OFT token issuers maintain complete control over their contracts and Security Stacks. (<em>Note: ONFTs will also be live on V2 but are now in beta due to contracts being audited. The same logic for OFTs can be easily extended to ONFTs.</em>)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SA3wW94xzFEKqNsy" /><figcaption>Bonus photo showcasing an OFT tx.</figcaption></figure><ul><li>The omnichain applications (OApp) contract standard provides a universal, blockchain-agnostic developer interface. With OApps, developers can now build an application once and deploy it across any number of chains without rewriting code. This cuts development time and opens up the entire blockchain ecosystem to their application rather than a fraction of it. This also allows developers to access the combined users and liquidity of any LayerZero-supported blockchain. In addition, multiple OApps can be combined, creating genuine full-stack, cross-chain financial applications (imagine a DeFi app that allows for borrowing on any chain, swapping on any chain, etc.).</li></ul><p>With V2, LayerZero should have a good chance of becoming the single framework for cross-chain tokens and governance, as it offers a universal messaging solution with a modular verification layer.</p><p>In other words, a token or governance setup can use ANY type of verification method — or combination of verification methods — to move data to a destination chain using V2, with the only trust assumption being the sanctity of LayerZero Endpoints (a trust assumption that cannot be escaped with any other solution, either).</p><p>Overall, the case can — and maybe should — be made that OFTs and OApps become the de facto contract standards for all tokens and contracts moving forward for teams building on LayerZero-supported chains. Here are a few reasons why:</p><ol><li><strong>Interoperability by Default: </strong>OFTs and OApps are built for a multi-chain world. They inherently adopt cross-chain communication, making them future-proof as crypto continues to evolve into an industry with 1000s of chains. Adopting these standards allows projects to plan for years instead of months.</li><li><strong>Modular Security:</strong> Both OFTs and OApps benefit from LayerZero’s modular security framework, which enables application-specific customization of security parameters. This means developers are not forced into a one-size-fits-all security model but can tailor security to the unique needs of their application or token, enhancing both flexibility and resilience.</li><li><strong>Simplicity and User Experience</strong>: For users, the complexity of blockchain interactions fades into the background with OFTs and OApps. They offer a simplified, consistent user experience that abstracts away the technicalities of chain-specific operations.</li><li><strong>Universal Composability</strong>: There are many cross-chain contract standards on the market. Solidifying OFT and OApp as industry norms increases composability while decreasing fragmentation — without locking protocols into a single security strategy.</li></ol><h3>Conclusion</h3><p>LayerZero’s architecture — modular at the verification level while static at the transport layer — strikes a crucial balance of current performance and future-proofed design.</p><p>The technology is here for us to build an open and just digital economy for all people, for all time. As an industry, crypto has to work together to bring that vision to fruition. By nature of that shared goal, our technologies must be permissionless.</p><p>For that vision to succeed, this philosophy must be upheld at every level of the stack. LayerZero defends these values down to the packet level.</p><p>When features are mutable, values can always be changed. Promises aren’t permanent. Decisions aren’t durable. Upgrades are risks. Eventually, systems are corrupted.</p><p>Permanence and provability must be hard coded.</p><p>That’s why LayerZero is here. That’s why LayerZero exists.</p><p><strong>LayerZero is built so you don’t have to trust others. It’s built so you can trust yourself.</strong></p><blockquote>Thanks for reading. A big shout out to Tapioca Matt, Paladin Marco, LI.FI Arjun, Sandman, Catalyst Jim, and BlockWorks Ren for feedback on this piece. Handshakes all around to the LZ team as well, especially BP, MP, and RMT.</blockquote><h3>Contact</h3><p>For more information on V2, check out this <a href="https://twitter.com/LayerZero_Labs/status/1752014702287437907">thread</a>, read this <a href="https://www.notboring.co/p/layerzero-the-language-of-the-omnnichain">article</a>, or check out our <a href="https://docs.layerzero.network/">docs</a>.</p><p>To learn more about LayerZero in general, check out the <a href="https://layerzero.network/">website</a>. For additional information, the LayerZero Labs team is available to answer general questions on <a href="https://discord-layerzero.netlify.app/discord">Discord</a> and <a href="https://t.me/joinchat/VcqxYkStIDsyN2Rh">Telegram</a>. You can also follow LayerZero Labs on <a href="https://twitter.com/LayerZero_Labs">X</a> to receive the most up-to-date information.</p><p>For specific inquiries:</p><ul><li>Infrastructure providers looking to run an Executor DVN should fill out this <a href="https://layerzeronetwork.typeform.com/to/U9hMgxf1">form</a>!</li><li>Developers looking to build an OApp or OFT should fill out this <a href="https://layerzeronetwork.typeform.com/to/uCwPqTp9#name=xxxxx">form</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=869f93e09850" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/layerzero-v2-deep-dive-869f93e09850">LayerZero V2 Deep Dive</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LayerZero V2 is Live]]></title>
            <link>https://medium.com/layerzero-official/layerzero-v2-is-live-740290f2dbe6?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/740290f2dbe6</guid>
            <category><![CDATA[interoperability]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[LayerZero]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 13:07:50 GMT</pubDate>
            <atom:updated>2024-01-29T13:28:49.283Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zxbuPnuI3Kpr41GPZvHPmA.png" /></figure><p>LayerZero V2 is live, bringing permissionless, censorship-resistant, and immutable interoperability to 20+ chains.</p><h3>V2 Highlights</h3><ul><li><strong>Universal Messaging</strong>: Any type of <a href="https://docs.layerzero.network/contracts/layerzero-messages">message</a> can be sent and composed between chains, including arbitrary data, external function calls, and/or tokens.</li><li><strong>Modular Security</strong>: Developers may choose from their preferred combination of 20+ <a href="https://docs.layerzero.network/contracts/dvn-addresses">Decentralized Verifier Networks</a> (DVNs) when selecting a <a href="https://docs.layerzero.network/contracts/configure-dvns">Security Stack</a> to verify cross-chain messages.</li><li><strong>Permissionless Execution</strong>: Anybody may run an <a href="https://docs.layerzero.network/explore/executors">Executor</a> in V2. Information on how to run your own Executor is available <a href="https://docs.layerzero.network/contracts/develop-executor">here</a>.</li><li><strong>Unified Semantics</strong>: OApp and OFT <a href="http://k/contracts/overview">contracts</a> enable developers to build applications and tokens that work the same across every blockchain V2 has an endpoint on.</li><li><strong>V1 Compatibility: </strong>​​Migration options exist for V1 applications. If already deployed on V1, applications can utilize the new security and execution model via ULN 301. More information can be found <a href="https://docs.layerzero.network/explore/migration">here</a>.</li></ul><p>For more detailed information on V2, check out the <a href="https://twitter.com/LayerZero_Labs/status/1735317463032893946">V2 launch video</a>, the <a href="https://layerzero.network/publications/LayerZero_Whitepaper_V2.0.pdf">V2 Whitepaper</a>, and <a href="https://docs.layerzero.network/">V2 Developer Documentation</a>. Audit reports for V2 are also available <a href="https://github.com/LayerZero-Labs/LayerZero-v2/tree/main/audit">here</a>.</p><h3>About LayerZero</h3><p>LayerZero is a permissionless, censorship-resistant, and immutable protocol that connects blockchains. Using LayerZero, developers can send arbitrary messages across chains while preserving full control over their application’s security. LayerZero enables developers to create, configure, and compose unified applications, tokens, and data primitives across many chains.</p><p>Anything that can be programmed as a smart contract on a single chain can be natively programmed across multiple chains via LayerZero. Since its inception, Over <a href="https://layerzeroscan.com/">40,000 OApp contracts</a> have been deployed on LayerZero, 100s of teams use LayerZero’s OFT Standard to power tokens, and dozens of teams have built full-scale applications as groupings of OApps. These products include lending markets, stablecoins, bridges, enterprise projects, NFTs, meme tokens, and identity solutions.</p><h3>Contact</h3><p>To learn more about LayerZero, check out the <a href="https://layerzero.network/">website</a>. For additional information, the LayerZero Labs team is available to answer general questions on <a href="https://discord-layerzero.netlify.app/discord">Discord</a> and <a href="https://t.me/joinchat/VcqxYkStIDsyN2Rh">Telegram</a>. You can also follow LayerZero Labs on <a href="https://twitter.com/LayerZero_Labs">X</a> to receive the most up-to-date information.</p><p>For specific inquiries:</p><ul><li>Infrastructure providers looking to run an Executor DVN should fill out this <a href="https://layerzeronetwork.typeform.com/to/U9hMgxf1">form</a>!</li><li>Developers looking to build an OApp or OFT should fill out this <a href="https://layerzeronetwork.typeform.com/to/uCwPqTp9#name=xxxxx">form</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=740290f2dbe6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/layerzero-v2-is-live-740290f2dbe6">LayerZero V2 is Live</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing LayerZero V2]]></title>
            <link>https://medium.com/layerzero-official/introducing-layerzero-v2-076a9b3cb029?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/076a9b3cb029</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[LayerZero]]></dc:creator>
            <pubDate>Thu, 14 Dec 2023 15:20:45 GMT</pubDate>
            <atom:updated>2023-12-14T15:20:45.371Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/679/0*nSEojpy03DInV0A2" /></figure><h3><strong>LayerZero</strong></h3><p>LayerZero enables developers to create and configure unified applications, tokens, and data primitives — regardless of chain — through the transmission of arbitrary messages.</p><p>Like TCP/IP standardized internet development, LayerZero’s goal is to standardize application development across all chains. This concept of unified cross-chain development is encapsulated in the word “omnichain” and is how LayerZero envisions the future of crypto.</p><p>LayerZero is a protocol designed to connect blockchains while upholding the following fundamental principles:</p><ul><li>Permissionless: Anyone may run the infrastructure necessary to verify and execute messages. Anyone can build on and interact with LayerZero.</li><li>Censorship resistant: No individual message can be executed until all previous messages have been verified, meaning no individual message can ever be censored on any pathway.</li><li>Immutable: Endpoints on each chain exist in the form of smart contracts. New verification libraries can be added as append-only updates. These are non-upgradeable and will exist in perpetuity.</li></ul><h3><strong>LayerZero V2 TL;DR</strong></h3><p>Today marks the deployment of LayerZero V2 on 40+ testnets and the introduction of the <a href="https://layerzero.network/publications/LayerZero_Whitepaper_V2.0.pdf">V2 technical whitepaper</a>. V2 creates an omnichain network of blockchains for developers to build universal applications.</p><p>The upgrade introduces key features:</p><ul><li><strong>Decentralized Verification Networks (DVNs):</strong> Replacing the V1 Oracle, this permissionless role empowers any entity capable of verifying cross-chain data packets to join LayerZero as a DVN.</li><li><strong>Adapters:</strong> Axelar and CCIP DVN adapters will be available today on testnet and when mainnet launches. Other adapters planned for 2024 will allow developers to integrate any type of native bridge, third-party bridge, middle chain, oracle, or other verification methods into LayerZero, thereby avoiding vendor lock-in at the security level.</li><li><strong>X of Y of N:</strong> This is a modular approach to verification empowering applications to neither overpay nor underpay for security depending on use case. X of Y of N allows applications to combine DVNs however they like. For instance, a “1 of 3 of 5” combination of DVNs would include one required DVN and two arbitrary DVNs out of a total of five that must verify a message for cross-chain execution.</li><li><strong>Permissionless Execution:</strong> Replacing the Relayer and separating execution from verification, LayerZero V2 introduces Executors — a permissionless role that facilitates smooth execution on the destination chain, simplifies gas payments, and offers customizable gas settings.</li><li><strong>Security Stack:</strong> Each Omnichain Application (OApp) must configure a Security Stack comprising DVNs, Executor(s), chain confirmations, MessageLibraries, and chain pathways for omnichain messaging. This setup grants applications complete control over security. With V2, are opt-in, with the recommendation being that OApp developers set their own Security Stack.</li><li><strong>Increased Throughput:</strong> By providing the option for lazy nonce enforcement or strict nonce enforcement, V2 allows developers to choose whether they want to execute transactions in order or out of order. With out-of-order transaction execution, LayerZero’s throughput matches that of the destination chain while maintaining censorship resistance.</li><li><strong>Enhanced Programmability:</strong> V2’s improved protocol contract interfaces, path-specific libraries, new design patterns, and horizontal composability redefine application interaction, fostering flexibility and uninterrupted cross-chain transactions.</li><li><strong>Unified Semantics:</strong> V2 enables developers to build applications that work the same across every blockchain LayerZero has an endpoint on — including non-EVM chains.</li><li><strong>V1 Compatability: </strong>​​For teams building on V1, the V2 launch will allow for both forward and backward compatibility.</li></ul><h4><strong>All told, with the launch of V2, LayerZero aims to embed itself as a crypto primitive on par with Bitcoin and Ethereum. Bitcoin as the protocol for crypto money, Ethereum as the protocol for crypto finance, and LayerZero as the protocol for crypto internet.</strong></h4><p>With DVNs and Adapters, LayerZero V2 sits at the transport layer of the blockchain economy, whereas other “cross-chain” solutions battle for the right to verify messages. LayerZero can now act as a quasi-aggregator of verification methods. Any type of verification method — be it bridge, oracle, attestation service, or a blockchain itself — can be plugged into V2 as a DVN. Application owners building on LayerZero may configure DVNs based on their project’s use case.</p><p>For example, application developers can opt to verify messages through shared-security adapters like Axelar and CCIP or go with enterprise signers like Blockdaemon and Google Cloud — or a combination of all four. And, most importantly, this decision is not set in stone, as the Security Stack configuration can be changed by the application owner (or a delegate) if a DAO or business decides to do so. Independent DVNs confirmed at testnet launch will include entities run by Blockdaemon, Google Cloud, Animoca, Delegate, Gitcoin, Nethermind, P2P, StableLab, Switchboard, Tapioca, LayerZero Labs, and Polyhedra. The number of DVNs should increase as mainnet approaches — with 50+ chains to support, there is a need for many DVNs.</p><p>Permissionless execution and lazy nonce-enforcement improve both liveness and throughput properties. Liveness concerns are minimized since anyone (third-party executor, application, end-user) may now execute transactions. Throughput is maximized to align with that of the destination chain. In addition, the protocol itself is easier to build on, with new design patterns available for developers to send, receive, and compose messages across chains. Furthermore, the core protocol is built in such a way that extending to new chains — even non-EVM chains — can be done without changing how messages are sent.</p><h3><strong>V2 Launch Details</strong></h3><p>LayerZero V2 endpoint contracts are deployed on 40+ testnets starting today, with the goal being to give developers time to experiment with new Security Stacks and Endpoints before going live on mainnet.</p><ul><li>You can read the whitepaper <a href="https://layerzero.network/publications/LayerZero_Whitepaper_V2.0.pdf">here</a>.</li><li>You can read the developer docs <a href="https://docs.layerzero.network">here</a>.</li></ul><p>Mainnet launch is targeted for January 2024. The launch will include V2 endpoints on each chain that V1 supports. All Omnichain contract standards — OApp, OFT, and ONFT — will be available by mainnet launch. On testnet, only OApp and OFT will be available.</p><p>Mainnet launch will include support from the following infrastructure entities:</p><ul><li>DVNs: Instructions on how to run a DVN are available in the LayerZero <a href="https://docs.layerzero.network/contracts/develop-dvn">documentation</a>. Read more <a href="https://docs.layerzero.network/explore/decentralized-verifier-networks">here</a>. In addition, Animoca, Blockdaemon, Delegate, Gitcoin, Nethermind, Obol, P2P, StableLab, Switchboard, Tapioca, Polyhedra, LayerZero Labs, and Google Cloud will run DVNs on testnet. Adapters for Axelar and CCIP will also be available for testnet and mainnet launch, with more coming soon.</li><li>Executors: Instructions on how to spin up an Executor are available in LayerZero <a href="https://docs.layerzero.network/contracts/develop-executor">documentation</a>. Read more <a href="https://docs.layerzero.network/explore/executors">here</a>. In addition, LayerZero Labs will offer third-party execution options for dApps. <a href="https://layerzeroscan.com/">LayerZero Scan</a> will also have a tab available for end-user execution.</li></ul><p><strong>Reach Out With Any Questions</strong></p><p>For teams building on V1, the V2 launch will allow for both forward and backward compatibility. You can find migration information specifically inside our <a href="https://docs.layerzero.network">documentation</a>. It is important to note that V1 is still in production and will continue to be in production in perpetuity. As of now, V2 brings no breaking changes to V1 (this might change when V2 endpoints extend to new chains).</p><p>As mainnet launch approaches, we will continue to update our documentation with any changes and publish educational resources to make the transition from V1 to V2 as smooth as possible.</p><p>If you are planning on building on V2, have questions about migrating from V1, or something in between, please join our <a href="https://layerzero.network/discord">Discord</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=076a9b3cb029" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/introducing-layerzero-v2-076a9b3cb029">Introducing LayerZero V2</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to ColorTrace]]></title>
            <link>https://medium.com/layerzero-official/introduction-to-colortrace-0538272e393d?source=rss----86a3a7f3e9a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/0538272e393d</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[layer-zero]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[algorithms]]></category>
            <dc:creator><![CDATA[Bryan Pellegrino]]></dc:creator>
            <pubDate>Tue, 14 Nov 2023 10:01:11 GMT</pubDate>
            <atom:updated>2023-11-14T10:01:11.339Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n69rpU-GKiy25cnXqo_PoA.png" /></figure><p><a href="https://layerzero.network/publications/ColorTrace.pdf">ColorTrace</a> is a practical solution to the colored coin problem. Colored coins set out to create distinction among a group of fungible assets by coloring individual coins, which can be thought of as the ‘marking’ of a bill of fiat currency. Each bill is equally spendable and yet you know unique characteristics about each based on their markings, such as who held them before, where they were printed, etc.</p><p>The original Colored Coin algorithm aimed to solve this through a lossless metadata layer on top of the bitcoin ledger, but more generally in EVM would be akin to keeping an infinitely large ledger list of every address of every possible colorer and their current balance per wallet. This is intractable in both storage and compute and, as such, has never been viable to implement- leaving there few good avenues for accurate onchain value attribution.</p><p>Introducing ColorTrace.</p><p>For a practical example of ColorTrace, we’ll walk through the implementation used by USDV in their recent launch of the stablecoin.</p><p>The problem to be solved was that much of the value of existing stablecoins were driven by the market participants themselves. Groups like Uniswap, Curve, Coinbase, and Binance have moved trillions of dollars of stablecoins and given immense utility to their underlying ecosystems and yet only one of those has ever been directly rewarded for it. Circle entered into a custom agreement with Coinbase to share the yield of USDC based on Coinbase’s contributions to the success of USDC. For this Coinbase currently earns almost $1B per year. The simple solution would be to create similar deals with all other major parties, but this is where the tricky part comes in. Imagine a world today where $24B of USDC sits in circulation, with the majority in EOAs. How much yield goes to each party? For the balance sitting in Uniswap, Curve, Coinbase, and Binance it’s easy to see how much each party has contributed, but for the more than $10B+ sitting in user wallets and EOAs it’s hard to know how much each group has contributed to that.</p><p>This is where onchain value attribution comes in. ColorTrace unlocks the ability for each entity to receive pro-rata attribution for the value they have created for the underlying ecosystem. In the case of USDV, this means that each token an entity has minted into circulation will be marked with their color and be attributed to them until it is redeemed for the underlying asset — a true onchain meritocracy.</p><p>Extending beyond USDV, ColorTrace can be used for things like onchain ref links, affiliate programs, and really any use-case that allows for protocols to reward participants fairly for any value accretive action.</p><p>For a deeper look at the design of ColorTrace and the other algorithms created along the way, read <a href="https://medium.com/layerzero-official/solving-fungible-token-coloring-a-nerds-version-ba74ea3a96ba">Solving Fungible Token Coloring — A Nerds Version</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0538272e393d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/layerzero-official/introduction-to-colortrace-0538272e393d">Introduction to ColorTrace</a> was originally published in <a href="https://medium.com/layerzero-official">LayerZero Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>