<?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[Stories by Katherine on Medium]]></title>
        <description><![CDATA[Stories by Katherine on Medium]]></description>
        <link>https://medium.com/@katherinebw?source=rss-f71de34470d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*4AxX6nGUlRx2BmAC</url>
            <title>Stories by Katherine on Medium</title>
            <link>https://medium.com/@katherinebw?source=rss-f71de34470d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:06:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katherinebw/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cross-Chain Connected Contracts with Hyperlane]]></title>
            <link>https://medium.com/moonbeam-network/cross-chain-connected-contracts-with-hyperlane-bc588ff2dcee?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc588ff2dcee</guid>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[xcm]]></category>
            <category><![CDATA[connected-contracts]]></category>
            <category><![CDATA[hyperlane]]></category>
            <category><![CDATA[moonbeams]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Mon, 28 Nov 2022 04:07:36 GMT</pubDate>
            <atom:updated>2023-01-10T21:25:29.436Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPUiHVbUmzLTl4SrRsc27A.png" /></figure><p><a href="https://moonbeam.network/blog/cross-chain-smart-contracts/">Cross-chain communication</a> lives at the heart of Moonbeam, which is why Hyperlane, another cross-chain protocol, has deployed on Moonbeam. Similar to previously introduced protocols <a href="https://moonbeam.network/blog/connected-contracts-axelar/">Axelar</a> and <a href="https://moonbeam.network/blog/connected-contracts-layerzero/">LayerZero</a>, Hyperlane allows developers to write smart contracts that can communicate across blockchains, which lets developers build cross-chain connected applications on Moonbeam that can tap into functionality from Polkadot, Ethereum, Avalanche, and beyond.</p><p>Multichain dApps are currently unified interfaces for protocols duplicated across multiple EVMs. Protocols will be able to connect their contracts cross-chain using Hyperlane’s general message passing to become multichain aware, allowing for advanced interoperability and functionality between what would otherwise be isolated ecosystems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QhfXtyaeb7bdNU7c1gmLoQ.png" /></figure><p>To demonstrate the power of <a href="https://moonbeam.network/builders/connected-contracts/">connected contracts</a>, walk through this demo that sends and stores a string from one TestNet EVM to another. The demo requires a MetaMask account with the Moonbase Alpha network added, which can be accomplished by visiting the <a href="https://docs.moonbeam.network/builders/get-started/networks/moonbase/#connect-metamask">Moonbeam docs site</a>.</p><h3>Intro to Hyperlane Contracts</h3><p><a href="https://www.hyperlane.xyz/">Hyperlane</a> is a delegated proof of stake chain protocol that validates and secures cross-chain communication via configurable consensus methods. Every validator in Hyperlane’s network will validate for every chain that Hyperlane is connected to. Hyperlane’s protocol includes verifiable fraud proofs that can be calculated by its network of <a href="https://docs.hyperlane.xyz/hyperlane-docs/protocol/agents/processor">Watchtowers</a> to prove if a cross-chain message provided by a validator is valid or not. These proofs will adapt based on which<a href="https://docs.hyperlane.xyz/hyperlane-docs/protocol/security/sovereign-consensus"> consensus method</a> (proof-of-stake, multisig, etc) a dApp desires to use, though most dApps will use proof-of-stake by default.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoWUA6RMsMK8W8WgqBZAKQ.png" /></figure><p>Image from <a href="https://www.hyperlane.xyz/">Hyperlane</a></p><p>Cross-chain messages are routed through Hyperlane’s Outbox and Inbox smart contracts. Inboxes are the smart contract that receives and processes messages. Each Hyperlane-connected chain has multiple Inboxes deployed, since each Inbox only connects to one other chain. The Outbox is a smart contract through which messages can be sent to other chains. Each chain has only one Outbox deployed on it. To help manage the Inbox and Outbox smart contracts, Hyperlane has a contract that is currently named the <a href="https://docs.hyperlane.xyz/hyperlane-docs/developers/building-applications/writing-contracts/abacusconnectionmanager"><em>AbacusConnectionManager</em></a> (Hyperlane used to be named Abacus). To help manage gas payments on the destination chain, Hyperlane has another contract named the <a href="https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/solidity/contracts/InterchainGasPaymaster.sol"><em>InterchainGasPaymaster.</em></a></p><p>You as a developer will deploy a smart contract that interacts with all of these contracts, though most of that smart contract code will be packaged into a parent smart contract for you to use without needing to look at the implementation details.</p><h3>Connected SimpleGeneralMessage Contract</h3><p>Hyperlane currently recommends using its <a href="https://docs.hyperlane.xyz/hyperlane-docs/developers/quickstarts">Quickstart guides</a> to get a feel for their protocol, which are great resources to understand how cross-chain messages are sent and received. This guide, which was developed in part using <a href="https://github.com/hyperlane-xyz/hyperlane-app-template">Hyperlane’s template project</a>, will help with understanding how cross-connected contracts are deployed and written.</p><p>Instead of setting up an entire Git repo, this guide will use a popular tool, Remix, to deploy and interact with contracts. To understand what you’re doing, take a look at the contract that you’ll deploy, which has been made available in a <a href="https://gist.github.com/jboetticher/f85dd837ca4a4845357a375f2495fa91">Github gist</a>, or can be accessed with this <a href="https://remix.ethereum.org/#gist=f85dd837ca4a4845357a375f2495fa91&amp;optimize=false&amp;runs=200&amp;evmVersion=null&amp;version=soljson-v0.8.7+commit.e28d00a7.js">Remix link</a>.</p><p>The contract’s <a href="https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/solidity/contracts/Router.sol">parent is Router</a>, which was imported from a <a href="https://www.npmjs.com/package/@hyperlane-xyz/app">Hyperlane package.</a> This parent contract abstracts away the difficulties of interacting with the <em>Inbox</em> and <em>Outbox</em> contracts, making it easier to write a connected contract. For the sake of simplicity, this post will not go in depth into the <em>Router</em> contract, but there are two points that are important for understanding the deployment steps.</p><p>First, note that there is a <em>_handle</em> function for smart contract developers to override. When an <em>Inbox</em> contract receives a message that is directed to a smart contract, it will call an external function called <em>handle</em>. The <em>handle</em> function will call <em>_handle</em> after a few checks, so the <em>_handle</em> function is effectively where the smart contract will receive and react to a cross-chain message.</p><p>Second, understand that there is a router enrollment system that acts as a whitelist for each contract. A Hyperlane connected contract cannot send a message to another that doesn’t enroll them (if the destination implements the <em>Router</em> contract). The <em>Router</em> contract will have many external functions that will have the <em>onlyRemoteRouter</em> modifier applied to them, which invokes the aforementioned whitelist system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8MW90f7CjvaGLUqYHPD4w.png" /></figure><p>When deploying, you will have to interact with the router enrollment system so that the connected contracts know which contract to send a message to.</p><p>But before you deploy, first review the <em>sendMessage</em> function in the <em>SimpleGeneralMessage</em> smart contract. If you’ve looked at our previous blog posts that introduced <a href="https://moonbeam.network/blog/connected-contracts-axelar/">Axelar</a> and <a href="https://moonbeam.network/blog/connected-contracts-layerzero/">LayerZero</a>, you’d correctly guess that this function similarly sends a message across chains. If you haven’t, well, now you know. Hyperlane’s Router contract provides perhaps the most abstracted version available, requiring only a domain (Hyperlane’s version of a chain ID) for the destination chain and a payload to begin a cross-chain message.</p><p>The first line packs the message sender and the string message into a bytes object, since that is the format that most cross-chain general message systems use to send and receive data. The second will dispatch the message to the local chain’s Outbox contract and pay for the message’s destination chain execution with the <em>InterchainGasPaymaster.</em></p><p>Note that the message is payable. Since this invocation of the <em>_dispatchWithGas</em> function includes <em>msg.value</em> as its third parameter, the entirety of the transaction’s value will be sent as gas to pay for the execution on the destination chain. The reason why there needs to be a second gas payment is that the gas paid in the execution of the transaction is only for the origin chain, and additional value must be sent to pay for the destination chain’s execution to complete a cross-chain message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pBS1I7RwYl1_Actcz39H6A.png" /></figure><p>Now look at how the connected contract receives a message. When an <em>Inbox</em> contract receives a message that’s directed towards a connected contract, it will call that contract’s external <em>handle</em> function and pass in relevant data. <em>The Router</em> function that your connected contract inherits from includes this handle function. Along with additional behind-the-scenes logic, it calls the internal and overridable _handle function as seen below, which allows developers to customize their smart contract’s logic when receiving a message.</p><p>In this case, the first thing that the <em>_handle</em> function does is decode the message that was packed by the remote contract’s <em>sendMessage</em> function. Then, on the second line, it stores the resulting message to be read in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uSPw5kPSoaQy9sv5-ZtD7g.png" /></figure><p>The code was relatively simple, so now you will deploy the contract! Doing is the best way to learn, so try to follow along with the deployment and message passing yourself on Moonbase Alpha.</p><h4>Deploying with Remix on Moonbase Alpha</h4><p>The easiest way to deploy the single demo contract is <a href="https://docs.moonbeam.network/builders/build/eth-api/dev-env/remix/">through Remix</a>. DEV is required to deploy on Moonbase Alpha, which is available from <a href="https://apps.moonbeam.network/moonbase-alpha/faucet/">the faucet</a> if you don’t have any already.</p><p>To deploy the script, first copy and paste <a href="https://gist.github.com/jboetticher/f85dd837ca4a4845357a375f2495fa91">the contract</a> into Remix or open it up directly from this <a href="https://remix.ethereum.org/#gist=f85dd837ca4a4845357a375f2495fa91&amp;optimize=false&amp;runs=200&amp;evmVersion=null&amp;version=soljson-v0.8.7+commit.e28d00a7.js">Remix gist link</a>. Then compile in the <strong>Solidity Compiler tab</strong>. Ensure that your MetaMask is connected to the Moonbase Alpha network. Then, in the <strong>Deploy &amp; Run Transactions</strong> tab of Remix, set the environment to the <strong>Injected Web3</strong>. This will use MetaMask as the Web3 provider.</p><p>To deploy on each chain, you will need the local instances’ addresses of two previously mentioned contracts: AbacusConnectionManager and InterchainGasPaymaster. Additionally, you will need the Hyperlane domain for a future step. All of this data has been provided for a select few TestNets in the table below. You can find other networks’ endpoints on <a href="https://docs.hyperlane.xyz/hyperlane-docs/developers/addresses#interchaingaspaymaster-1">Hyperlane’s documentation site</a>.</p><p>Once the contract has been deployed on Moonbase Alpha, make sure to copy down its address and repeat the process with one of any of the other <a href="https://docs.hyperlane.xyz/hyperlane-docs/developers/addresses#testnet2">EVM TestNets</a> that are connected to Hyperlane so it can send a message across chains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HgK-WUy0W1q9F4SMFYLpCA.png" /></figure><h4>Enrolling Remote Routers</h4><p>As previously mentioned, there is a whitelisting security system that comes with the <em>Router</em> parent smart contract. If you followed along with the <a href="https://moonbeam.network/blog/connected-contracts-layerzero/">LayerZero blog post</a>, you’ll note that they had a similar system when setting trusted remote addresses.</p><p>The Router contract currently allows only one smart contract per chain as an enrolled remote router, since it assumes that there is a single deployment on each chain that ought to communicate with each other. This isn’t a network-wide limitation though: you could write your own custom Router smart contract.</p><p>To enroll a connected Router contract, the following function must be called. Only the contract owner, in this instance the deployer, can set trusted remote addresses. The<em> _domain</em> parameter is the Hyperlane domain identifier for the chain that the contract should receive messages from, some of which were listed in the table above (the rest are on <a href="https://docs.hyperlane.xyz/hyperlane-docs/developers/domains">Hyperlane’s documentation site)</a>. The _router parameter is the connected contract address that messages should be received from that exists on the same chain as the domain identifier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f5IXXjc-rCW4fhDcWbTNiQ.png" /></figure><p>You might notice that the <em>_router</em> parameter is a <em>bytes32</em> instead of an address. This is so that future non-EVM chains can be supported. You will need to pad an additional 24 zeros to the address when providing input in Remix. For example, if my connected contract’s address was 0xaf108eF646c8214c9DD9C13CBC5fadf964Bbe293, I would input the following into Remix:</p><p>0x000000000000000000000000af108ef646c8214c9dd9c13cbc5fadf964bbe293</p><p>Now go ahead and use Remix to ensure that your two connected contracts trust each other. You will have to do this on both contracts that you have deployed. To switch between contracts on different chains, connect to the destination network through MetaMask. Make sure that you are in the <strong>Injected Provider</strong> environment and that the contract is still <strong><em>SimpleGeneralMessage</em></strong>. Then take the address of the destination contract, and paste it into the <strong>At Address</strong> input.</p><p>To add trusted remote addresses, find the <em>enrollRemoteRouter</em> function within the <em>SimpleGeneralMessage</em> contract and open it.</p><p>When you are on Moonbase Alpha, set the <strong>_domain</strong> as the Hyperlane domain identifier of the other EVM TestNet that you chose (found in <a href="https://docs.hyperlane.xyz/hyperlane-docs/developers/domains">their documentation</a> or the table above). Set the <strong>_router</strong> as the properly formatted (padded with 24 zeros) address of the contract you deployed on the other EVM TestNet. Afterwards, transact and confirm in MetaMask.</p><p>When you are on the alternate EVM TestNet, set the<strong> _domain</strong> input as Moonbase Alpha’s Hyperlane domain identifier (0x6d6f2d61). Set the <strong>_router</strong> input as the properly formatted address of the contract you deployed on Moonbase Alpha. Finally, transact and confirm in MetaMask.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LwUdNldXGi6s3tBpSbTulA.png" /></figure><p>In this section, you should have sent two transactions on two chains to set trusted remote addresses in both contracts. Afterwards, you should be good to send transactions between the connected contracts.</p><h4>Sending a Cross-Chain Message from Moonbase with Hyperlane</h4><p>To send a cross-chain message with an automatic destination chain transaction, an additional gas payment must be sent with the Hyperlane message to offset the destination chain’s gas cost. This additional gas payment comes in the form of the native currency (GLMR, ETH, etc) that you include in the transaction, set as the value of the message.</p><p>Hyperlane has a <a href="https://docs.hyperlane.xyz/hyperlane-docs/developers/building-applications/nodejs-sdk/gas#estimating-interchain-gas-payment-using-the-sdk">helpful SDK</a> to help estimate the cross-chain transaction gas fee, but for this blog post it is out of scope. For simplicity, it’s best to send a large amount, such as 300000000 Gwei of the native currency, with the cross-chain message. Note that you should not do this in production, and that this gas overestimation is just for TestNet demonstration purposes. As of writing, Hyperlane’s gas refund feature is still in development, and any extra gas will be kept by the relayer.</p><p>Now use the Remix interface. This example is going to send a cross-chain message to the Avalanche Fuji TestNet, but you can substitute the gas value and chain name for whichever EVM you desire. Check the following things:</p><ul><li>The environment is <strong>Injected Provider — Web3</strong> on network 1287 (Moonbase Alpha)</li><li>You have substantial funds in your wallet from <a href="https://apps.moonbeam.network/moonbase-alpha/faucet/">the faucet</a> to cover both the transaction cost and the DEV included for destination chain gas</li><li>You have the gas fee as 300000000 Gwei in the previous step placed in the <strong>value</strong> input</li><li>Put a short message of your choice in the <strong>message</strong> input of the sendMessage call (in this case “hello from moonbase alpha”)</li><li>Put the destination chain’s Hyperlane domain identifier in the _<strong><em>destinationDomain</em></strong> input of the <em>sendMessage</em> call</li></ul><p>Once this is all done, transact the execution and confirm it in MetaMask.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*QKpT5f2kufENApabkya-4A.png" /></figure><h4>Tracking Cross-Chain Messages</h4><p>After sending your transaction, you should be able to go into the <a href="https://moonbase.moonscan.io/">Moonbase Alpha block explorer</a> to take a look at the transaction using its transaction hash. If everything went well, it should be confirmed, and you’ll be able to see traces of the input of your transaction at the very bottom when viewing it as UTF-8.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GXVW2ztyhLqBzklYN30l9g.png" /></figure><p>In a typical transaction, the status and data of the transaction would be available on a single page on a single explorer. But, since this is cross-chain messaging, there are really two EVM transactions happening on two chains.</p><p>If everything goes smoothly, the transaction will be approved and you will be able to see the lastMessage updated in the origin chain from the successful cross-chain transaction! If it doesn’t automatically update, don’t worry. It’ll take a few seconds for it to properly go through.</p><p>If you want to see the message stored in the contract, you can do so through Remix. First, connect to the destination network through MetaMask. Make sure that you are in the <strong>Injected Provider</strong> environment and that the contract is still <strong><em>SimpleGeneralMessage</em>.</strong> Then take the address of the destination contract, and paste it into the <strong>At Address</strong> input. Press it, and you should be able to use the outcome contract to view the last message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rat_LlGVw5FZCRUBNavneQ.png" /></figure><p>If you don’t see the result of the message, Hyperlane <a href="https://explorer.hyperlane.xyz/">has an explorer</a> to track transactions, which you can use to track the status of the cross-chain message with the transaction hash of the first origin chain message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WCcejiE7X7naJZT8iOqpmw.png" /></figure><h4>Learn More About Connected Contracts</h4><p>Moonbeam’s vision for an interoperable hub of networks doesn’t stop here. Learn more about on the Hyperlane <a href="https://www.hyperlane.xyz/">website</a>, including how to send cross-chain messages in the <a href="https://docs.hyperlane.xyz/hyperlane-docs/introduction/readme">Hyperlane docs.</a> Read how <a href="https://moonbeam.network/builders/connected-contracts/">connected contracts</a> have positioned Moonbeam as the leader in blockchain interoperability.</p><p>If you are interested in <a href="https://moonbeam.network/">Moonbeam</a> and want to learn more, <a href="https://moonbeam.network/newsletter/">subscribe to the newsletter</a> and follow us on socials (links in the page header).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc588ff2dcee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/cross-chain-connected-contracts-with-hyperlane-bc588ff2dcee">Cross-Chain Connected Contracts with Hyperlane</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cross-Chain Connected Contracts with LayerZero]]></title>
            <link>https://medium.com/moonbeam-network/cross-chain-connected-contracts-with-layerzero-5cd25753840d?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cd25753840d</guid>
            <category><![CDATA[moonbeams]]></category>
            <category><![CDATA[connected-contracts]]></category>
            <category><![CDATA[layer-zero]]></category>
            <category><![CDATA[xc-20]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 19:56:30 GMT</pubDate>
            <atom:updated>2023-01-10T21:10:41.672Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tXdChA76dXGe1TnUOxKlrQ.png" /></figure><p>Connected contracts allow smart contracts to communicate with each other across chains, opening the possibility for multichain-aware dApps. Moonbeam’s first integration for <a href="https://moonbeam.network/builders/connected-contracts/">connected contracts</a> was <a href="https://moonbeam.network/blog/connected-contracts-axelar/">Axelar</a>, and in this blog post you will be introduced to another popular cross-chain protocol.</p><p>LayerZero is designed to be a lightweight interoperability protocol for cross-chain message passing. Benefits of LayerZero’s connected contract design include nonce-ordered messages and configurable trustlessness. Using LayerZero’s connected contracts solution, developers can build dApps that can tap into functionality from Polkadot, Ethereum, Avalanche, Swimmer, and beyond.</p><p>Multichain dApps are currently unified interfaces for protocols duplicated across multiple EVMs. Protocols will be able to connect their contracts cross-chain using LayerZero’s message passing to become multichain-aware, allowing for advanced interoperability and functionality between what would otherwise be isolated ecosystems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zgqfebWLvW7XS2S2diJ1Q.png" /></figure><p>To demonstrate the power of connected contracts, this demo will send and store a string from one TestNet EVM to another. The demo requires a MetaMask account with the Moonbase Alpha network added, which can be accomplished by visiting the Moonbeam <a href="https://docs.moonbeam.network/builders/get-started/networks/moonbase/#connect-metamask">docs site.</a></p><h3>Intro to LayerZero</h3><p>LayerZero is a trust-configurable protocol that provides secure cross-chain communication. Ultra-light nodes (ULN) in the form of smart contracts provide chains with the block headers of other bridged chains, but only on-demand for efficiency purposes. The LayerZero endpoint, which is a smart contract that houses the ULN, communicates with an oracle and a relayer.</p><p>The Oracle component provides and receives block headers. Applications can select from a marketplace of oracles, including Chainlink, and design the oracle component to require agreement from multiple entities. Block headers are published to destination chains, which allow for the on-chain verification of messages. The Relayer receives and provides proofs of cross-chain messages, which can be verified by block headers, allowing for messages to be completed on destination chains. Relayers can be maintained by anyone. In practice, however, LayerZero manages a relayer service that applications can leverage today. Over the next few months, an open source implementation of the relayer will create a marketplace of relayers for applications to select from and design further decentralized relayer systems similar to that of the Oracle component. The safety of the system relies on the separation between the oracle and relayer systems, and thus the trustlessness of the system is inherited from how much trust is required from the relayer and oracle actors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pk-cXVeVbheYbZqmb7ib4A.png" /></figure><p>This simple smart contract example will only be concerned with one smart contract, <em>NonblockingLzApp</em>. This smart contract will interact with the LayerZero endpoint to receive and send messages, and also stops failed transactions from blocking future messages from being received.</p><h3>Connected SimpleGeneralMessage Contract</h3><p>Now try it out in the most basic way possible. To understand what you’re doing, take a look at the contract that you’ll deploy, which has been made available in a <a href="https://gist.github.com/jboetticher/54b79e3a5b95605c298edaf2f23614cd">GitHub gist.</a></p><p>The contract’s <a href="https://github.com/LayerZero-Labs/solidity-examples/blob/main/contracts/lzApp/NonblockingLzApp.sol">parent is <em>NonblockingLzApp</em></a>, which was imported from a LayerZero GitHub repository. This parent contract abstracts away the technicalities of working with LayerZero’s endpoint smart contract so that receiving cross-chain messages is very easy.</p><p>Notice that <em>NonblockingLzApp</em> inherits from <em>LzApp</em>. To understand the difference between these two contracts, first know that if any connected contract receives a message from LayerZero, and when receiving that message, an uncaught exception occurs, no other messages can be received from LayerZero. In such an instance, the message that causes the exception is blocking other messages from being received, and will not stop blocking until the message stops causing an exception. Failed messages are blocked when inheriting from <em>LzApp</em>, but by using <em>NonblockingLzApp</em>, all exception causing messages are elegantly caught automatically.</p><p>With a brief look at how the <em>NonblockingLzApp</em> contract receives messages below, it’s clear that the _ <em>blockingLzReceive</em> function (called by <em>blockingLzReceive</em>) from the <em>LzApp</em> parent contract is overridden. This is the function that gets called when the connected contract receives a cross-chain message. This implementation has a line of code that calls the function <em>nonblockingLzReceive</em>, and checks for a success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8bXMMXeIgAcwb2YnQYqaSw.png" /></figure><p>Review the implementation of the <em>nonblockingLzReceive</em> function. All it does is ensure that the contract is calling itself (hence the previous function), and then calls a wrapper function that the developer can override. The only thing this chain of functions ( <em>blockingLzReceive</em>, <em>_blockingLzReceive</em>, <em>nonblockingLzReceive</em>) does is catch every exception and forward the call to <em>_nonblockingLzReceive</em> so that the developer can write custom logic when they receive a message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9D3VzfXjB9uXs2XIj3LN7g.png" /></figure><p>Next, look at how the <em>SimpleGeneralMessage</em> contract implements the <em>_nonblockingLzReceive</em> function. All it does is take the payload and write it into a mapping, so that it can be read later!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPAqVne27CTWzQYFrQUEOA.png" /></figure><p>What about sending the message? Before going into how to send a message, think again about the process of sending a message. The user will send a transaction to <em>SimpleGeneralMessage</em> on the origin chain, which will then be picked up by LayerZero’s oracle and relayer, and finally a second transaction on the destination chain will be sent by a LayerZero relayer.</p><p>Now back to the code. This also only needs two lines. In the first, the contract encodes the message into a bytes format so that it can be sent across chains. In the second, the message is sent across chains to the contract it’s connected to. The parameters are mostly self explanatory, and the ones that aren’t are irrelevant for this contract’s purposes. The main point is that the destination chain ID is set to a function input, the payload is set as the message, the refund address is set as the message sender, and the destination chain’s gas payment (<em>_nativeFee)</em> is the value of the message.</p><p>The reason there needs to be a gas payment paid through the<em> _lzSend</em> function is that there are two transactions: one on the origin chain and one on the destination chain. The transaction on the origin chain is paid like you normally would pay for a transaction: through the transaction fee inherit to a blockchain transaction. The second transaction is paid by sending additional native currency (value) through the LayerZero protocol, which will make up for the gas paid by a LayerZero relayer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HY80Y1pcHK0lp9GLX_SGpw.png" /></figure><p>Doing is the best way to learn, so try to follow along with the deployment and message passing yourself on Moonbase Alpha.</p><h4>Deploying with Remix on Moonbase Alpha</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7bpBvTjCorZvQnDwDMBM1A.png" /></figure><p>The easiest way to deploy the single demo contract is <a href="https://docs.moonbeam.network/builders/build/eth-api/dev-env/remix/">through Remix</a>. DEV is required to deploy on Moonbase Alpha, which is available from <a href="https://apps.moonbeam.network/moonbase-alpha/faucet/">the faucet</a> if you don’t have any already.</p><p>To deploy the contract, first copy and paste <a href="https://gist.github.com/jboetticher/54b79e3a5b95605c298edaf2f23614cd">the contract</a> into Remix, or access it through <a href="https://remix.ethereum.org/#gist=54b79e3a5b95605c298edaf2f23614cd&amp;optimize=false&amp;runs=200&amp;evmVersion=null&amp;version=soljson-v0.8.7+commit.e28d00a7.js">this Remix link.</a> Then compile in the Solidity Compiler tab. Ensure that your MetaMask is connected to the Moonbase Alpha network. Then, in the Deploy &amp; Run Transactions tab of Remix, set the environment to Injected Web3. This will use MetaMask as the Web3 provider.</p><p>For the contract to interact with LayerZero’s core functionality, it’s going to need to use the LayerZero endpoint contract. Moonbase Alpha’s endpoint is 0xb23b28012ee92E8dE39DEb57Af31722223034747, and you can find the other networks’ endpoints on <a href="https://layerzero.gitbook.io/docs/technical-reference/testnet/testnet-addresses">LayerZero’s documentation site</a>. Use this contract address in the constructor when deploying the contract to Moonbase Alpha.</p><p>Once the contract has been deployed on Moonbase Alpha make sure to copy down its address and repeat the process with any of the other <a href="https://layerzero.gitbook.io/docs/technical-reference/testnet/testnet-addresses">EVM TestNets</a> that are connected to LayerZero so it can send a message across chains.</p><h4>Adding Trusted Sources</h4><p>Since the smart contract at hand inherits from the parent LzApp smart contract, there is a trusted contract security system that comes with it. In order for the smart contract to call <em>_nonblockingReceive</em> when receiving a message, the message must come from a trusted source.</p><p>To add a contract as a trusted remote, the <em>setTrustedRemote</em> function must be called. Only the contract owner, by default the deployer, can set trusted remote addresses. The <em>_srcChainId</em> is the LayerZero chain ID of the source chain, which can be found on their documentation site and in the table above. The _path is the address to trust in bytes format.</p><p>LzApp stores a single trusted source from each chain in the trustedRemoteLookup map. The way it is stored is more complex than simply an address, however. The format requires two addresses packed together into bytes format: the first being the message source and the last being the message destination. This might seem like a strange way of doing it, but it makes the implementation in LzApp easier when checking for unauthorized messages.</p><p>For example, if you wanted to send a message from a contract <em>0xAAAAAAAAAAAAAAAAAAAA</em> on a chain with lzID 100 to a contract <em>0xBBBBBBBBBBBBBBBBBBBB</em> on a chain with lzID 101, you would format the trusted remote call on the latter chain:</p><p><em>setTrustedRemote(101, 0xBBBBBBBBBBBBBBBBBBBBAAAAAAAAAAAAAAAAAAAA)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SBhSeUVG59AjzcCAlExgFA.png" /></figure><p>There is an easier way to do this, however. LayerZero has provided a <em>setTrustedRemoteAddress</em> function in their implementation that helps with the formatting of the message. All that needs to be inputted is the LayerZero chain ID (_remoteChainId) and the address you want the contract to trust on the destination/remote chain (<em>_remoteAddress</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UkLGI201pETVi__YyyXPFg.png" /></figure><p>Now use Remix to ensure that both of your contracts trust each other. You will have to do this on both contracts that you have deployed. To switch between contracts on different chains, connect to your desired network through MetaMask. Make sure that you are in the <strong>Injected Provider</strong> environment and that the contract is still “ <em>SimpleGeneralMessage</em>”. Then take the address of the destination contract, and paste it into the <strong>At Address</strong> input.</p><p>To add trusted remote addresses, find the <em>setTrustedRemoteAddress</em> function within the <em>SimpleGeneralMessage</em> contract and open it.</p><p>When you are on Moonbase Alpha, set the <strong>_remoteChainId </strong>as the LayerZero chain ID of the other EVM TestNet that you chose (the LayerZero chain ID can be found <a href="https://layerzero.gitbook.io/docs/technical-reference/testnet/testnet-addresses">in their documentation</a> or in the table above). Set the <strong>_remoteAddress</strong> as the address of the contract you deployed on the other EVM TestNet. Afterwards, transact and confirm in MetaMask.</p><p>When you are on the alternate EVM TestNet, set <em>the </em><strong>_remoteChainId</strong> as Moonbase Alpha’s LayerZero chain ID (10126). Set the <strong>_remoteAddress</strong> as the address of the contract you deployed on Moonbase Alpha. Finally, transact and confirm in MetaMask.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a3_rZ1YnHneh-j8fwWayqg.png" /></figure><p>In this section you should have sent two transactions on two chains to set trusted remote addresses in both contracts. Afterwards, you should be good to send transactions between the connected contracts.</p><h4>Sending a Cross Chain Message from Moonbase with LayerZero</h4><p>To send a cross-chain message with an automatic destination chain transaction, an additional gas payment must be sent with the LayerZero endpoint message to offset the destination chain’s gas cost. This additional gas payment comes in the form of the native currency (GLMR, ETH, etc) that you include in the transaction, set as the value of the message.</p><p>For this post, the way to estimate the cross-chain transaction gas fee is out of scope. For simplicity on a TestNet, it’s best to send a large amount, such as 500000000 Gwei of the native currency, with the cross chain message. If there is an amount left over, it may be refunded if deemed inexpensive enough to do so.</p><p>Now you can use the Remix interface. This example is going to send a cross-chain message to the Fantom TestNet, but you can substitute the gas value and chain name for whichever EVM you desire. Check the following things:</p><ul><li>The environment is <strong>Injected Provider — Web3</strong> on network 1287 (Moonbase Alpha)You have substantial funds in your wallet from the faucet to cover both the transaction cost and the DEV included for destination chain gas</li><li>You have the gas fee as 500000000 Gwei in the previous step placed in the <strong>value</strong> input</li><li>Put a short message of your choice in the <strong>message</strong> input of the <em>sendMessage</em> call (in this case “gm”)</li><li>Put the destination chain’s layer zero ID in the <strong>destChainId</strong> input of the <em>sendMessage</em> call. Since you’re sending the transaction on TestNets, the ID should be above 10000</li></ul><p>Once this is all done, transact the execution and confirm it in MetaMask.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*748dBRvzArV3Y3MikbOxVA.png" /></figure><h4>Tracking Cross Chain Messages</h4><p>After sending your transaction, you should be able to go into the <a href="https://moonbase.moonscan.io/">Moonbase Alpha block explorer</a> to take a look at the transaction using its transaction hash. If everything went well, it should be confirmed, and you’ll be able to see traces of the input of your transaction at the very bottom when viewing it as UTF-8.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ezYZCQUP7zu2g0SFrFCwfA.png" /></figure><p>In a typical transaction, the status and data of the transaction would be visible on a single page on a single explorer. But, since this is cross-chain messaging, there are really two EVM transactions happening on two chains.</p><p>If everything goes smoothly, the transaction will be approved and you will be able to see the <em>lastMessage</em> updated in the origin chain from the successful cross-chain transaction! If it doesn’t automatically update, don’t worry. On average, it takes about 30 seconds to a minute for a transaction to go through.</p><p>If you want to see the message stored in the contract, you can do so through Remix. First, connect to the destination network through MetaMask. Make sure that you are in the <strong>Injected Provider</strong> environment and that the contract selected is still “ <em>SimpleGeneralMessage</em>”. Then take the address of the destination contract, and paste it into the <strong>At Address</strong> input. Press it, and you should be able to use the outcome contract to view the last message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*erfEQTYF5kpPtyhFHEvs3g.png" /></figure><p>If you don’t see the result of the message, LayerZero <a href="https://testnet.layerzeroscan.com/">has an explorer</a> to track transactions, which you can use to track the status of the cross-chain message with the transaction hash of the first origin chain message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vAHm8F87P5IF65mLLX26Ig.png" /></figure><h4>Learn More About Connected Contracts</h4><p>Moonbeam’s vision for an interoperable hub of networks doesn’t stop here. Learn more on the LayerZero <a href="https://layerzero.network/">website</a>, including how to send cross-chain messages in the <a href="https://layerzero.gitbook.io/docs/">LayerZero docs</a>. Read how <a href="https://moonbeam.network/builders/connected-contracts/">connected contracts</a> have positioned Moonbeam as the leader in blockchain interoperability.</p><p>If you are interested in <a href="https://moonbeam.network/">Moonbeam</a> and want to learn more, <a href="https://moonbeam.network/newsletter/">subscribe to the newsletter</a> and follow us on socials (links in the page header).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cd25753840d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/cross-chain-connected-contracts-with-layerzero-5cd25753840d">Cross-Chain Connected Contracts with LayerZero</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moonriver Provides EVM Smart Contract Platform for Robonomics Applications with XCM Integration]]></title>
            <link>https://medium.com/moonbeam-network/moonriver-provides-evm-smart-contract-platform-for-robonomics-applications-with-xcm-integration-66873bf9333a?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/66873bf9333a</guid>
            <category><![CDATA[connected-contracts]]></category>
            <category><![CDATA[evm]]></category>
            <category><![CDATA[moon-river]]></category>
            <category><![CDATA[xcm]]></category>
            <category><![CDATA[robonomics]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 15:08:15 GMT</pubDate>
            <atom:updated>2023-01-10T20:16:09.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WGtD-zn8KVK-YL9f.png" /></figure><p>Singapore — November 22, 2022 — <a href="https://moonbeam.network/">Moonbeam</a>, the top destination for multi-chain applications on Polkadot, has announced an <a href="https://moonbeam.network/blog/xcm-on-polkadot/">XCM connection</a> between Moonriver and Robonomics by opening an HRMP channel to bring the Robonomics native token, XRT, to Moonriver. The XRT token can now be used as <a href="https://moonbeam.network/announcements/moonriver-adds-cross-chain-capabilities-and-xcksm/">xcXRT</a> across the Moonriver ecosystem.</p><p>Robonomics is an open-source platform for IoT applications. It supports Web3 technology that implements the exchange of information in atomic transactions between user applications, IoT services, and complex robotics. The Robonomics platform contains tools for developing IoT applications, both on the robotics and the user interface sides. The user and device communicate using IPFS, Ethereum, and Polkadot.</p><p>With this integration, the Robonomics team can explore bringing smart contracts into their parachain on Kusama. Developers can build atop Moonriver’s fully Ethereum-compatible smart contract platform to explore the integration of composable smart contracts into the real-world applicability that IoT devices have been created to provide. Taking on-chain data and being able to translate that into real-world events will open up a new class of development and use cases that blockchains can power.</p><p>In August, Moonbeam announced a live proof-of-concept of <a href="https://moonbeam.network/announcements/xcm-to-evm-functionality-moonbase-alpha/">XCM-to-EVM functionality</a> on Moonbase Alpha TestNet. This technology allows developers on remote chains to trigger function calls on the Moonriver/Moonbeam platform, allowing them to tap into the features of the developer-friendly EVM on their home chains. This functionality furthers Moonbeam’s interoperability mission by providing more potential use cases for chains connecting to Moonbeam as a “hub” for Polkadot and the parachains, and other ecosystems like Ethereum, Avalanche, Cosmos, and more.</p><p>If remote EVM calls through XCM are enabled on Moonbeam and Moonriver by a community vote, Robonomics’ IoT devices and applications will be able to remotely call smart contracts on Moonriver with the native security of the Kusama chain, through XCM. This opens up an entirely new realm of possibilities for IoT devices that work on Robonomics parachain, as they’ll be able to access the immutability and security of smart contracts.</p><p>Find out about <a href="https://moonbeam.network/builders/">building and development</a> on Moonriver and Moonbeam and <a href="https://moonbeam.network/newsletter/">sign up for the newsletter.</a></p><h3>About the Moonbeam Network</h3><p><a href="http://moonbeam.network/">Moonbeam</a> is a smart contract platform for building cross-chain connected applications that can access users, assets, and services on any chain. By uniting functionality from Ethereum, Cosmos, Polkadot, and more into a single platform, Moonbeam solves today’s fragmented user experience — unlocking true interoperability and paving the way for the next generation of applications. The Moonbeam platform uses integrated cross-chain messaging to allow developers to create smart contracts that access services across many remote blockchains. This approach, plus Moonbeam’s developer-friendly EVM platform, vast tool support, and modern Substrate architecture, creates the ideal development environment for building connected applications.</p><h3>About Robonomics</h3><p><a href="https://robonomics.network/">Robonomics</a> Network — a decentralized cloud for secure and reliable control of IoT applications. It incorporates decentralization, blockchain technologies and token-based economics for the protection of smart devices and their data. Robonomics is aimed at: 1) control of smart devices with security and global availability, 2) serverless IoT applications for users for their privacy, 3) performing technical and economic transactions between people and machines for service efficiency. Moreover, the Robonomics parachain has an IoT subscription function that allows users to send device transactions without fee, for a period of one month. This allows, in particular, to make the smart home completely sovereign of centralized service providers, while keeping the ability to securely and remotely access devices at home.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66873bf9333a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/moonriver-provides-evm-smart-contract-platform-for-robonomics-applications-with-xcm-integration-66873bf9333a">Moonriver Provides EVM Smart Contract Platform for Robonomics Applications with XCM Integration</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bifrost Polkadot Integrates with Moonbeam to Power GLMR Liquid Staking]]></title>
            <link>https://medium.com/moonbeam-network/bifrost-polkadot-integrates-with-moonbeam-to-power-glmr-liquid-staking-a6dd6b6b1195?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6dd6b6b1195</guid>
            <category><![CDATA[glmr]]></category>
            <category><![CDATA[bifrost]]></category>
            <category><![CDATA[moonbeams]]></category>
            <category><![CDATA[liquid-staking]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Thu, 17 Nov 2022 15:50:12 GMT</pubDate>
            <atom:updated>2023-01-10T20:13:29.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q3ebwmI-e3hbIjLP.png" /></figure><p>Singapore — November 17, 2022 — <a href="https://moonbeam.network/">Moonbeam</a>, the top destination for multi-chain applications on Polkadot, has announced an XCM connection between Moonbeam and <a href="https://bifrost.finance/">Bifrost</a> by the opening of HRMP channels bringing the Bifrost native token, BNC, to Moonbeam. Bifrost’s token can now be used as xcBNC, an <a href="https://moonbeam.network/announcements/moonriver-adds-cross-chain-capabilities-and-xcksm/">XC-20 representation of BNC</a>, across the Moonbeam ecosystem, and the GLMR token is now available on Bifrost.</p><p>Bifrost exists as a parachain on both Kusama and Polkadot as Bifrost Kusama and Bifrost Polkadot. Both parachains are DeFi protocols that provide staking derivatives and liquidity to bonding assets. Bifrost powers vTokens (Staking Derivatives Voucher Token), which allow users to exchange PoS tokens for vTokens and obtain liquidity and staking rewards through Bifrost protocol</p><p>The underlying technology that enables the XC-20 standard, XCM (Cross-Consensus Messaging) is uniquely made possible by the Polkadot architecture. XCM is a language that enables asset transfers from Bifrost, and other parachains to Moonbeam represented as standard ERC-20s.</p><p>This format provides flexible interoperability within the Polkadot ecosystem and beyond — a key building block of the cross-chain connected future. Moreover, XCM allows one parachain to perform remote calls on the other, a key element that will power the GLMR liquid staking solution that Bifrost provides through XCM. The<a href="https://moonbeam.network/announcements/xcm-sdk/"> recent activation of the XCM SDK</a> makes it easier than ever for developers to use these features in the design of cross-chain applications on Moonbeam.</p><p>Moonbeam continues to support the building of cross-chain applications that provide a better user experience and superior interoperability than historical multi-chain approaches. XCM and XC-20s are tools that support Moonbeam community goals by providing technology for accessing the functionality of remote blockchains.</p><h3>About the Moonbeam Network</h3><p><a href="http://moonbeam.network/">Moonbeam</a> is a smart contract platform for building cross-chain connected applications that can access users, assets, and services on any chain. By uniting functionality from Ethereum, Cosmos, Polkadot, and more into a single platform, Moonbeam solves today’s fragmented user experience — unlocking true interoperability and paving the way for the next generation of applications. The Moonbeam platform uses integrated cross-chain messaging to allow developers to create smart contracts that access services across many remote blockchains. This approach, plus Moonbeam’s developer-friendly EVM platform, vast tool support, and modern Substrate architecture, creates the ideal development environment for building connected applications.</p><h3>About Bifrost</h3><p>Bifrost is a web3 derivatives protocol that provides decentralized cross-chain liquidity for staked assets. By leveraging on the cross-consensus message (XCM), it can provide cross-chain liquid staking services for multiple chains.</p><p>Bifrost’s mission is to provide standardized cross-chain interest-bearing derivatives for Polkadot relay chains, parachains, and heterogeneous chains bridged with Polkadot. Furthermore, by aggregating over 80% of PoS consensus chains’ staking liquidity through cross-chain derivatives, our protocol lowers users’ staking threshold, increases multi-chain staking ratio, and improves the ecosystems application interest base by creating a three-way positive cycle for the StakeFi ecosystem by empowering users, multi-chains, and ecosystem applications.</p><p>Bifrost has raised over USD 2M from top-tier venture capital firms by the likes of NGC, SNZ, DFG, CMS and other institutions. In addition to being an early receiver of a Web3 Foundation Grant, Bifrost is also a member of the Substrate Builders Program and the Web3 Bootcamp.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6dd6b6b1195" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/bifrost-polkadot-integrates-with-moonbeam-to-power-glmr-liquid-staking-a6dd6b6b1195">Bifrost Polkadot Integrates with Moonbeam to Power GLMR Liquid Staking</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moonriver and Moonbeam Natively Supports Auto-Compounding of Staking Rewards]]></title>
            <link>https://medium.com/moonbeam-network/moonriver-and-moonbeam-natively-supports-auto-compounding-of-staking-rewards-a70a5dcd03d3?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a70a5dcd03d3</guid>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[moonbeams]]></category>
            <category><![CDATA[runtime-upgrade]]></category>
            <category><![CDATA[moon-river]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Thu, 03 Nov 2022 17:04:36 GMT</pubDate>
            <atom:updated>2023-01-10T19:47:03.103Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68-7Q9lMJs9IdamIZrBW6g.png" /></figure><p>Singapore — November 03, 2022 — <a href="http://moonbeam.network/">Moonbeam</a>, the top destination for multi-chain applications on Polkadot, has released runtime 1901 in Moonriver, and soon, Moonbeam, after the passing <a href="https://moonriver.polkassembly.network/referendum/116">referendum 116</a>. Runtime 1901 includes new features that allow users to auto-compound staking rewards earned on the Moonriver and Moonbeam staking DApps. This upgrade also activates randomness, a feature anticipated for gaming on Moonbeam, and identity verification. The latest technical components included in Runtime 1901 will positively impact application development with new use cases on the Moonriver and Moonbeam networks.</p><h3>Auto-Compounded Staking</h3><p><a href="https://moonbeam.foundation/glimmer-token/">GLMR</a> and <a href="https://moonbeam.foundation/moonriver-token/">MOVR</a> token holders support the maintenance of the Moonbeam and Moonriver networks, respectively, by locking their tokens to collators. When a user delegates tokens to a collator, the staking rewards earned on the Moonbeam and Moonriver Dapps are automatically deposited into the connected wallet. These tokens are available to be used however the token holder wishes. If the staker desired to add the rewarded tokens back into the delegation, the only option was to do so manually. Now there is an automatic option.</p><p>The implementation of runtime 1901 now allows <a href="https://apps.moonbeam.network/moonriver">Moonriver staking dapp</a> users to autostake their token rewards with one click. This feature will be added to Moonbeam in the next two weeks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xs-LuPvu_o1wOur1_tGdxA.png" /></figure><p>Users have always been free to delegate these funds, but it had to be done manually, and a transaction fee was deducted from the amount. In response to requests from the community, this upgrade means staking rewards can be natively staked automatically or auto-compounded, at the user’s discretion right in the Moonriver and Moonbeam Dapps.</p><p>Stakers can choose the percentage amount of the rewards they wish to be auto-compounded and the amount will automatically be added to the delegation. Add or change the auto-staking percentage at any time on a new or existing delegation. The default percentage is set to 100, and users can change this amount at any time with the simple sliding tool.</p><p>When an auto-compound is set, it will take effect after two rounds and continue until the user ends the auto-compounding by moving to a percentage of zero. This upgrade makes it easier to stake tokens and earn rewards on the network.</p><h3>Randomness Function</h3><p>The second upgrade in runtime 1901 is the much-anticipated <a href="https://docs.moonbeam.network/learn/features/randomness/">randomness function</a> which is used for a variety of blockchain applications to create unbiased, unpredictable, and unique outcomes. The activation of randomness on Moonriver/Moonbeam brings with it verifiable random functions (VRF) that can be verified on-chain. Developers on Moonriver and Moonbeam have access to two sources of randomness inputs which can be interacted with via the randomness precompile contract.</p><p>Developers can use the randomness precompile to create truly random functions that can be verified as such. This function has applications for all types of DApps being built, including gaming, and will bring new functionality to those building and deploying their projects on Moonbeam.</p><h3>On-Chain Identity Verifier</h3><p>Finally, the on-chain identity verifier is now activated on Moonriver and soon Moonbeam, allowing users who choose to identify themselves and verify their identity trustlessly. This update was <a href="https://moonbeam.network/announcements/xcm-to-evm-functionality-moonbase-alpha/">previously announced</a> on Moonbase Alpha and is now active on Moonriver, coming to Moonbeam soon. The process avoids legal KYC and entails a variety of checks to ensure the connection between an address and an identity. Public profiles can be added by showing a passport to a registrar, proving that you are connected to the address/handle, etc. Power to confirm identity on-chain relies on <a href="https://wiki.polkadot.network/docs/learn-identity#registrars">Polkadot pallet for identity</a>.</p><h3>About the Moonbeam Network</h3><p><a href="http://moonbeam.network/">Moonbeam</a> is a smart contract platform for building cross-chain connected applications that can access users, assets, and services on any chain. By uniting functionality from Ethereum, Cosmos, Polkadot and more into a single platform, Moonbeam solves today’s fragmented user experience — unlocking true interoperability and paving the way for the next generation of applications. The Moonbeam platform uses integrated cross-chain messaging to allow developers to create smart contracts that access services across many remote blockchains. This approach, plus Moonbeam’s developer-friendly EVM platform, vast tool support, and modern Substrate architecture, creates the ideal development environment for building connected applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a70a5dcd03d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/moonriver-and-moonbeam-natively-supports-auto-compounding-of-staking-rewards-a70a5dcd03d3">Moonriver and Moonbeam Natively Supports Auto-Compounding of Staking Rewards</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spotlight: Cross Chain NFTs and 1:1 NFT Art on Moonbeam]]></title>
            <link>https://medium.com/moonbeam-network/spotlight-cross-chain-nfts-and-1-1-nft-art-on-moonbeam-f8e541b69112?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8e541b69112</guid>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[art]]></category>
            <category><![CDATA[crosschain]]></category>
            <category><![CDATA[moonbeams]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Thu, 27 Oct 2022 17:39:16 GMT</pubDate>
            <atom:updated>2023-01-10T20:52:24.844Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mVwA8R4sBl3-5ZY4BcOZ3g.png" /></figure><p>The <a href="https://moonbeam.network/community/projects/">NFT scene on Moonbeam</a> has grown with the development of new blockchain technology. New use cases that include the freedom for users to access their NFTs across blockchains and the concept of one-of-one NFTs are making waves in the space. Moonbeam is actively improving <a href="https://moonbeam.network/blog/cross-chain-smart-contracts/">cross-chain</a> access to NFTs with connected contracts, which opens new opportunities for the use of NFTs on any blockchain.</p><p>The <a href="https://moonbeam.network/">Moonbeam network</a> is home to a diverse and active ecosystem that includes NFTs natively supported by the ERC-721 and ERC-1155 standards available for use in cross-chain connected smart contracts. This means Ethereum-compatible NFTs and other assets are visible and useable from one application without moving them across blockchains. This flexibility will impact NFT use in many aspects of gaming, metaverse, art collection, and more.</p><p>Moonbeam is Ethereum compatible and supports ERC-721 NFT bridging with Ethereum, but this may no longer be necessary as the next generation of user-friendly applications solve the problem of fragmented cross-chain functionality and user experience.</p><h3>NFTs on Moonbeam</h3><p>A variety of top-tier multi-chain <a href="https://moonbeam.network/networks/moonbeam/nfts/">NFT marketplaces deployed on Moonbeam</a> are already experimenting with the possibilities brought by recent innovations. Moonbeam’s marketplaces include <a href="https://moonbeam.network/community/projects/treasureland/">Treasureland</a>, <a href="https://moonbeam.network/community/projects/nftrade/">NFTrade</a>, <a href="https://tofunft.com/">Tofu NFT</a>, <a href="https://moonbeam.network/blog/native-project-spotlight-moonbeans-nft-marketplace-grows-on-moonriver/">Moonbeans</a>, <a href="https://moonbeam.network/community/projects/mintverse/">Mintverse</a>, and <a href="https://moonbeam.network/community/projects/raresama/">Raresama</a>.</p><p>As a smart contract platform for building cross-chain connected applications that can access users, assets, and services on any chain, Moonbeam is an ideal place for NFT marketplaces to reach their users on more than one blockchain.</p><p>“TofuNFT supports more than 30 chains, and Moonbeam is a very important one. The number of projects is large, the quality is high, and above all, we strongly feel through the Moonbeam project there is a lot of community building that is so important to establish NFT projects,” says Yuto Nagashima of TofuNFT. “We will continue to provide strong support for Moonbeam, as its growth will lead to the growth of NFT marketplaces such as tofuNFT.”</p><p>Treasureland is another multi-chain NFT marketplace that supports NFT creation, issuance, auction, and socialization, aiming to connect NFT creators, users, and consumers in a decentralized way. “Treasureland supports the Moonbeam network due to its strong compatibility and flexibility, which gives the NFT assets on Moonbeam long-term potential, even more so for the 1–1 NFTs,” a rep explains.</p><p>Projects building on Moonbeam have their sights set on the benefits of interoperability available through Moonbeam cross-chain smart contracts with integrated cross-chain messaging.</p><p>Harrison Seletsky, Head of Growth and Strategy at NFTrade, explains, “At NFTrade, we believe in a cross-chain and multi-chain future, which is exactly what Moonbeam is working to facilitate. In this regard, we are happy to work together with Moonbeam development teams and their community so that value accrual occurs on their chain and to their collections, which will be a focal point of success for the future.”</p><p>Moonbeam is uniting functionality from Ethereum, Cosmos, Polkadot, and more into a single platform, solving today’s fragmented user experience — unlocking true interoperability and paving the way for the next generation of applications. One key motivator for improving user experience is to support wider adoption, and the NFT space is a meaningful way to do that.</p><p>Lead Raresama, Momsama shares that “Raresama is a Marketplace with a focus on 1:1 art and is 100% community governed and curated; new tokens and collections on the Marketplace have to be voted in by the token holders. Verification (think blue checkmark) of members also goes through community voting and even new features, and the development direction of the platform is in the hands of the community and artists.”</p><p>Miami, CEO of Moonbeans, explains that the Moonbean’s marketplace’s aim is to provide a user experience that is familiar and friendly. “We want newcomers to the space to feel comfortable learning about NFTs and trading them. Ease of cross-chain transactions is key to the user experience. Therefore, [Moonbeans] has reached out to partners like Multichain to provide support to help develop the protocols to allow proper NFT bridging. Cross-chain NFTs are the way forward and providing an interaction layer to users to easily be able to transact and interact with these NFTs is key.”</p><p>Polkadot is inherently built with cross-chain interoperability in mind. So, according to Miami, “Picking Moonbeam was a no-brainer as the leading EVM chain on Polkadot. Over time [Moonbeans] will be rolling out support to all EVM parachains and external EVM chains as well”.</p><h3>The Value and Uses of NFTs</h3><p>NFTs are cryptographic assets that exist on the blockchain with unique identifiers that distinguish them from each other. Unlike cryptocurrencies which are fungible, NFTs are non-fungible which means one cannot be traded equivalently for another. NFTs are not interchangeable, which leads to a marketplace centered largely around collectibles.</p><p>NFTs come in the form of photography, music, digital art, collectibles, 1:1 art, tickets, memberships, gaming avatars, and domain names. NFTs can consist of generative art, original art, or a series of images like collectibles (i.e.trading cards). The creator of an NFT can choose how, where, and how many NFTs to mint, depending on their intended use case.</p><p>The value of an NFT comes from community demand and scarcity. Like fine art, “rarity” is what makes owning NFTs exciting. NFTs can offer other utility as well, including access to token-gated communities, metaverses, and gaming. NFTs can give access to voting, provide proof of ownership, and represent the authenticity of real-world assets. In some cases, NFTs can be used as collateral for borrowing.</p><p>New NFT use cases continue to arise as the possibilities of Web3 broaden. NFTs are being used to represent investment baskets tradable by investors and can aid in royalty distribution. NFTs can be fun to collect and trade and play with, but they also prevent fraud and support decentralized finance in staking.</p><p>The success of an NFT project hinges partly on the strength of the community surrounding it, making NFTs, especially 1:1 NFT artists, a bridge between traditional real-world art communities, and digital blockchain art. The nature of the online community is shifting to bring more users into Web3 as more people understand and appreciate the potential of NFTs.</p><h3>1:1 NFTs</h3><p>When minting an NFT, a creator can choose to issue a collection or one or more editions of the same piece of art. When there is one edition of a single work, this NFT is the only one available and referred to as a 1:1: NFT.</p><p>Unique NFTs often fetch higher market prices than collections because they are one-of-a-kind, which drives up demand. Another reason for interest in 1:1 NFTs is that they tend to come from artists that bring their own fans and community to the marketplace, increasing demand and interest, making obvious the need for a more familiar buying and trading experience. Additionally, one-of-a-kind perks may tip the scale even further as some 1:1 NFTs offer VIP access to events or also include a piece of real-world art.</p><p>Moonbeam provides infrastructure for the user-friendly development of fluid applications and projects in Web3 which extends to the NFT space. This 1:1 approach to NFTs is changing the space and has the potential to address problems surrounding royalties of art returning to the artist throughout the trading process, and access of fans to purchase the art.</p><p>On Moonbeam, the Moonbeans marketplace focuses on giving users the freedom to create as they want to make. They have been “working on the full non-beta product from the ground up using what worked from the beta platform to build an experience that is not only easy to use but also exciting to use.”</p><p>“To this end [Moonbeans has] designed creation features that allow a range of NFT types, one of these being 1 of 1 NFTs. These unique NFTs will benefit from all the current features in the beta plus a few extra features being cooked up. [Moonbeans’] goal is to support all creation so users can focus on their art, games, brand, or whatever else their vision is. We run the tech so they can run the experience,” says Miami.</p><h3>Artists on Moonbeam</h3><p>1:1 NFTs have low volume, but bring communities into Web3 as part of the “fan” journey. This experience is collaborative and bridges the gap between the world of art and the communities that support the arts. Angela Pencheva’s contact with Moonbeam to mint on Raresama and additionally list on Moonbeans and NFtrade is an example of this process in action.</p><p>Angela Pencheva is an artist, NFT creator, and designer working on her first personal one-of-one NFT project on Moonbeam. Based in Sofia, Bulgaria, Pancheva worked as a UI/UX designer when an offer to work on an NFT project came up, which resulted in two successful NFT projects featuring her drawings.</p><p>1:1 NFTs are a tool that real-world artists are beginning to use to move their communities into the Web3 space. In this regard, one-of-one NFTs may very well become a catalyst for wider adoption of blockchain technology as more users open crypto wallets and utilize crypto tokens for purchases.</p><p>“With an increased focus on utility in the world of NFTs — often considered a challenge by artists,” Momsama says “Raresama will offer NFTs on the platform long-term support and integration in its (future) metaverses. This way, Raresama delivers the utility and artists can focus on creating their art, unleashing their creativity, and telling their stories.”</p><p>Artist curious about the NFT space may look to collaborate with teams like the people that work on Moonbeam itself, or a marketplace like Raresama that have experience building online communities, minting NFTs, and using the tools common to these things (i.e. discord, telegram, etc) as they transition from Web2 to Web3.</p><p>Pencheva recognizes entering the NFT space as the best thing that has happened in her career so far, despite the challenge of learning the lingo, how to mint, the purpose of gas fees, using tokens, and how to set up a wallet. The biggest obstacle to entering the space was bridging the gap between the art world and the digital blockchain world as an artist.</p><p>This movement of real-world art and its fans into the digital space signals a shift in the way NFTs are being used, and how they may develop in the future. The focus becomes less on flipping static digital images and generative art and more on the quality of the images, and the authenticity of the artist.</p><p>Visit <a href="https://moonbeans.io/collections/astrocluster">Moonbeans</a>, <a href="https://raresama.com/collections/0xaccb8b73499ab0e76141684d144deec17c96e44c">Raresama</a>, or <a href="https://nftrade.com/collection/astro-cluster">NFTrade</a> for more about Pencheva’s Astro Cluster collection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-bOjzXnoCfr2JlEfu1WdQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VKyti5NCkvsgSJvzJo8Jrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-BsRVHWFJzTXaJ1bxjsnEQ.png" /></figure><h3>Building on Moonbeam</h3><p>Moonbeam was instrumental in aiding Pencheva’s transition to Web3. The team got her started once she did her own research and chose which layer 1 blockchain she wanted to build on. According to Pencheva, the unique connected contract strategy put her over the edge in her decision to choose Moonbeam.</p><p>“As an artist, I don’t want my NFTs to be confined to just a single L1 given how many chains are developing in the Web3 space, so with connected contracts, I’m able to de-risk that decision of where my NFTs will live and have utility on since by being on Moonbeam they’ll be able to interact with other chains as well,” Pencheva said.</p><p>The community aspect of the ecosystem and Dotsama in general also attracted Pencheva to Moonbeam. She explains that “everyone has been very open and supportive to help me out which is great for someone who is new to this space.”</p><p>Moonbeam continues to support the ecosystem with cross-chain connected contracts, and real-world applications of Web3 concepts like NFTS, decentralization, and community. Building user-friendly applications will continue to streamline interoperability between blockchains and bring about the mass adoption of blockchain technology including the art world via 1:1 NFTs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8e541b69112" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/spotlight-cross-chain-nfts-and-1-1-nft-art-on-moonbeam-f8e541b69112">Spotlight: Cross Chain NFTs and 1:1 NFT Art on Moonbeam</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the Moonbeam Community Forum]]></title>
            <link>https://medium.com/moonbeam-network/using-the-moonbeam-community-forum-c5593f2ea169?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5593f2ea169</guid>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[community-forum]]></category>
            <category><![CDATA[moonbeams]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Wed, 26 Oct 2022 20:04:46 GMT</pubDate>
            <atom:updated>2023-01-10T20:42:35.523Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ZdGHdRQ2kV0XzdHWsenBQ.png" /></figure><p>The Interim Treasury Program is a 6-month program that establishes a separate community Treasury Council to manage Treasury funds, a budget for Treasury spending, and a required discussion time to gather community feedback on possible future Treasury proposals.</p><p>When a community member has a new idea for a Treasury proposal, the first step they’ll need to take before submitting a formal on-chain proposal is to post their idea on the <a href="https://forum.moonbeam.foundation/login">Moonbeam Community Forum</a>. The proposer will collect feedback from community members and the Treasury Council for five days.</p><p>After five days of community engagement, the proposal can be submitted formally on-chain along with a proposal bond. The proposal bond on Moonbeam and Moonriver is 5% of the amount requested by the proposer, with a minimum amount and no upper limit. The minimum is 100 GLMR on Moonbeam and 1 MOVR on Moonriver, although these amounts may change in the future.</p><p>The proposal can then be converted to a Council motion or rejected by any member of the Treasury Council. If none of the Treasury Council members propose it as a motion, the bond stays locked and cannot be claimed back by the proposer.</p><p>Assuming the proposal was converted to a Council motion, the motion will then be subject to an on-chain vote. A majority of 3/5th of the Treasury Council is required to pass the motion. On the other hand, the threshold for rejecting a proposal is at least 1/2 of the Treasury Council. If the proposal passes, the funds are disbursed from the Treasury after the current spending period has passed and sent to the beneficiary address. If the proposal is rejected, the proposal bond is burned.</p><p>For more information on the Treasury proposal process, please visit the <a href="https://docs.moonbeam.network/learn/features/treasury/">Treasury page</a> of the Moonbeam documentation site.</p><p>The happy path for a Treasury proposal is depicted in the following diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uwHzw5m-_yJ0YghhKbSilA.png" /></figure><p>The Moonbeam Discussion Forum will be used throughout the entire submission process of Treasury proposals. As proposals progress through the phases, community members can track the status from within the forum to see if it’s being reviewed, voted on, passed, rejected, and more.</p><h3>Getting Started with the Discussion Forum</h3><p>To access the Moonbeam Community Forum, you must be a member of the <a href="https://discord.com/invite/PfpUATX">Moonbeam Discord</a> community. You can then sign up to get access to the forum using your Discord credentials.</p><p>To sign up for the first time or log in for returning users, click <strong>Log in</strong> and then <strong>Log in with Discord</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gzgZVm4Ek0u7hGhXSj75wA.png" /></figure><p>You’ll be taken to Discord, and if you’re not already logged into Discord, you can log in. Then you’ll be prompted to authorize the Moonbeam Community Forum to access your Discord account. Upon authorization, you’ll be redirected to the Moonbeam Community Forum.</p><p>If you’re a first-time user, your account information will be pre-populated for you. All you’ll need to do is to click <strong>Create your account.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gzgZVm4Ek0u7hGhXSj75wA.png" /></figure><p>Once you’re logged in, you can explore the latest discussions, join conversations, and create your own discussion for a proposal idea you may have. Before posting or commenting for the first time, be sure to familiarize yourself with the <a href="https://forum.moonbeam.foundation/login">FAQ</a> to learn about the community guidelines.</p><h3>Proposal Statuses</h3><p>As you begin to explore the Moonbeam Discussion Forum, you’ll notice that proposals have a status tied to them. A proposal can have any of the following statuses depending on where the proposal is throughout the submission process:</p><p>- <strong>Idea</strong> — for new proposals seeking community feedback and Treasury Council input<br> — <strong>Submitted</strong> — for proposals that have been submitted formally on-chain along with a bond and have not yet been reviewed by any members of the Treasury Council<br> — <strong>Reviewing</strong> — for submitted proposals that are being reviewed by a member of the Treasury Council to determine whether the proposal should be converted to a Council motion<br> — <strong>Voting</strong> — for a proposal that has been converted to a Council motion and is being voted on by the members of the Treasury Council<br> — <strong>Passed</strong> — for a proposal that was voted on and approved by at least 3/5ths of the Treasury Council<br> — <strong>Rejected</strong> — for a proposal that was voted on and rejected by at least 1/2 of the Treasury Council</p><h3>Interacting with a Proposal</h3><p>The Moonbeam Foundation Forum’s homepage has three discussion categories. For Treasury-related proposals, you can navigate the <strong>Governance</strong> category and click on <strong>Treasury Proposals.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*my7mQCKNznkfbiG1VEOABg.png" /></figure><p>From the <strong>Treasury Proposals</strong> forum, you can review the Treasury proposal template, the top, and the latest proposals and create new proposals.</p><p>When viewing proposals, you can click on <strong>All tags</strong> to filter proposals by different tags, for example, getting the proposals for Moonbeam, Moonriver, or Moonbase Alpha or by the status of the proposal. Proposals with a lock icon next to them indicate the proposal is no longer up for discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZ5rF2JzDowKwq9beqNubQ.png" /></figure><p>If you click on a specific proposal, you can get more information about what the proposer is proposing. You can like, share, bookmark, pin, and set up notifications for the proposal. By default, you’ll be notified if someone mentions your name or replies to you. If you notice a problem with the proposal, you can <a href="https://forum.moonbeam.foundation/login#flag-problems">flag it</a>.</p><p>You can provide feedback on a proposal if it is labeled with the Idea tag and isn’t locked. Before commenting on the proposal, please take some time to review the <a href="https://forum.moonbeam.foundation/login">community guidelines</a>. To provide feedback on the proposal, you can take the following steps:</p><ol><li>Click on <strong>Reply</strong></li><li>Enter your thoughts into the text box</li><li>When you’re ready to submit your comment, you can click on <strong>Reply</strong> again. Otherwise, you can click on <strong>Close</strong>, where you’ll be able to delete your comment or save a draft for later.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bLbPyiEaz8oNW786Pg_9tg.png" /></figure><h3>Creating a Proposal Discussion</h3><p>The first step to creating a Treasury proposal is to post your idea on the <strong>Treasury Proposals</strong> forum. It is recommended to review the <a href="https://forum.moonbeam.foundation/login">community guidelines</a> before creating a post for the first time.</p><p>From the <strong>Treasury Proposals</strong> forum, you can get started by clicking on <strong>New Topic</strong>. The text editor will pop up at the bottom of the screen and will be pre-populated with the proposal template. You will need to adhere to the template structure when creating your proposal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MOEsrvJn67eY1ypuwJMbZQ.png" /></figure><p>For the first couple of times, you create a post, the panel on the right side will appear to help you get started. You can close out of that panel to see a preview of your proposal as you write it.</p><p>When filling out your proposal idea, you’ll take the following steps:</p><ol><li>Enter a title for your proposal idea. The title should follow the format as seen in the body of the proposal: [Proposal: XX][Status: Idea] proposal title . For example, [Proposal: XX][Status: Idea] Sample of treasury proposal in Moonbase Alpha . The XX will be updated with the proposal ID once the proposal has been formally submitted on-chain</li><li>Verify you’re adding your proposal to the correct category. All Treasury proposals should be in the <strong>Governance</strong> — <strong>Treasury Proposals</strong> category</li><li>For each of the sections, you can fill out the requested information for your Moonbeam Treasury Proposal (MBTP)</li><li>Once you’ve reviewed your proposal and it looks good, you can submit it by clicking on <strong>Create Topic</strong>. If you need more time, you can click <strong>Close</strong> and then <strong>Save the draft for later</strong>. Or you can also discard your proposal by clicking <strong>Close,</strong> then <strong>Discard</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zWfZi-MAfhKoVk8Or08ag.png" /></figure><p>Once you’ve submitted your proposal idea, it will be subject to approval by one of the forum moderators. The <a href="https://forum.moonbeam.foundation/about">moderators</a> will ensure the proposal follows the posting template and is associated with the right category and labels. Once posted, a notification will be sent to the Moonbeam Discord in the <a href="https://discord.gg/7HT6akkvD9">#🏛️governance-forum-updates</a> channel to inform community members that they can engage in discussion. The proposal will be open for discussion for at least five days.</p><p>After five days, the proposer can submit the proposal on-chain. When creating the on-chain proposal, the proposer will need to specify the beneficiary and the requested amount and submit the proposal along with a proposal bond. The proposal bond will be 5% of the requested amount or the proposal bond minimum, whichever is greater. The proposal bond minimum is 100 GLMR on Moonbeam or 1 MOVR on Moonriver. You can create and submit the proposal via Polkadot.js Apps. Make sure that in <a href="https://polkadot.js.org/apps/?rpc=wss://wss.api.moonbeam.network#/treasury">Polkadot.js Apps</a>, you are connected to the network you want to submit the proposal on.</p><p>Once submitted, the proposal will appear on <a href="https://moonbeam.polkassembly.network/">Polkassembly</a>. Then on Polkassembly, as the proposer, you can edit the description of the proposal to include a link to the proposal discussion on the Moonbeam Discussion Forum. You must be logged in to Polkassembly with the same account you used to submit the on-chain proposal. Make sure that in Polkassembly, you are connected to the network you’ve submitted the proposal on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S5RpbtYiWoP1Go2ZPqlLbg.png" /></figure><p>After submitting the on-chain proposal, you’ll need to edit your proposal on the Moonbeam Discussion Forum. You will need to update the title to include the proposal ID, and the status will need to be changed to <strong>Submitted</strong>. For example, [Proposal: 07][Submitted] Sample of treasury proposal in Moonbase Alpha . To update the title, you can click on the pencil icon next to the title and take the following steps:</p><ol><li>Update the title to include the proposal ID and change the status to <strong>Submitted</strong></li><li>Click on the check mark icon to save the changes</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j8v3AspujZ6-apNGWXRGNQ.png" /></figure><p>You’ll also need to add a comment to the proposal containing a link to the proposal on Polkassembly. To do so, you can take the following steps:</p><ol><li>Click on <strong>Reply</strong></li><li>Paste the link to the proposal on Polkassembly in the text box</li><li>To submit it, click <strong>Reply</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ROkR_gthyYfxhxJNPner9Q.png" /></figure><p>Once your comment has been posted, you’ll need to click on the <strong>Solution</strong> button to connect the on-chain proposal to the proposal discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xNkChhgaXckzQIC1XWEIZQ.png" /></figure><p>The solution button will turn green, and the body of the discussion post will automatically be updated to show the discussion has been solved via the on-chain proposal on Polkassembly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*knVzEypk2bkTV-FL8Cshdg.png" /></figure><p>As the proposal progresses through the remainder of the submission process, the Treasury Council will update the status of your proposal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5593f2ea169" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/using-the-moonbeam-community-forum-c5593f2ea169">Using the Moonbeam Community Forum</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the Moonbeam Community Forum]]></title>
            <link>https://medium.com/moonbeam-network/introducing-the-moonbeam-community-forum-20c7197957d3?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/20c7197957d3</guid>
            <category><![CDATA[moonbeams]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[community-forum]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Wed, 26 Oct 2022 18:43:01 GMT</pubDate>
            <atom:updated>2023-01-10T20:28:05.389Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YiDt0Xm-H_rginqA.png" /></figure><p>The Moonbeam community is welcome to participate in the <a href="https://forum.moonbeam.foundation/">Moonbeam Community Forum</a>, a new community space dedicated to hosting Moonbeam and Moonriver-related discussions, including technology development, governance, and future ecosystem initiatives. The forum will also serve the updated <a href="https://moonbeam.foundation/grants/">Moonbeam Foundation Grants</a> and <a href="https://moonbeam.foundation/news/proposal-treasury-program-approved/">Treasury Programs</a> as the designated discussion forum for proposals before and during democracy.</p><h3>About the Moonbeam Community Forum</h3><p>The Moonbeam Community Forum was launched as a dedicated space for the community to refine and brainstorm concepts, share their feedback and participate in community discussions about governance, technology development, future ecosystem initiatives, and more.</p><p>Users can access and view all live discussions by going to the <a href="https://forum.moonbeam.foundation/">Moonbeam Community Forum</a> site. Users must log in using their Discord credentials to start participating and posting. Comments should be made in English and follow the <a href="https://github.com/moonbeam-foundation/code-of-conduct">Moonbeam Foundation Code of Conduct</a>.</p><p>In brief, conforming to the Moonbeam Foundation Code of Conduct means participating in a way that creates a welcoming environment and a harassment-free experience for all community members. Users should use inclusive language, be respectful of differing viewpoints, accept constructive feedback, and focus on what is best for the network, community, and ecosystem.</p><p><a href="https://forum.moonbeam.foundation/about">Community moderators</a> will support the forum by ensuring discussions follow the Moonbeam Code of Conduct, answering general questions, and sending technical questions to the appropriate team members.</p><p>Community members in the Moonbeam Discord Server will also have access to a read-only channel called <a href="https://discord.gg/7HT6akkvD9">#🏛️governance-forum-updates</a> to get notified about new discussions posted in the forum.</p><h3>How to Use the Moonbeam Community Forum</h3><p>The Moonbeam Community Forum has four discussion categories available for the community to read, post submissions, and share ideas with other community members. To keep things clear and organized, users must select a category when posting using the outlined purpose of each discussion category.</p><p>The forum categories are divided into</p><ul><li><strong>Governance</strong><br> Dedicated to discussions about on-chain proposals. The subcategories are titled according to the proposal type, i.e., democracy, grant, or treasury.</li><li><strong>Development</strong><br> Community space to discuss the development of Moonbeam &amp; Moonriver networks, like core protocol, improvement proposals, developer tooling, and runtime upgrades.</li><li><strong>Site Feedback</strong><br> This category is a spot for members to add new labels and categories or propose ways to improve communication and collaboration on the forum.</li><li><strong>General Discussion</strong><br> The General category is for topics that don’t need a category or don’t fit into any other existing category.</li></ul><h3>Governance Proposals Discussions</h3><p>Governance in Moonbeam is a way for GLMR and MOVR token holders to be actively involved in critical decisions of the Moonbeam and Moonriver networks, including technical upgrades, treasury distribution, and ecosystem development.</p><p>Community engagement in governance includes participating in discussions, on-chain voting, and submitting proposals. The Moonbeam Community Forum plays a vital role in governance by being the central hub for governance discussions. Additionally, the forum is also the place to view the status of current and past proposals. <a href="https://moonbeam.polkassembly.network/referenda">Proposals</a> and <a href="https://moonbeam.polkassembly.network/discussions">discussions</a> published before the forum launch can be accessed through <a href="https://moonbeam.polkassembly.network/">Polkassembly</a>.</p><p>As part of the early phases of the community-driven <a href="https://moonbeam.foundation/news/proposal-treasury-program-approved/">Interim Treasury Program</a> and <a href="https://moonbeam.foundation/news/interim-grant-program/">Level 3-Grants</a> submission process, users and ecosystem projects are required to publish a draft version of <a href="https://forum.moonbeam.foundation/c/governance/treasury-proposals/">the treasury</a> or <a href="https://forum.moonbeam.foundation/c/governance/grant-proposals/">grant</a> proposal, respectively, for community discussion and feedback before it is published for on-chain voting. <a href="https://moonbeam.network/blog/using-moonbeam-community-forum/">Learn how to use the Moonbeam Community Forum to submit a Treasury proposal.</a></p><h3>Community Feedback is Essential</h3><p>In addition to the governance discussion functions, the Moonbeam Community Forum also <a href="https://request.moonbeam.network/tabs/3-launched">connects the community with the team developing Moonbeam</a> through a site to share ideas that support the growth and development of the Moonbeam and Moonriver networks and see the latest networks’ technology upgrades.</p><p>Launching the <a href="https://forum.moonbeam.foundation/">Moonbeam Community Forum</a> is a step forward in the continued effort to increase community involvement in key decisions of the Moonbeam and Moonriver networks. All the Moonbeam community is encouraged to join and participate in the community forum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20c7197957d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/introducing-the-moonbeam-community-forum-20c7197957d3">Introducing the Moonbeam Community Forum</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moonbeam Expands Cross-Chain Capabilities with Hyperlane Deployment]]></title>
            <link>https://medium.com/moonbeam-network/moonbeam-expands-cross-chain-capabilities-with-hyperlane-deployment-84d572be5498?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/84d572be5498</guid>
            <category><![CDATA[moonbuilders]]></category>
            <category><![CDATA[crosschain]]></category>
            <category><![CDATA[xcm]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Wed, 19 Oct 2022 13:32:42 GMT</pubDate>
            <atom:updated>2022-10-19T14:16:43.048Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LuPCtnDNfHMJzgt_.png" /></figure><p>Singapore — October 19, 2022 — <a href="https://moonbeam.network/">Moonbeam</a>, the top destination for cross-chain connected applications, has extended its interoperability capabilities through the addition of <a href="https://www.hyperlane.xyz/">Hyperlane</a>, an interoperability platform for building interchain applications. As a smart contract platform optimized for cross-chain scenarios, Moonbeam is designed to serve as an ideal deployment destination for applications that live across many chains. The addition of Hyperlane gives builders on Moonbeam even more <a href="https://moonbeam.network/blog/cross-chain-smart-contracts/">cross-chain messaging</a> capabilities and extends the number of networks connected to it, enabling developers to better construct all-in-one applications that securely communicate across many blockchains.</p><p>Cross-chain applications rely upon two core components to be effective: a number of smart contracts on various blockchains and a way to securely message between each of these instances. Moonbeam’s design allows it to be the hub of these many smart contracts, where <a href="https://moonbeam.network/blog/cross-chain-smart-contracts/">connected contracts</a> often act as “the brain” of the application and coordinate between many contracts on many chains. The introduction of Hyperlane adds a valuable component to this approach, allowing developers to send secure messages between chains with varying architectures, regardless of whether they are rollups (app-specific or general), app chains, or heterogeneous monolithic chains. Hyperlane allows developers building on Moonbeam to access seven networks, including Ethereum, Polygon, Avalanche, Optimism, Arbitrum, BNB, and Celo.</p><p>“Messaging protocols like Hyperlane provide the critical capability that allows Moonbeam to serve developers building cross-chain applications,” said Derek Yoo, CEO of PureStake, a development team building Moonbeam. “The Hyperlane integration provides Moonbeam developers access to unique destinations and novel features such as Sovereign Consensus, which gives developers fine-grained control over the security architecture of their application. The addition of Hyperlane strengthens the ability of Moonbeam to support cross-chain connected protocols.”</p><p>Hyperlane has a unique focus on future-proofing and was built with flexibility in mind. As part of this mission to evolve with developers and their applications, Hyperlane uses an approach called Sovereign Consensus, which lets developers configure their own security model utilizing Interchain Security Modules (ISMs). ISMs let a developer mix and match their approaches to economic security, optimistic security, proof of authority, and any other security model they’d like to enable.</p><p>“Our mission at Hyperlane is to connect blockchains with seamless interfaces for developers so that they can serve users on any chain. This vision is so clearly aligned with Moonbeam, and we’re thrilled to collaborate in this growing ecosystem,” said Jon Kol, co-founder at Hyperlane.</p><p>As a destination for cross-chain builders, Moonbeam offers broad protocol support for a variety of message-passing protocols, including <a href="https://moonbeam.network/announcements/moonbeam-layerzero/">LayerZero</a>, <a href="https://moonbeam.network/blog/connected-contracts-axelar/">Axelar</a>, <a href="https://wormhole.com/">Wormhole</a>, Polkadot’s XCM, and now Hyperlane. By offering a variety of messaging standards and formats, Moonbeam gives builders ultimate control over their cross-chain application design, allowing them to optimize for efficiency as well as optimal user experience. As cross-chain-connected contracts, applications can communicate and interact across blockchains using native assets on other chains without needing to move them, effectively making Moonbeam DApps into access points from which a user can tap into many tokens and chains at once.</p><h3>About the Moonbeam Network</h3><p><a href="https://moonbeam.network/">Moonbeam</a> is an Ethereum-compatible smart contract platform on the Polkadot network that makes it easy to build natively interoperable applications. This Ethereum compatibility allows developers to deploy existing Solidity smart contracts and DApp frontends to Moonbeam with minimal changes. Like Moonriver, its sister parachain on Kusama, Moonbeam is expected to accumulate developer and user activity from the <a href="https://moonbeam.network/community/projects/">100+ projects</a> building DApps and protocols on the network. As a parachain on the Polkadot network, Moonbeam benefits from the shared security of the Polkadot Relay Chain and integrations with other chains that are connected to Polkadot. Learn more: <a href="https://moonbeam.network/">https://moonbeam.network/.</a></p><h3>About Hyperlane</h3><p><a href="https://www.hyperlane.xyz/">Hyperlane</a> is an interoperability platform empowering developers to build interchain applications, applications that can communicate between blockchains and serve users regardless of the chain they are on. Hyperlane is building the simplest and most secure way to communicate between blockchains, allowing developers to spend time focusing on their applications instead of on blockchain infrastructure. Learn more: <a href="https://www.hyperlane.xyz/">https://www.hyperlane.xyz/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84d572be5498" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/moonbeam-expands-cross-chain-capabilities-with-hyperlane-deployment-84d572be5498">Moonbeam Expands Cross-Chain Capabilities with Hyperlane Deployment</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Darwinia XCM Integration Connects Moonriver and Moonbeam Ecosystems for Cross-Chain Interaction]]></title>
            <link>https://medium.com/moonbeam-network/darwinia-xcm-integration-connects-moonriver-and-moonbeam-ecosystems-for-cross-chain-interaction-d7bd9f8e13f0?source=rss-f71de34470d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7bd9f8e13f0</guid>
            <category><![CDATA[moon-river]]></category>
            <category><![CDATA[xcm]]></category>
            <category><![CDATA[moonbeams]]></category>
            <dc:creator><![CDATA[Katherine]]></dc:creator>
            <pubDate>Tue, 18 Oct 2022 13:18:49 GMT</pubDate>
            <atom:updated>2022-10-18T17:10:31.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wwiVXZcJqakT-Q1qvwQo0w.png" /></figure><p>Singapore — October 18, 2022 — <a href="https://moonbeam.network/">Moonbeam</a>, the top destination for cross-chain connected applications, has announced an XCM integration with <a href="https://darwinia.network/">Darwinia</a>, which will allow <a href="https://moonbeam.network/builders/connected-contracts/">connected contracts</a> on Moonbeam to communicate via Darwinia’s Universal Cross-Chain Messaging Network once remote EVM calls through XCM are enabled. Furthermore, this will connect any contract in Moonbeam to any network outside of the Polkadot ecosystem, like Ethereum, Avalanche, and others, once Darwinia’s Light-Client Based Cross-Chain Messaging protocol and XCM are combined. To start, the XCM integration will allow the movement of RING, Darwinia’s token, as an <a href="https://docs.moonbeam.network/builders/xcm/xc20/">XC-20</a> inside <a href="https://www.dtmb.xyz/moonbeam">Moonbeam’s broad dApp ecosystem.</a></p><p>Darwinia is a generalized light-client based message delivery network and Polkadot parachain that provides a highly-secure and programmable bridging framework between Polkadot and EVM chains such as Ethereum, Polygon, BSC, and others, and also provides an SDK to simplify the development process and create seamless user experiences, especially when transacting across multiple chains.</p><p>The <a href="https://docs.moonbeam.network/builders/xcm/overview/">Moonbeam XCM</a> connection with Darwinia smart contract platform will bring Darwinia Universal Cross-Chain Message SDK for use in developing cross-chain asset bridges, and cross-chain access to assets for use as collateral on a remote blockchain, and allowing asset exchanges across chains with a single transaction in the future. These integrations look forward to allowing NFTs to move across multiple chains, and unified multi-chain governance with no requirement to move assets to a central voting chain.</p><p>This connection with Darwinia strengthens Moonbeam’s delivery of <a href="https://moonbeam.network/builders/connected-contracts/">cross-chain connected applications</a> uniting functionally within and beyond Polkadot and Kusama networks. The Darwinia SDK allows cross-chain use cases while improving the simplifying user experience by abstracting away all the intermediate routes and protocol translations along the way, even if there are multiple network hops.</p><p>As a whole, the Polkadot and Kusama ecosystems work together with parachains like Moonbeam and Darwinia to strengthen and secure communications using the growing library of options for secure cross-chain messaging available. Connections between Kusama and Polkadot in addition to the external connections enabled via Moonbeam with Axelar, Layer Zero, Wormhole, and Hyperlane contribute to the next generation of applications to move Dotsama forward.</p><h3>About the Moonbeam Network</h3><p><a href="http://moonbeam.network/">Moonbeam</a> is a smart contract platform for building cross-chain connected applications that can access users, assets, and services on any chain. By uniting functionality from Ethereum, Cosmos, Polkadot and more into a single platform, Moonbeam solves today’s fragmented user experience — unlocking true interoperability and paving the way for the next generation of applications. The Moonbeam platform uses integrated cross-chain messaging to allow developers to create smart contracts that access services across many remote blockchains. This approach, plus Moonbeam’s developer-friendly EVM platform, vast tool support, and modern Substrate architecture, creates the ideal development environment for building connected applications.</p><h3>About Darwinia</h3><p>Darwinia is a cross-chain messaging infrastructure, which provides a light client-based, programmable, universal cross-chain messaging network for decentralized applications. <a href="https://docs.darwinia.network/lcmp-overview">Darwinia’s light-client cross-chain messaging protocol(LCMP)</a> is used to bridge cross-chain messages between substrate chains, and also between substrate and EVM chains. The <a href="https://docs.darwinia.network/sdk/api-reference">Darwinia SDK</a> allows developers to easily integrate cross-chain capabilities into their Dapps which will have profound implications for cross-chain interoperability and Darwinia as a cross-chain messaging infrastructure will facilitate the building of a hybrid cross-chain network for Polkadot.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7bd9f8e13f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moonbeam-network/darwinia-xcm-integration-connects-moonriver-and-moonbeam-ecosystems-for-cross-chain-interaction-d7bd9f8e13f0">Darwinia XCM Integration Connects Moonriver and Moonbeam Ecosystems for Cross-Chain Interaction</a> was originally published in <a href="https://medium.com/moonbeam-network">Moonbeam Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>