<?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 Chris Li on Medium]]></title>
        <description><![CDATA[Stories by Chris Li on Medium]]></description>
        <link>https://medium.com/@chrisli2046?source=rss-9dd0c8ef9484------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s691GCpP2IQr7aEBphNKRQ.jpeg</url>
            <title>Stories by Chris Li on Medium</title>
            <link>https://medium.com/@chrisli2046?source=rss-9dd0c8ef9484------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:48:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisli2046/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[OAK Network Is Now Ava Protocol: From Polkadot to Ethereum and Beyond]]></title>
            <link>https://medium.com/avaprotocol/oak-network-is-now-ava-protocol-from-polkadot-to-ethereum-and-beyond-485dae9636a1?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/485dae9636a1</guid>
            <category><![CDATA[eigenlayer]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Thu, 06 Jun 2024 17:15:46 GMT</pubDate>
            <atom:updated>2024-06-06T17:15:46.513Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Expanding our autonomous transaction capabilities to multiple blockchain ecosystems while maintaining seamless continuity.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XMaMJK0Esriw_WuN" /></figure><p>Dear Community,</p><p>We’re excited to announce that <strong>OAK Network is evolving into </strong><a href="https://avaprotocol.org/"><strong>Ava Protocol</strong></a>, broadening our autonomous transaction infrastructure to include the Ethereum ecosystem. This evolution marks a significant milestone in our journey, and we want to assure you that our commitment to our community remains unwavering.</p><h3>Meet Ava Protocol</h3><p>Ava Protocol is <strong>an intent-based infrastructure that empowers private autonomous transactions for Ethereum and beyond</strong>. This evolution started with our strong foundation in Polkadot and continues to develop, enabling true cross-chain automation and composability. The name Ava represents an intelligent, spiritually strong character, symbolizing our smart, ambitious, and tenacious protocol team and community.</p><h3>Serving both Ethereum and Polkadot</h3><p>We’re thrilled to announce that our mainnet will launch on both Ethereum’s EigenLayer and on Polkadot, initially as a parachain and then transitioning to <a href="https://x.com/gavofyork/status/1780897336857698418">Polkadot JAM</a> when it’s live.</p><p>Our implementation for Polkadot is mature, with over 10,000 unique wallet addresses registered on the testnet. We’ve spent years refining our time and price automation pallets. The expansion to Ethereum, supported by a new round of funding led by Electric Capital, will allow us to unlock new frontiers and cement our position as leaders in cross-chain decentralized automation.</p><h3>OAK tokens will become AP</h3><p>We know many of you are wondering what will happen to OAK tokens. Rest assured, there will be no changes except for the token name and ticker. All other aspects, including total supply, category percentage, unlock schedule, and the amount that each user will receive, remains the same. We will provide more details about the tokenomics as the token launch date approaches.</p><p>The new AP token will be accessible on both Ava Protocol AVS and Polkadot, compatible with both EVM and Substrate wallets. Tokens will be transferable from day one, and users will soon be able to bridge them between the two networks.</p><p>We’re currently in discussions with several tier-1 centralized exchanges, and are also considering a hybrid launch on both CeFi and DeFi platforms.</p><h3>A new plan for TUR token</h3><p>The Turing Network token (TUR), our testnet token within the Kusama ecosystem, has been actively traded on the MangataX DEX since its inception. Following Mangata’s rebranding, questions have arisen regarding TUR’s future tradability. We’re exploring options to ensure TUR’s continuity and are in the process of assessing potential solutions. We’re committed to protecting our community’s interests, and will publish a detailed roadmap for TUR soon. Rest assured, your TUR tokens will remain SAFU.</p><h3>Roadmap for the next 3 months</h3><p>This summer, our primary objective is to launch our protocols as an EigenLayer AVS and Polkadot parachain, along with the AP token. We also aim to establish Ava Protocol as the leading developer in the autonomous transaction space, covering Smart Contract Automation, DeFi Automation, NFT Automation, and RWA Automation. Our evolution from OAK to Ava Protocol is the first step in this process.</p><p>At the same time, we’re strengthening our developer adoption initiatives. Our <a href="https://avaprotocol.org/blog/oak-grants-updates-bagpipes-defi-automation-workflow-builder-m1-delivery">open grant program</a> has attracted talented teams that are building a drag-and-drop visualization UI as well as limit order functionalities for DEX. We’ve also been busy sponsoring hackathons and startup competitions, as we just did during Consensus 2024.</p><h3>Embracing the future</h3><p>Our expansion from Polkadot to Ethereum and beyond is a strategic step to grow our technology and better serve our community. We’re dedicated to building powerful cross-chain automation infrastructure that remains rooted in our strong foundation with Polkadot. Thank you for your continued support as we enter this exciting new chapter together.</p><p>Let’s go forward! 🚀</p><h4>__</h4><h4>Join the Ava Protocol community on <a href="https://x.com/ava_protocol">X (Twitter)</a>, <a href="https://discord.com/invite/7W9UDvsbwh">Discord</a>, and <a href="https://t.me/ava_protocol">Telegram</a>.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=485dae9636a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/oak-network-is-now-ava-protocol-from-polkadot-to-ethereum-and-beyond-485dae9636a1">OAK Network Is Now Ava Protocol: From Polkadot to Ethereum and Beyond</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Into OAK’s Cross-chain Automation World: 2023 Year in Review]]></title>
            <link>https://medium.com/avaprotocol/into-oaks-cross-chain-automation-world-2023-year-in-review-90c08c263e7c?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/90c08c263e7c</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[oak-network]]></category>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[polkadot-network]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Thu, 18 Jan 2024 18:56:20 GMT</pubDate>
            <atom:updated>2024-01-18T18:56:20.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qtuJXtsME-zrmlVx4ylaZQ.png" /></figure><p>Dear OAK community,</p><p>The year 2023 has been a year of growth for OAK Network, both in terms of community and products. We would like to extend our heartfelt gratitude to both our community members, and to the Polkadot and Kusama network communities for their unwavering support, which has played a crucial role in our success this year. 🫶</p><h3>Product Development</h3><h4>Launch of the Automation Hub</h4><p>Undoubtedly, the highlight of this year was the introduction of the OAK Network’s <a href="https://www.notion.so/OAK-Managed-Collators-d3f160d1368040e9a79fe0776a12d609?pvs=21"><strong>Automation Hub</strong></a>. This web app aims to serve as an efficient index of automation applications, created by our team or the community, to help users quickly navigate and discover the specific functions they need. We will also regularly review and include new apps to ensure security and improve the user experience. The Automation Hub exemplifies our dedication to building top-notch automation solutions.</p><h3>OAK Network on Twitter: &quot;The WAIT for @OAK_Network&#39;s Automation Hub Launch is OVER!Now @MoonriverNW @ShidenNetwork &amp; Turing Network users can utilize the following features on the Automation Hub:💵Auto-Pay♻️Stake &amp; Compound🌉Auto-Bridge🗄Task HistoryTry it out here⤵️ https://t.co/n2kUUyf1t9 pic.twitter.com/ddxN45OclM / Twitter&quot;</h3><p>The WAIT for @OAK_Network&#39;s Automation Hub Launch is OVER!Now @MoonriverNW @ShidenNetwork &amp; Turing Network users can utilize the following features on the Automation Hub:💵Auto-Pay♻️Stake &amp; Compound🌉Auto-Bridge🗄Task HistoryTry it out here⤵️ https://t.co/n2kUUyf1t9 pic.twitter.com/ddxN45OclM</p><h4>Infrastructure Enhancements</h4><p>The Automation Hub represents just the tip of the iceberg, as a significant part of our work involves engineering secure and developer-friendly infrastructure. This includes the development of the blockchain, SDK, data indexer, documentation, and out-of-the-box code snippets. 🛠 🧰</p><p>For example, in Q3 2023, in response to valuable feedback from our partners and the requirements of our internal team, we built a <strong>Data</strong> <strong>Insights services, including a Data Monitoring dashboard and a GraphQL API</strong>, to address challenges of our current and future products. This solution now plays a vital role among our products. For more information, please refer to the <a href="https://medium.com/oak-blockchain/introducing-oak-networks-data-monitoring-insights-dashboard-fb6789c955ce">OAK Networks’ Data Monitoring Insights Dashboard article</a>.</p><h4>Ecosystem dApps</h4><p>Thanks to the comprehensive developer tools and documentation provided by the OAK team, numerous teams have joined us in building automation features. Among them, the Yieldbay team has <a href="https://github.com/OAK-Foundation/Grants-Program/pull/3">received a grant</a> to develop an LP Auto-compounder app for MangataX DEX. Currently, there are over 20 dApps leveraging the automation infrastructure we provide, offering services like recurring payments, stake compounding, and LP reward compounding.</p><p>I am also honored to have been invited <strong>as a visiting lecturer by the Polkadot Blockchain Academy to UC Berkeley</strong>. During my workshop session, the students hacked code and contributed many great ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SQmOZytCfMeFCiwlArteSA.jpeg" /><figcaption>Chris is conducting a workshop session at UC Berkeley</figcaption></figure><p>We are actively seeking talented teams to collaborate with us and build upon our technology. If you are a developer and interested, please check out our <a href="https://github.com/OAK-Foundation/Grants-Program">Grants Program</a>.</p><h3>Community Engagement and Growth</h3><p>In 2023, our community has been more active than ever before. We are delighted to see ambassadors and community members frequently requesting treasury funding and sharing their ideas to help grow and engage the community.</p><h4>Social Media Growth</h4><p>Throughout the year, we have been consistently posting development updates and hosting events. Our Twitter follower count has grown organically from 23K at the beginning of 2023 to 53K, a 130% increase. Additionally, our Discord server has seen an impressive growth, with over 15K members, a 3.5x increase since before.</p><p>What’s even more exciting to see is that <strong>the engagement rate is very high, which reflects the liveliness of our community</strong>. Our Twitter account’s monthly total engagement (replies, likes, and retweets) remains above 10K per month and experienced a 70% growth in December.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*vFTZ9iogizK_z2i0OVvW0w.png" /><figcaption>Total engagement of OAK’s Twitter account for December 2023</figcaption></figure><p>As a result, Turing Network now has gained more than 10K wallet address on-chain, a 185% growth from the beginning of the year. 📈</p><h4>Galxe Campaigns</h4><p>December marked the beginning of a significant chapter in our marketing strategy as we launched campaigns on Galxe. This initiative proved to be quite successful, attracting over 40K members in just a month. Our aim with these campaigns was not only to expand our reach but also to actively engage with our growing community.</p><p>We highly encourage you to join and <strong>follow </strong><a href="https://www.notion.so/Into-OAK-s-Cross-chain-Automation-World-2023-Year-in-Review-81eccef7d6a84caf90df5b11f7faf3e9?pvs=21"><strong>our space on Galxe</strong></a>, where we regularly update about ongoing and upcoming campaigns. These campaigns are not just informative but also rewarding. Many of them feature a prize pool of 500 USDT with simple tasks, creating an exciting opportunity for our members. 💵 💵</p><h3>OAK Network on Twitter: &quot;🚨NEW @OAK_Network x @Galxe Campaign!🚨🚀To promote the COUNTDOWN to our Automation Hub Launch🚀💰We&#39;re hosting a #Galxe airdrop raffle for anyone w/ an eth wallet with a Total Prize Pool of 500 $USDT Enter Here ⤵️https://t.co/FIVX6fS6Io pic.twitter.com/N2fdHs8RB2 / Twitter&quot;</h3><p>🚨NEW @OAK_Network x @Galxe Campaign!🚨🚀To promote the COUNTDOWN to our Automation Hub Launch🚀💰We&#39;re hosting a #Galxe airdrop raffle for anyone w/ an eth wallet with a Total Prize Pool of 500 $USDT Enter Here ⤵️https://t.co/FIVX6fS6Io pic.twitter.com/N2fdHs8RB2</p><h4>Ambassador Program</h4><p>Thanks to our Ambassador program, we currently have 28 active ambassadors who are instrumental in building the OAK community. They fulfill various responsibilities, including providing product feedback, creating short video content, and moderating social media. In last Spring, our community manager Jorge has written <strong>an explainer: </strong><a href="https://medium.com/oak-blockchain/oak-networks-ambassador-program-a-year-in-review-cb8031326b77"><strong>OAK Network’s Ambassador Program: A Year in Review</strong></a><strong>.</strong></p><p>If you are interested in joining our Ambassador program, please feel free to contact us <a href="https://discord.gg/7W9UDvsbwh">on Discord</a>!</p><h4>We Throw Great Parties!</h4><p>We take pride in hosting memorable parties and always strive to provide the best experiences for our attendees! Throughout the year, we have hosted and co-hosted more than 20 parties, including the official opening party of the Stanford Blockchain Conference, the closing party of the Polkadot Blockchain Academy, and San Francisco crypto meetups. 🍺</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p1p6_M2rIrWtDu3tBOc2bQ.jpeg" /><figcaption>OAK co-hosted the opening party of Stanford Blockchain Conference with Electric Capital</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dF8i3VSHsFj7lVTQRg8zoQ.jpeg" /><figcaption>OAK hosted the closing party of Polkadot Blockchain Academy</figcaption></figure><h3>Strategic Collaborations</h3><p>As OAK aims to achieve cross-chain automation, we maintain a strong relationship with our parachain and XCM partners. These collaborations play a crucial role in shaping OAK’s product roadmap and greatly contribute to expanding our reach.</p><ol><li>This February, we completed and published a product demo of the <strong>Liquidity Pool auto-compound feature for MangataX DEX</strong>. This demo later evolved into a real product developed by YieldBay, marking the first cross-chain automation showcase delivered by our team. This achievement represents an important milestone in OAK’s short history. To delve deeper into this topic, you can explore the <a href="https://medium.com/oak-blockchain/oak-network-mangata-xcm-liquidity-pool-auto-compounding-%EF%B8%8F-93926ea57a25">OAK Network &amp; Mangata: XCM Liquidity Pool Auto-Compounding article</a>.</li><li>Shortly after, we successfully convinced the Moonriver community to approve our governance proposal <strong>to open HRMP channels between Turing Network and Moonriver</strong>, and register our asset xcTUR on Moonriver. Since then, we have been actively testing Moonriver’s unique remote execution capabilities. Discover the full story in the <a href="https://medium.com/oak-blockchain/moonbeam-oak-network-integrate-to-create-xcm-automation-1ec2b6ab5a23">Moonbeam &amp; OAK Network Integrate to Create XCM Automation article</a>.</li><li>Lastly, we are thrilled to announce our partnership with the ArthSwap team to build <strong>a limit order feature for their DEX on the Astar Network</strong>. Through remote execution and automation of the ArthSwap smart contract, OAK enables users to schedule orders based on price movement. For additional details, the <a href="https://medium.com/oak-blockchain/introducing-non-custodial-price-automation-for-limit-orders-liquidation-prevention-df8ffde8cefd">Introducing Non-Custodial Price Automation for Limit Orders &amp; Liquidation Prevention article</a> offers an in-depth look.</li></ol><h3>What’s New in 2024</h3><p>I will soon publish another article to explain the future roadmap for OAK Network, but we have big plans ahead! Here are two important milestones that we are laser-focused on achieving in the beginning of 2024!</p><h4>More TUR Listings</h4><p>Our Turing Network token, $TUR, has been listed on MangataX DEX for over a year. Recently, we have been actively seeking new listing partners, including both centralized exchanges and DEXs. For example, Moonriver has already approved and implemented our proposal to create the XC20 token, xcTUR, on their network. Our team is currently discussing the possibility of <strong>trading with Solarbeam and lending with Moonwell</strong>.</p><p>Today, you can track TUR token’s price on <a href="https://www.coingecko.com/en/coins/turing-network">Coingecko</a>.</p><h4>Geared up for OAK Mainnet</h4><p>Another important milestone for us is the launch of the OAK mainnet. With the tools and technical experience we have accumulated, the mainnet launch poses no problem. I believe it will be in full swing immediately after the launch. 💪 💪</p><h3>Conclusion</h3><p>The year 2023 has been a defining period for OAK Network, marked by significant achievements, community growth, and technological advancements. Our team’s dedication to innovation and user engagement has laid a strong foundation for future success.</p><p>The entire OAK team would like to express our sincere gratitude for the support of our community. Let’s go forward together in 2024! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90c08c263e7c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/into-oaks-cross-chain-automation-world-2023-year-in-review-90c08c263e7c">Into OAK’s Cross-chain Automation World: 2023 Year in Review</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ How to Participate in OAK Network's Airdrop on Galxe]]></title>
            <link>https://medium.com/avaprotocol/how-to-participate-in-oak-networks-airdrop-on-galxe-be730fa8813f?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/be730fa8813f</guid>
            <category><![CDATA[oak-network]]></category>
            <category><![CDATA[galxe]]></category>
            <category><![CDATA[rewards-programs]]></category>
            <category><![CDATA[airdrop]]></category>
            <category><![CDATA[usdt]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Thu, 23 Nov 2023 01:40:58 GMT</pubDate>
            <atom:updated>2023-11-23T02:35:16.659Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*2elXOVRieQsJaDoLSmOn3g.png" /></figure><p>Hi OAK community,</p><p>We are thrilled to host <strong>our first #Galxe airdrop raffle with a total prize pool of $500 USDT!</strong> 🌟 Get ready to dive into the action with OAK Network on Galxe and make your mark! Follow these simple steps to join the fun:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*RKoeij2f-xb0BmeReXErEQ.png" /><figcaption>Source: <a href="https://x.com/oak_network/status/1727413838415569164?s=20">https://x.com/oak_network/status/1727413838415569164?s=20</a></figcaption></figure><p>1. <strong>Navigate to the campaign page, </strong><a href="https://galxe.com/oaknetwork/campaign/GC1TetU4nU"><strong>https://galxe.com/oaknetwork/campaign/GC1TetU4nU</strong></a></p><p>2. Click “Have the Acorn role in OAK Network Discord Server”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lubw69Pb0wqH8NvC" /></figure><p>3. Click “Authorize” to connect your Discord account here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wpCCcz8F3T36Vc15" /></figure><p>4. Click “Accept Invite” to join the OAK Network discord community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eydUnAjwplBBHEPP" /></figure><p>5. Once you have joined the Discord, check out the <strong>Welcome Instructions</strong> and click “Complete”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4vPzhMVjqFv7GV7K" /></figure><p>6. Once the Welcome instruction are completed, the “rules &amp; guidelines” window will automatically pop up. Read the rules and click the “I have read and agree to the rules” field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cMUETrUJzk2AnAa5" /></figure><p>7. Click “Submit”, then the system will navigate to the “#rules-and-guidelines” channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HBBLzuBhaQQ-_kBU" /></figure><p>8. In order to get the <strong>Acorn status</strong> on the Discord server, <strong>click the 👍 or other emojis</strong> after checking the rules-and-guidelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EGJUZ3ErexmsAu_N" /></figure><p>9. After completing the above steps on Discord, navigate back to the Galxe site and click the “Refresh” button to update task status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nQy4-H3sJiKtyBc3" /></figure><p>10. Click the 2nd task, “Join the <a href="http://twitter.com/OAKNetworkCommunity">@OAKNetworkCommunity</a> on Telegram”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mV3gMRp9PZIKi-TT" /></figure><p>11. Click “VIEW IN TELEGRAM” to join OAK Network’s Telegram community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vf4nqAj9h4c0KcmI" /></figure><p>12. Click here to move to “Follow oak_network on Twitter” task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nZaIxPgnIKi3D31K" /></figure><p>13. The below steps 14–19 are intended for first-time setup of a Twitter account on Galxe. If you’ve already connected your Twitter to your Galxe account, please proceed directly to Step #20.</p><p>14. For connecting a Twitter account on Galxe, first click “Tweet”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h2wUOoWop5EXiFiK" /></figure><p>15. Click “Post” to tweet out the message pre-filled by Galxe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tepTPPFtOJF0K2Fz" /></figure><p>16. Click the “Share” button, to get the link of your tweet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-xPcRegb8zMgHZ0J" /></figure><p>17. Click “Copy link”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Aglr_fPKkiynPakV" /></figure><p>18. Navigate back to the Galxe site and paste the link to the “Paste link here” field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yc-zihrWo3tDN1JL" /></figure><p>19. Click “Verify” and complete Twitter account connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-eIaT5xYJ4t-7-oL" /></figure><p>20. Next, click “Follow <a href="http://twitter.com/oak_network">@oak_network</a> on Twitter”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mSQYfTSlHU2wP63g" /></figure><p>21. Click “Follow” to follow OAK Network’s Twitter account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rJW-UeWZtEiFct3n" /></figure><p>22. Next, click “OAK Network’s space users” task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wtBzeUKfo2wbjwT-" /></figure><p>23. Click “Follow” to follow OAK Network Galxe to finish the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k6tprJ2RyVicgAvX" /></figure><p>24. Click “Quote the Tweet and mention 3 friends” task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9JyQzg9LOPZ-6TLT" /></figure><p>25. The Tweet post will pop up, mention three twitter users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*16bP8RUSzr5IsvkK" /></figure><p>26. Click “Post” to finish the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f3EmDrC1tQ39Nulq" /></figure><p>27. Lastly, click the “Like <a href="http://twitter.com/oak_network">@oak_network</a> Tweet” task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4ABqVoDX_H2nCCxL" /></figure><p>28. A Twitter post will pop up. Click “Like”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QihYWifVH-rUzlPj" /></figure><p>29. After completing all tasks and marking them as “Done”, the “Not Eligible” button at the bottom will change to “Participate”. Simply click on “Participate” to finalize your enrolment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LOoPip71isMxtgtu" /></figure><p>30. You can monitor the raffle status here to see when the campaign concludes. If you are chosen as a winner after the campaign ends, the button will change to ‘Claim,’ enabling you to withdraw your 25 USDT reward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zWQhrlJy6-0owchL" /></figure><p>Thank you for reading this far. 🎉 Keep updated with the raffle status in our Telegram or Discord communities, and be prepared to claim your 25 USDT reward if you win!</p><h3>About OAK Network</h3><p>OAK Network is a layer-1 blockchain that enables multi-chain applications to automate single or recurring transactions using a simple ‘if this’ trigger condition and ‘then that’ transaction instruction. As the web3 hub for cross-chain automation, OAK unlocks a diverse range of rich DeFi user experiences including scheduled and recurring payments, stable-cost-averaging, stop loss and limit orders, and non-custodial copy trading.</p><p><a href="https://discord.gg/vmvmWFmW5p">Discord</a> | <a href="https://github.com/OAK-Foundation">Github</a> | <a href="https://link.medium.com/0rgiZXwWnsb">Medium</a> | <a href="https://t.me/OAK_Announcements">Telegram</a> | <a href="https://twitter.com/oak_network">Twitter</a> | <a href="https://oak.tech/">Website</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be730fa8813f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/how-to-participate-in-oak-networks-airdrop-on-galxe-be730fa8813f">🚀 How to Participate in OAK Network&#39;s Airdrop on Galxe</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Turing Network TUR Burning Event & New Token Burning Mechanism]]></title>
            <link>https://medium.com/avaprotocol/announcing-turing-network-tur-burning-event-new-token-burning-mechanism-6d3cd06e3241?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d3cd06e3241</guid>
            <category><![CDATA[polkadot-network]]></category>
            <category><![CDATA[oak-network]]></category>
            <category><![CDATA[tokenburn]]></category>
            <category><![CDATA[tokenomics]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Tue, 21 Nov 2023 18:11:29 GMT</pubDate>
            <atom:updated>2023-11-21T18:43:23.238Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In the following article we will describe and explain the </em><strong><em>Turing Network Token Burning Event</em></strong><em> which will reduce the circulating supply of our Kusama parachain tokens (TUR) by around 32%. Additionally we will describe the new </em><strong><em>automatic token burning mechanism</em></strong><em> which will be coming to the Turing Network in the short future.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*40xULi5MNJdxYJszeGP6sg.png" /></figure><h3>Introduction</h3><p>OAK Network’s Kusama parachain Turing Network has come a long way since producing the network’s first block. With nearly 4 million blocks generated since its launch, a substantial portion of the Turing Network’s treasury funds now resides freely in hardware wallets owned by the OAK team. Furthermore, an annual inflation rate of 5% (please refer to <a href="https://oak.tech/turing/token/#inflation">Token Inflation</a>) allocates 33% of its newly minted tokens to those wallets each year.</p><p>In light of the current state of the treasury, where a significant portion of allocated funds remains under utilized, and as part of our commitment to supporting our dedicated community, we have made the strategic decision to refine the network’s future tokenomics. <strong>This will be achieved through a token burning event, effectively reducing the circulating supply of TUR tokens by an impressive 32%.</strong> To break it down further, this equates to an 8% reduction per quarter. However, due to a slight delay in conducting the burn, we have opted to burn the cumulative amount of four quarters’ worth of tokens at the year’s end.</p><p>In addition to this immediate token burning event, we have also introduced an innovative auto-burn mechanism, which will take place on a regular cadence in the future. This mechanism will further contribute to the ongoing optimization of our network’s tokenomics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*_nDfa3DuktHNsYjK1Ho2lw.png" /><figcaption>Turing Network has issued 754M TUR total at the moment — source: <a href="http://turing.subscan.io/">turing.subscan.io</a></figcaption></figure><h3>What is a Token Burn?</h3><p><strong>A token burn is the process of permanently removing cryptocurrency tokens from circulation</strong> which reduces the total supply of tokens available on the chain. Essentially a token burn destroys or deletes a portion of the total coins available to the network. The removal of a portion of tokens from circulation creates a deflationary effect and are common across many blockchain projects.</p><p>While the Turing Network is currently using our Gas &amp; Fee Instant Burning Mechanism, our team at OAK Network wants to accelerate the amount of tokens being burned by holding a one-time token burning event and introducing a secondary auto-burn mechanism.</p><p>As part of the one-time event for token burning, our team will burn 32% of the total tokens from the wallets listed below. <strong>It’s important to note that no user wallets will be affected by the burn.</strong></p><ul><li><em>Ecosystem Growth</em></li><li><em>Strategic Partnerships</em></li><li><em>Developer Incentives</em></li><li><em>Crowdloan Rewards</em></li><li><em>Initial Collator Fund</em></li><li><em>Early Backers</em></li><li><em>Future Parachain Reserve</em></li><li><em>Community DAO</em></li></ul><p><strong>This will result in the burning and removal of approximately 240 million out of the 755 million TUR tokens from circulation.</strong> For a breakdown of the TUR token distribution check out <a href="https://oak.tech/turing/token/">TUR Distribution on our website</a> or see the diagram below.</p><h3>Changes of Token Supply Curve</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*etmN7-Dyh_L3_cr3OPriGQ.png" /><figcaption>TUR Circulating Supply Before Burn</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ritSAHJIFGEzg7qpTCADJw.png" /><figcaption>TUR Circulating Supply After Burn</figcaption></figure><p>The figures above illustrate the circulating supply curve of the TUR token before and after the token burning event. Following the burn, a significant number of TUR tokens will be removed from circulation, resulting in a reduced supply curve. The majority of tokens burned can be categorized into three groups:</p><ol><li><strong>Initial Collator Fund:</strong> This portion of tokens was intended to support the initial set of 24 collators responsible for running the network. Since the minimum token requirement for collator candidates was set relatively low, not all tokens in this category were fully utilized. As a result, 75% of this portion will be burned, while the remaining 25% is reserved for future collator needs.</li><li><strong>Crowdloan Rewards:</strong> The Crowdloan Rewards portion was meant to reward participants in the Kusama crowdloan. However, due to a decrease in the KSM requirement to win a crowdloan during the launch of the Turing Network, only a small portion of the originally planned tokens were used. Consequently, 75% of this portion will be burned.</li><li><strong>Future Parachain Reserve:</strong> This Reserve was designated for purchasing KSM with TUR to fund parachain slots over time. However, no TUR tokens from this reserve were utilized, as our team has been purchasing KSM using stable coins. Additionally, with both Polkadot and Kusama moving towards a more flexible coretime runtime model in the future, the demand for bidding on parachain slots is expected to decrease. As a result, we have decided to burn half of this reserve as well.</li></ol><p>All other categories were burned by 10%, resulting in a total burn of 240M TUR, which accounts for 31.8% of the current token supply.</p><h3>Changes of Category</h3><p>The two pie charts below provide a visual representation of the changes in the allocation of treasury funds following the token burning event, highlighting the adjustments made to support the growth and development of the Turing Network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Ew1hSXP2fQd-qV1Ix6CUOg.png" /><figcaption>Distribution of Treasury Funds Before Burn</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*FXChbzkm1rRqPnoNtkLAIA.png" /><figcaption>Distribution of Treasury Funds After Burn</figcaption></figure><h3>How will the Token Burn take place?</h3><p>Similar to the Treasury of both Polkadot and Kusama, the token burn will take place using the treasury pallet of Turing Network. To do this, the mentioned tokens need to be transferred to Turing Network’s treasury pallet wallet, 68d8VZxMCLRDPBCCT67VEBVAamG1uozgWj3bHxCTv6iZcbYN, before they can be burned.</p><p>First, we will manually transfer the mentioned amount to the treasury pallet wallet. Then, we will start a governance proposal to change the burn percentage from the current 0% to 100% and set its cadence to 7 days. This means that in 7 days, all the transferred tokens will be burned by the treasury pallet.</p><p>Please note that the remaining ecosystem funds, such as developer incentives and ecosystem growth categories, will still provide funds for the growth of the Network, as specified on the <a href="https://oak.tech/turing/token/">Turing Token Page</a>. If you are a developer or project interested in building automation functionality into your dApp, please check out the available grants on our website at the link below.</p><h3>Future Solution — Auto-Burn Feature</h3><p>Later on, we will introduce a new auto-burn mechanism to the Turing Networking. <strong>This mechanism will be implemented through our unique </strong><a href="https://docs.oak.tech/docs/time-automation-explained/"><strong>Time Automation feature</strong></a><strong>, allowing us to automate the token transfer process mentioned above on a quarterly basis.</strong></p><p>The auto-burn mechanism is designed to automatically reduce a portion of TUR tokens every quarter. The reduction will be based on the transaction volume recorded on the blockchain over the previous 90 days. The formula used for this calculation is outlined below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*cxc24B1ZmzUaEeNTKDbBZg.png" /></figure><p>Where,</p><ul><li><strong>p</strong> represents the percentage of TUR token to be burned.</li><li>Phigh and Plow are the upper and lower boundaries of p.</li><li><strong>x</strong> indicates the total on-chain transaction volume over the last 90 days.</li><li><strong>k</strong> is a manually determined factor that influences the curve of the burn rate chart.</li></ul><p>The specific values for these variables will be established prior to the activation of the auto-burn feature. However, you can refer to the diagram below for an illustrative example, where:</p><ul><li>The y-axis represents the burn ratio (e.g., 0.06 equates to 6% of the treasury).</li><li>The x-axis shows the past 90-day transaction volume (e.g., 5*10⁶ is 5 million transactions).</li><li>The k-value is set at 1,000,000.</li><li>P_high and P_low are set at 0.06 (6%) and 0.01 (1%), respectively.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*Fkgi9q4VvuZ-yq5duQUKkA.png" /><figcaption>Example graph of TUR burning ratio based on transaction volume</figcaption></figure><p>In this example, a near-zero transaction volume results in a 6% burn ratio, implying that 6% of the treasury’s tokens are burned at the quarter’s end. Conversely, with a transaction volume of 6 million, the burn rate drops to 1.8%.</p><p>The primary objective of this mechanism is to counterbalance the annual inflation of the network’s token. By aligning the burn rate with on-chain activity, we aim to regulate the token supply, ensuring it doesn’t deflate too rapidly, thus maintaining a healthy economic ecosystem within the Turing Network.</p><h3>Other Possible Solutions</h3><p>As OAK Network and the Turing Network continue to grow our team is committed to implementing and trying out new features which benefit the health of our blockchains and our community. This includes different token burning mechanisms such as token buy-back programs, which is something our team is exploring for the future.</p><h3>About OAK Network</h3><p>OAK Network is a layer one blockchain that enables multi-chain applications to automate single or recurring transactions using a simple ‘if this’ trigger condition and ‘then that’ transaction instruction. As the web3 hub for cross-chain automation, OAK unlocks a diverse range of rich DeFi user experiences including scheduled and recurring payments, stable-cost-averaging, stop loss and limit orders, and non-custodial copy trading.</p><p><a href="https://discord.gg/vmvmWFmW5p">Discord</a> | <a href="https://github.com/OAK-Foundation">Github</a> | <a href="https://link.medium.com/0rgiZXwWnsb">Medium</a> | <a href="https://t.me/OAK_Announcements">Telegram</a> | <a href="https://twitter.com/oak_network">Twitter</a> | <a href="https://oak.tech/">Website</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d3cd06e3241" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/announcing-turing-network-tur-burning-event-new-token-burning-mechanism-6d3cd06e3241">Announcing Turing Network TUR Burning Event &amp; New Token Burning Mechanism</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OAK Network Raises a $5.5M Seed Round from Foundation Capital, Greylock, and Hypersphere Ventures]]></title>
            <link>https://medium.com/avaprotocol/oak-network-raises-a-5-5m-seed-round-from-foundation-capital-greylock-and-hypersphere-ventures-6c957f1c1ab?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c957f1c1ab</guid>
            <category><![CDATA[polkadot]]></category>
            <category><![CDATA[investment]]></category>
            <category><![CDATA[parachain]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[fundraising]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Wed, 09 Feb 2022 17:18:50 GMT</pubDate>
            <atom:updated>2022-02-09T18:33:34.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A2cUJZ0S83Wykr_nhy6Aiw.png" /></figure><p><a href="https://oak.tech/">OAK Network</a>, the Web 3.0 hub for Defi and payment automation, closed a $5.5M Seed round led by <a href="https://foundationcapital.com/">Foundation Capital</a>, <a href="https://greylock.com/">Greylock</a>, and <a href="https://hypersphere.ventures/">Hypersphere Ventures</a>. Other notable participants in the funding round include <a href="https://www.electriccapital.com/">Electric Capital</a>, <a href="https://www.monday.capital/">Monday Capital</a>, <a href="https://www.gsr.io/">GSR</a>, <a href="https://shima.capital/">Shima Capital</a>, <a href="https://www.blockwall.digital/">Blockwall Digital</a>, and angel investors.</p><p>OAK Network’s innovation, <strong>the event-driven transaction</strong>, allows users to create bespoke on-chain automation not possible today. Incumbent “automation” solutions are not consumer-friendly, requiring coding knowledge, AWS servers, and private key delegation. OAK’s more powerful transaction shifts the paradigm of automation from centralized servers to the blockchain. With OAK, users are empowered to <strong>schedule future and recurring payments</strong>, engage in <strong>trustless auto-trading</strong>, and place decentralized <strong>limit and stop-loss orders on AMM DEXs</strong> all without smart contract middlemen or compromising the security of a user’s wallet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m5HJpqrXzX4KwB2J" /><figcaption>OAK’s team scaled up to 10 full-time employees in the U.S. and China.</figcaption></figure><p>The OAK Network team received <a href="https://medium.com/oak-blockchain/oak-network-wins-grant-from-web3-to-build-quadratic-funding-module-556811363f2d">an open grant from the Web3 Foundation</a> in May 2021, and won the <a href="https://medium.com/oak-blockchain/oak-network-won-the-first-prize-of-the-2nd-polkadot-hackathon-11738da61b9f">1st prize in the Polkadot hackathon</a> in July. The team has developed a working proof of concept of the event registry on top of Parity’s Substrate open source framework. OAK Network’s chains are natively compatible with Polkadot, and will be integrated with Kusama and Polkadot as parachains through crowdloan auctions. The networks and timelines are,</p><p><strong>Neumann Network, </strong>a parachain testnet that has been operating since June 2021.</p><p><strong>Turing Network, </strong>a Kusama parachain to launch in Q2 2022.</p><p><strong>OAK Network, </strong>a Polkadot parachain to launch in Q4 2022.</p><p>“The reason we chose Polkadot is because it has solved many critical problems of Ethereum. The blockchain comes with out-of-the-box solutions such as staking, DAO governance and inter-chain communication. The adoption of Polkadot will take time but technologically, many constraints have been lifted for us to develop the next generation blockchains.” says <a href="https://www.linkedin.com/in/chrisli2046/">Chris Li, co-founder and CEO</a>.</p><p>“We’re a team of utilitarian builders. We’re driven by the vision that in an increasingly decentralized world, there is a great need for automation to be seamless, trustless and secure for consumers of all generations.” — <a href="https://www.linkedin.com/in/irsal/">Irsal McGinnis, co-founder and CTO</a>.</p><p>Ultimately, OAK Network will bridge to and facilitate other major blockchains such as Bitcoin, Ethereum, and Solana. The team is actively working with academia to develop cutting-edge solutions for cross chain communication and on-chain automation privacy.</p><p>Stay tuned for further information about the OAK Network here on <a href="https://medium.com/oak-blockchain">Medium</a>, <a href="https://twitter.com/oak_network">Twitter</a> and <a href="https://www.linkedin.com/company/oak-blockchain/">LinkedIn</a>, as well as in our <a href="https://discord.gg/7W9UDvsbwh">Discord Server</a>!</p><p>Please check out our engineering and growth <a href="https://oak.tech/career">job openings</a>, contact <a href="http://partner@oak.tech/">partner@oak.tech</a> for partnerships, or <a href="http://contact@oak.tech/">contact@oak.tech</a> for any general inquiries.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c957f1c1ab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/oak-network-raises-a-5-5m-seed-round-from-foundation-capital-greylock-and-hypersphere-ventures-6c957f1c1ab">OAK Network Raises a $5.5M Seed Round from Foundation Capital, Greylock, and Hypersphere Ventures</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polkadot XCM Cross-Chain Asset Transfer Demo]]></title>
            <link>https://medium.com/avaprotocol/polkadot-xcm-cross-chain-asset-transfer-demo-53aa9a2e97a7?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/53aa9a2e97a7</guid>
            <category><![CDATA[xcm]]></category>
            <category><![CDATA[crosschain]]></category>
            <category><![CDATA[technical]]></category>
            <category><![CDATA[substrate]]></category>
            <category><![CDATA[polkadot]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 17:00:38 GMT</pubDate>
            <atom:updated>2021-09-08T17:00:38.925Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YELeZS97kbdVf7H_XJbMJQ.png" /></figure><p>Hi Polkadot &amp; Substrate developers,</p><p>This article presents a step-by-step Polkadot XCM tutorial, making a cross-chain asset transfer from a relay chain to a parachain, and vice versa, in a local environment.</p><h3>1. Prerequisite</h3><p>First, let’s set up the testing environment as following:</p><p>Rust：</p><p>nightly-2021–03–01</p><p>Relay chain code: Polkadot <a href="https://github.com/paritytech/polkadot/tree/release-v0.9.9">release-v0.9.9</a></p><p>Parachain code: Cumulus with ORML</p><p><a href="https://github.com/OAK-Foundation/cumulus/tree/orml">https://github.com/OAK-Foundation/cumulus/tree/orml</a></p><p><em>Above code in OAK Network’s repo is a modified version of Cumulus framework with additional ORML modules.</em></p><p>Polkadot.js-apps UI<br><a href="https://github.com/OAK-Foundation/apps/tree/orml">https://github.com/OAK-Foundation/apps/tree/orml</a></p><p><em>It is a modified version of polkadot.js/apps. Since we have added the ORML configuration to the blockchain, we need to resolve the type definition conflicts in the polkadot.js-apps by using aliases.</em></p><h3>2. Integrating the ORML modules</h3><p>In this section, we explain the ORML modules and the process of integrating them. We also shared the finished code in the repo below, so if you don’t want to go over the process manually you can skip this section.</p><p><a href="https://github.com/OAK-Foundation/cumulus/tree/orml">https://github.com/OAK-Foundation/cumulus/tree/orml</a></p><p><strong>About ORML modules</strong></p><p>ORML provides a comprehensive general solution for various cross-chain token transactions. You can see the original code and detailed explanations here.</p><p><a href="https://github.com/open-web3-stack/open-runtime-module-library">https://github.com/open-web3-stack/open-runtime-module-library</a></p><p>In this demo we have particularly integrated three important ORML modules into our code. They are,</p><p><strong>orml-tokens</strong>: Fungible tokens module that implements MultiCurrency trait.</p><p><strong>orml-xcm-support</strong>: Provides traits, types, and implementations to support XCM integration.</p><p><strong>orml-xtokens</strong>: Provides methods forXCM cross chain assets transfer.</p><p>Besides, we also referenced several other modules such as orml-currencies, orml-traits, orml-unknown-tokens, and applied <a href="https://github.com/AcalaNetwork/Acala/blob/master/runtime/karura/src/lib.rs">Acala’s acala-primitives</a> implementation to our code.</p><h3>3. Fix typedef conflicts in polkadot.js-apps</h3><p>Normally, in order to add a custom data we can set up the types in Settings -&gt; Developer, however, in this case there’s a conflict between the tokens.accounts storage type AccountData and the original AccountData in Substrate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KlqEXrRWuvWw_gOV" /></figure><p>We found a way to solve the problem by renaming the new AccountData in tokens.accounts to OrmlAccountData, using the typesAlias method mentioned in <a href="https://polkadot.js.org/docs/api/start/types.extend/#type-clashes">polkadot.js docs: type-crashes</a>.</p><p>As shown in the screenshot below, the type name has changed to “OrmlAccountData.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ioDrWTEuwD4w_YpB" /></figure><h3>4. Setup local environment</h3><h3>4.1 Setup the relay chain and para-chain</h3><p>The first step is to set up a relay chain and a parachain. Please refer to our previously posted tutorial on setting up the local environments .</p><p><a href="https://medium.com/oak-blockchain/tutorial-polkadot-cross-chain-message-passing-xcmp-demo-with-ping-pallet-f53397158ab4">https://medium.com/oak-blockchain/tutorial-polkadot-cross-chain-message-passing-xcmp-demo-with-ping-pallet-f53397158ab4</a></p><p>In general, the steps are:<br>1. Set up a Rococo relay chain network</p><p>2. Run the parachain collator node (running only one node is enough in this case, we are using para-id 2000 as an example)</p><p>3. Connect the parachain to the relay chain</p><h3>4.2 Start up polkadot.j-apps UI</h3><p>Run the following commands in polkadot.js/apps：</p><pre>yarn</pre><pre>yarn run start</pre><p>Relay chain portal URL：<a href="http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/extrinsics">http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9944</a></p><p>Parachain portal URL：<a href="http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/chainstate">http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9951</a></p><h3>5. Transfer asset from the relay chain to the para-chain</h3><h3>5.1 Transfer call</h3><p>Run the xcmPallet.reserveTransferAssets in the relay chain’s portal:</p><p><a href="http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/extrinsics">http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/extrinsics</a></p><p>The parameters are set as following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qpqL40zb7WnhxxE6" /></figure><p>In the screenshot the relay chain account is transferring 7 * 10¹⁵ planck（generally the smallest unit for Substrate blockchains are all planck） to the parachain account.</p><h3>4.2 Transfer Results</h3><p>You can check the tokens.account state in the parachain portal.</p><p><a href="http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/chainstate">http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/chainstate</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QnEw3HzPudYB0-Y9" /></figure><p>Please note that the token unit OAK shown in the polkadot.js UI is not proper. OAK is the default token for the para-chain. Ideally, we want the transfer result to show the source chain’s token, which in this case is DOT.</p><p>Besides, the transferred amount shown 6.999 OAK (after transaction fees deduction) is calculated based on the precision(15 digits) of the para-chain token instead of that(12 digits) of the relay chain token. Using the 12 digits precision for calculation we would get the correct result 6999 DOT.</p><h3>6. Transfer asset from the parachain to the relay chain</h3><h3>6.1 Transfer call</h3><p>First, let’s top up our operating account on para-chain with some OAKs for gas fee.</p><p>Then, run the xtokens.transfer from the para-chain portal, with below parameters.</p><p><a href="http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/extrinsics">http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/extrinsics</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OGH8uLOCGkmQ2S74" /></figure><p>In this case a para-chain account transferred 3.1 DOTs to a relay chain account, which is 3.1 * 10¹⁵ planck, using the 15 digits precision from para-chain configuration.</p><h3>5.2 Transfer Results</h3><p>Now, let’s check account balance from the relay chain’s portal</p><p><a href="http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/accounts">http://localhost:3000/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/accounts</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q9rV8Ul44QCrfzWQ" /></figure><p>As shown in the screenshot, the relay chain account has received the transfer, which is 3099.9760 UNIT after gas fee deduction, calculated using 12 digits precision.</p><p>That’s all for today’s XCM cross-chain transfer tutorial.</p><p>Please let us know if you have encountered any problem with the methods explained above, and we will try our best to answer your questions.</p><p>Stay tuned for further information about the OAK Network here on <a href="https://medium.com/oak-blockchain">Medium</a>, our <a href="https://twitter.com/oak_network">Twitter channel</a> as well as in our <a href="https://discord.gg/7W9UDvsbwh">Discord Server</a>!</p><p>Website: <a href="http://oak.tech/">http://oak.tech/</a></p><p>Email: contact@oak.tech</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53aa9a2e97a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/polkadot-xcm-cross-chain-asset-transfer-demo-53aa9a2e97a7">Polkadot XCM Cross-Chain Asset Transfer Demo</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Tutorial] Polkadot Cross-Chain Message Passing (XCMP) Demo with Ping Pallet]]></title>
            <link>https://medium.com/avaprotocol/tutorial-polkadot-cross-chain-message-passing-xcmp-demo-with-ping-pallet-f53397158ab4?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/f53397158ab4</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[substrate]]></category>
            <category><![CDATA[technical]]></category>
            <category><![CDATA[parachain]]></category>
            <category><![CDATA[polkadot-network]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Fri, 27 Aug 2021 07:15:18 GMT</pubDate>
            <atom:updated>2021-08-31T04:47:06.127Z</atom:updated>
            <content:encoded><![CDATA[<h3>[Tutorial] Polkadot Cross-Chain Message Passing (XCMP) demo with ping pallet</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ni1g9ORpCTK3LvXJIbW35w.png" /></figure><p>This article presents a demo for cross-chain function calling through Polkadot’s XCMP, with Substrate’s Ping Pallet code example.</p><p>All code mentioned in this article can be found in the OAK Network Github repo: <a href="https://github.com/OAK-Foundation/ping-workshop">https://github.com/OAK-Foundation/ping-workshop</a></p><h3>1. Overview</h3><p>In this demo, we will leverage the polkadot v0.9.8 developed by <a href="https://medium.com/u/433b0bc6fa9e">Parity Technologies</a> to create a relay chain network and two parachain networks, and call the cross-chain ping-pong function from parachain A to parachain B.</p><p>Specifically, we will create 4 command-line environments to host 2 validators for the relay chain network, and 1 validator for each parachain. 4 is the minimum number of nodes for this cross-chain ping-pong demonstration.</p><p>Below we explain the details.</p><h4>1.1 Ping-pallet in Cumulus</h4><p>Cumulus is an extension to Substrate that makes it easy to make any Substrate built runtime into a Polkadot-compatible parachain. To learn more about it, please refer to <a href="https://wiki.polkadot.network/docs/build-cumulus">Polkadot Wiki: Cumulus</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LLFWR_J3rLvsRqz2SCsDYA.png" /></figure><p>In this demo, we will refer to the ping-pallet in Cumulus code base as a dependency, but will not use other pallets in Cumulus.</p><p>Github: <a href="https://github.com/paritytech/cumulus">https://github.com/paritytech/cumulus</a></p><h4>1.2 Host 2 validators with polkadot v0.9.8</h4><p>The first step in our demo is to set up a relay chain network with 2 validator nodes. The code base is polkadot v0.9.8:</p><p><a href="https://github.com/paritytech/polkadot/tree/release-v0.9.8">https://github.com/paritytech/polkadot/tree/release-v0.9.8</a></p><h4>1.3 Host 2 parachains with substrate-parachain-template</h4><p>This template is a modified Substrate node to include dependencies required for registering the node as a parachain to an established relay chain.</p><p>After the relay chain setup, we will spin up two parachains withsubstrate-parachain-template code.</p><p>Github: <a href="https://github.com/substrate-developer-hub/substrate-parachain-template">https://github.com/substrate-developer-hub/substrate-parachain-template</a></p><h3>2. Adding the ping-pallet to parachain</h3><p>In this section we are adding the cross function code to the substrate-parachain-template, mentioned in 1.3 above.</p><h4>2.1 Add cumulus-ping dependency to runtime/Cargo.toml</h4><pre><em># Custom Dependencies<br></em>cumulus-ping = { git = &#39;https://github.com/paritytech/cumulus&#39;, branch = &#39;polkadot-v0.9.8&#39;, default-features = false }</pre><h4>2.2 Add Cumulus-Ping into runtime code</h4><h4>2.2.1 Implement cumulus-ping::config in runtime</h4><p>Here we refer to the code in rococo repository.</p><p><a href="https://github.com/paritytech/cumulus/blob/ed6ba5dfb2c112c29505e856e8971da3420ce6d0/polkadot-parachains/rococo/src/lib.rs#L393">https://github.com/paritytech/cumulus/blob/ed6ba5dfb2c112c29505e856e8971da3420ce6d0/polkadot-parachains/rococo/src/lib.rs#L393</a></p><pre>impl cumulus_ping::Config for Runtime {</pre><pre>  type Event = Event;</pre><pre>  type Origin = Origin;</pre><pre>  type Call = Call;</pre><pre>  type XcmSender = XcmRouter;</pre><pre>}</pre><h4>2.2.2 Add cumulus-ping to construct_runtime</h4><p>Here we also refer to the code in rococo repository</p><p><a href="https://github.com/paritytech/cumulus/blob/ed6ba5dfb2c112c29505e856e8971da3420ce6d0/polkadot-parachains/rococo/src/lib.rs#L459">https://github.com/paritytech/cumulus/blob/ed6ba5dfb2c112c29505e856e8971da3420ce6d0/polkadot-parachains/rococo/src/lib.rs#L459</a></p><pre>construct_runtime! {<br>    pub enum Runtime where<br>        Block = Block,<br>        NodeBlock = generic::Block&lt;Header,sp_runtime::OpaqueExtrinsic&gt;,<br>        UncheckedExtrinsic = UncheckedExtrinsic,<br>    {<br>        ....<br>        Spambot: cumulus_ping::{Pallet, Call, Storage, Event&lt;T&gt;} = 99,<br>    }<br>}</pre><p>And now the cumulus_ping pallet is included in the substrate-parachain-template.</p><h3>3. Run relay chain + 2 parachains</h3><h4>3.1 Prerequisite</h4><h4>3.1.1 Rust environment</h4><p>Run the following code to make sure you have the correct version of Rust installed.</p><pre># setup Rust nightly toolchain<br>rustup default nightly-2021-03-01<br># setup wasm toolchain<br>rustup target add wasm32-unknown-unknown --toolchain nightly-2021-03-01</pre><h4>3.1.2 Relay chain: polkadot v0.9.8</h4><p><a href="https://github.com/paritytech/polkadot/tree/release-v0.9.8">https://github.com/paritytech/polkadot/tree/release-v0.9.8</a></p><h4>3.1.3 Parachain：</h4><p>Here we use the code base in OAK Network’s ping-workshop repo.</p><p><a href="https://github.com/OAK-Foundation/ping-workshop">https://github.com/OAK-Foundation/ping-workshop</a></p><p>The ping-workshop is based on <a href="https://github.com/substrate-developer-hub/substrate-parachain-template/commit/9b41b90fa241ea36563bf1f5cefca0bdd2543c26">the most recent release</a> of substrate-parachain-template, which is compatible with Polkadot v0.9.8.</p><h4>3.2 Compile and run the relay chain</h4><h4>3.2.1 Compile the relay chain code</h4><pre>git clone -b release-v0.9.8 <a href="https://github.com/paritytech/polkadot">https://github.com/paritytech/polkadot</a><br>cd polkadot<br>cargo build --release</pre><h4>3.2.2 Generate config</h4><pre>./target/release/polkadot build-spec <em>--chain=rococo-local --disable-default-bootnode --raw &gt; rococo-local.json</em></pre><h4>3.2.3 Run the code</h4><pre><em># First node<br></em>./target/release/polkadot <em>--name alice --chain rococo-local --alice -d ./data/alice --ws-external --rpc-external --rpc-cors all  --node-key 0000000000000000000000000000000000000000000000000000000000000001</em></pre><pre><em>#Second Node<br></em>./target/release/polkadot <em>--name bob --chain rococo-local --bob -d ./data/bob --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp</em></pre><p>Check the following tutorial for details on starting a network.</p><p>​​<a href="https://substrate.dev/docs/en/tutorials/start-a-private-network/alicebob">https://substrate.dev/docs/en/tutorials/start-a-private-network/alicebob</a></p><p>So far we have launched two nodes and formed the relay chain network.</p><h4>3.3 Compile and run the parachains</h4><h4>3.3.1 Compile the code</h4><pre>git clone <a href="https://github.com/imstar15/ping-workshop">https://github.com/imstar15/ping-workshop</a><br>cd ping-workshop<br>cargo build --release</pre><h4>3.3.2 Generate genesis state &amp; wasm</h4><p>We are giving the two parachain IDs 2000 and 2001. The genesis wasm file is the same for the 2 parachains, but each needs a separate genesis state file.</p><pre><em># Export genesis wasm<br></em>./target/release/parachain-collator export-genesis-wasm &gt; genesis-wasm<br><em># Export genesis-state-2000<br></em>./target/release/parachain-collator export-genesis-state <em>--parachain-id 2000 &gt; genesis-state-2000<br># Export genesis-state-2001<br></em>./target/release/parachain-collator export-genesis-state <em>--parachain-id 2001 &gt; genesis-state-2001</em></pre><h4>3.3.3 Run the parachains</h4><pre>// First chain<br>RUST_LOG=runtime=debug ./target/release/parachain-collator -d ./data/alice <em>--collator --alice --force-authoring --port 40557 --ws-port 9951 --parachain-id 2000 --ws-external --rpc-cors all --rpc-methods=unsafe -- --execution wasm --chain ../polkadot/rococo-local.json --port 40558 --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp</em></pre><pre>// Second chain<br>RUST_LOG=runtime=debug ./target/release/parachain-collator -d ./data/bob <em>--collator --bob --force-authoring --port 40777 --ws-port 9971 --parachain-id 2001 --ws-external --rpc-cors all --rpc-methods=unsafe -- --execution wasm --chain ../polkadot/rococo-local.json --port 40778 --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp</em></pre><p>For more details about the parachain-collator program, use the help command to check out the examples.</p><pre>./target/release/parachain-collator <em>--help</em></pre><h4>3.3.4 Connect the parachains to the relay chain</h4><p>In this step, we will need to use polkadot.js/apps website to send request to the chains. Use sudo access to submit the registration information of the two parachains to <strong><em>araSudoWrapper.sudoScheduleParaInitialize</em></strong>.</p><p>As mentioned above, the para-ids are 2000 and 2001.</p><p>Navigate to polkadot.js/apps website with a local rpc target.</p><p><a href="https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/sudo">https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/sudo</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqEKX3D9VJo8dTbu1uMaIQ.png" /></figure><p>Under the Network tab you should be able to see the 2 parachains registered on the relay chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C4BLucnBFGRF5lKg" /></figure><p>And here you can see the parachain’s blocks are finalized, indicating that the Parachains are successfully connected to the relay chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iFd3rZD-rV4fdYpC" /></figure><h3>4. Build HRMP channels and call the cross-chain function</h3><p><a href="https://wiki.polkadot.network/docs/learn-crosschain#xcmp-lite-hrmp">XCMP-light(HRMP)</a> is an alternative messaging channel to the XCMP which has the same interface. It’s the current implementation of a messaging channel.</p><h4>4.1 Call the cross-chain function</h4><p>First, let’s try to call the cross-chain function. In this case, it’s <strong><em>spambot.start</em></strong> which sends a ping message from parachain 2000 to parachain 2001</p><p>Navigate to the Developer tab of polkadot.js/apps</p><p><a href="https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/sudo">https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/sudo</a></p><p>Execute spambot.start with below parameters,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXslubogeOiamBLE19qSTA.png" /></figure><p>However, all we received is an error, ErrorSendingPing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jo9M4i4ba_rZ8yNboHbnRQ.png" /></figure><p>After debugging we found the root cause of that error, as seen in below code.</p><p><a href="https://github.com/paritytech/cumulus/blob/ed6ba5dfb2c112c29505e856e8971da3420ce6d0/pallets/parachain-system/src/lib.rs#L675">https://github.com/paritytech/cumulus/blob/ed6ba5dfb2c112c29505e856e8971da3420ce6d0/pallets/parachain-system/src/lib.rs#L675</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YxJroZsFHemUmToS" /></figure><p>In this get_channel_max, the number of channels is 0. Therefore, the binary_search_by_key fails to execute. The cross chain messaging channel is not yet established.</p><h4>4.2 Build the HRMP channel</h4><p>Now we execute <strong><em>paraSudoWrapper.sudoEstabllishHrmpChannel</em></strong> to build the messaging channel between 2000 and 2001. We also need to repeat the process for the channel from 2001 to 2000.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3YDqftakMDueILkcy2Unvw.png" /></figure><p>After the channel setup, we repeat the <strong><em>spambot.start</em></strong> function in 4.1, and now we see the spambot.PingSent and spambot.Ponged events shown in recent blocks, indicating that the ping function is successfully called cross-chain.</p><p><a href="https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/explorer">https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9951#/explorer</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*f9hvIxlQf9kLpjg6Ts4GvA.png" /></figure><h3>5. Analyze the code</h3><p>As mentioned in 1., the code of ping function is from cumulus-ping pallet.</p><p><a href="https://github.com/paritytech/cumulus/blob/polkadot-v0.9.8/polkadot-parachains/pallets/ping/src/lib.rs">https://github.com/paritytech/cumulus/blob/polkadot-v0.9.8/polkadot-parachains/pallets/ping/src/lib.rs</a></p><h4>5.1 The Start function</h4><p>Use this code to start</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JMgAYyET6L9Qdiz7" /></figure><h4>5.2 on_finalize function</h4><p>The code defines a hook that when the block is finalized, the start method will send the requested message out to the destination chain with a ping message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JV0Eljo2VFB05qMX" /></figure><h4>5.3 The ping function</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X2VU3ubgO68teR78" /></figure><p>When ping is executed, it will reply with a XCMP, calling pong function; therefore, it completes a round-trip for ping-pong.</p><h3>6. Cross-chain message filtering</h3><p>One important thing to note in above implementation is that a cross-chain message needs to be whitelisted in the receiver end to be accepted. The whitelisting happens in a place called the Barrier.</p><p>Without the whitelisting, the receiving chain will encounter an <strong><em>XcmError.Barrier</em></strong> error, as shown in below screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/0*TXveHXo6jf3Xb2p4" /></figure><p>Let’s take a look at the Barrier setup below.</p><p>In runtime/src/lib.rs</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gPftzyVkYNo2hhyl" /></figure><p>It shows <em>pub type Barrier = (….), w</em>here it defines 4 Barrier, and each has a message filter criteria.</p><p><a href="https://github.com/paritytech/polkadot/blob/3a10ee63c0b5703a1c802db3438ab7e01344a8ce/xcm/xcm-builder/src/barriers.rs#L69">https://github.com/paritytech/polkadot/blob/3a10ee63c0b5703a1c802db3438ab7e01344a8ce/xcm/xcm-builder/src/barriers.rs#L69</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pyLk7kb61Cseatx3" /></figure><p>For example, the <strong><em>AllowUnpaidExecutionFrom</em></strong> Barrier limits the origin to be within a range,</p><ul><li>AllowUnpaidExecutionFrom&lt;ParentOrParentsUnitPlurality&gt;: only messages from the relay chain council will be executed.</li><li>AllowUnpaidExecutionFrom&lt;All&lt;MultiLocation&gt;&gt;: accept all messages origins</li><li>AllowUnpaidExecutionFrom&lt;SpecParachain&gt;: parachain 2000 and 2001 can only execute messages from each other</li></ul><pre>match_type! {<br>    pub type SpecParachain: impl Contains&lt;MultiLocation&gt; = {<br>        X2(Parent, Parachain(2000)) | X2(Parent, Parachain(2001))<br>    };<br>}</pre><p>That’s all for today’s tutorial. Hope you grasp the idea of Polkadot cross-chain function calling from our article. The parachain code is based off of substrate-parachain-template and ready in the OAK Network Github:</p><p><a href="https://github.com/OAK-Foundation/ping-workshop">https://github.com/OAK-Foundation/ping-workshop</a></p><p>Stay tuned for further information about the OAK Network here on <a href="https://medium.com/oak-blockchain">Medium</a>, our <a href="https://twitter.com/oak_network">Twitter channel</a> as well as in our <a href="https://discord.gg/7W9UDvsbwh">Discord Server</a>!</p><p>Website: <a href="http://oak.tech/">https://oak.tech/</a></p><p>Email: contact@oak.tech</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f53397158ab4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/tutorial-polkadot-cross-chain-message-passing-xcmp-demo-with-ping-pallet-f53397158ab4">[Tutorial] Polkadot Cross-Chain Message Passing (XCMP) Demo with Ping Pallet</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Tutorial] Become a Validator node in OAK Network Testnet]]></title>
            <link>https://medium.com/avaprotocol/tutorial-become-a-validator-node-in-oak-network-testnet-cf6ebb3f34cf?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf6ebb3f34cf</guid>
            <category><![CDATA[parity-substrate]]></category>
            <category><![CDATA[polkadot-network]]></category>
            <category><![CDATA[validator]]></category>
            <category><![CDATA[technical]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Mon, 16 Aug 2021 03:47:35 GMT</pubDate>
            <atom:updated>2021-11-05T05:14:18.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pEF5kzAZkJDobfWqJSGHrg.png" /></figure><p>Hi OAK community members,</p><p>We are proud to present the OAK Testnet to the developer community. Please note that at this stage the Testnet Validator application is only open to developers for testing purposes, and we will open up the validator staking after the launch of the mainnet.</p><p>In order to enhance the product’s user experience and to improve on-chain security, OAK team launched the first Bug Bounty program with potential payouts of $2,500. Check out <a href="https://medium.com/oak-blockchain/oak-network-launches-bug-bounty-program-451fc206100a">the program here</a>.</p><h3>1. Setup OAK Testnet Validator Node</h3><h4>1.1 Environment</h4><p>Make sure a Docker engine is correctly installed on your server.</p><h4>1.2 Run the flowing code to Start Node</h4><pre>docker pull oaknetwork/oak_testnet:latest &amp; docker run -d --name &lt;container_name&gt; oaknetwork/oak_testnet:latest --name &lt;node_name&gt;</pre><p>Example:</p><pre>docker pull oaknetwork/oak_testnet:latest &amp; docker run -d --name node001 oaknetwork/oak_testnet:latest --name david</pre><p><strong>1.3 Check Node Operating Log</strong></p><pre>docker logs -f --tail=200 &lt;container_name&gt;</pre><p>Example:</p><pre>docker logs -f --tail=200 node001</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n8_ky7Tn6uKTc_m3" /></figure><pre>Syncing, target=#287414 (1 peers), best: #2164 (0x2e46…fe34), finalized #2048 (0x9d90…8a48), ⬇ 142.9kiB/s ⬆ 1.9kiB/s</pre><p>The above message indicates that on-chain election is complete.</p><h3>2. Become a Validator</h3><h4>2.1 Run the Node</h4><p>Create a new Docker container with the latest image <strong>oaknetwork/oak_testnet:latest</strong>. Note that the <strong>~/oak-testnet/data</strong> path in the below command is the path in your persistent storage for node data, which will not be deleted when the Docker container is removed.</p><pre>docker run -d --name &lt;container_name&gt; -v ~/oak-testnet/data:/app/data -p 30333:30333 oaknetwork/oak_testnet:latest --name &lt;validator_name&gt; --validator</pre><h4>2.2 Get Rotate Keys</h4><p>Retrieve a RotateKey from the node via cURL:</p><pre>docker exec -it &lt;container_name&gt; curl -H &quot;Content-Type: application/json&quot; -d&#39;{&quot;id&quot;:1, &quot;jsonrpc&quot;:&quot;2.0&quot;, &quot;method&quot;: &quot;author_rotateKeys&quot;, &quot;params&quot;:[ ]}&#39; <a href="http://localhost:9933/">http://localhost:9933</a></pre><p>Save the Rotate keys, for example:</p><pre>0xd63605b333d1a706bddfa0c79e930fbcb3db786d59181289b19d698e4c8f7b5ca2b5e55a59fa94bf0a147a4aa697c9ff90ed075923bf17d7c80ca1daccb2c31e10cb1cc74a53f5ce5fb048ac12e2d0c8d74eed658ba85dc6788e67077b5e871ad8dbf6d47a1233dd40d3b17ce6c130c274a3f83779105416c8e3e1c929f62618</pre><h3>2.3 Become a Validator</h3><p>Click the link：</p><p><a href="https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.testnet.oak.tech#/staking/actions">https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.testnet.oak.tech#/staking/actions</a></p><p>Click the Validator button:</p><p>Set up Validator 1/2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bwMeYdVGkmRgfHLE" /></figure><p>Fill in the information:</p><p><strong>Stash Account/Controller Account</strong></p><p>The Stash account is meant to stay in cold storage, while the Controller account makes day-to-day transactions like setting session keys or deciding which validators to nominate. The Stash account still needs to make some transactions, though, like bonding extra funds or designating a new Controller.</p><p><strong>Place Funds at Stake</strong></p><p>To become a Validator you need to lock away the minimum threshold stake. This is done using a bonding transaction which places an amount of OAK tokens into the staking system. Please note that you will need to leave a minimum amount as transaction fees.</p><p><strong>Choose the Destination Account</strong></p><p>Here you can specify the account where you wish to receive staking rewards.</p><p>Click <em>Next</em> to complete the form</p><p>Set up Validator 2/2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JvB1unyP0xWcGwQk" /></figure><p><strong>Fill in Rotate Keys</strong></p><p>Fill in the Rotate Ket generated earlier.</p><p><strong>Setup Commission Rate</strong></p><p>For example, 20% to validator and 80% to be assigned by the nominator.</p><p><strong>Allows New Nominations</strong></p><p>Choose if the validator allows new nominations.</p><p>With the submission, you’ll see your account in the stashes list.​​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mEyrEPd1kzx7Os-u" /></figure><p>Meanwhile, your account will show up in the waiting list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TICxNHPNG6E3-RaA" /></figure><p>After an era, your account should show up in the Validator list.</p><p>In OAK Testnet an era is one hour.</p><p>We accept limited validators, the first 6 nodes will be the validator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q7vxc0iGat1R4YL_" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T5JtFhFIzOtAApJb" /></figure><p>Congratulations, you are all set as a validator in OAK Testnet. If you encounter people and problems during this process, please contact the developers of OAK Network in <a href="https://discord.com/invite/7W9UDvsbwh">Discord Server</a>.</p><p>Stay tuned for further information about the OAK Network here on <a href="https://medium.com/oak-blockchain">Medium</a>, our <a href="https://twitter.com/oak_network">Twitter channel</a> as well as in our <a href="https://discord.gg/7W9UDvsbwh">Discord Server</a>!</p><p>Website: <a href="http://oak.tech/">https://oak.tech/</a></p><p>Email: contact@oak.tech</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf6ebb3f34cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/tutorial-become-a-validator-node-in-oak-network-testnet-cf6ebb3f34cf">[Tutorial] Become a Validator node in OAK Network Testnet</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User tutorial of OAK’s hackathon winning Quadratic Funding dApp]]></title>
            <link>https://medium.com/avaprotocol/user-tutorial-of-oaks-hackathon-winning-quadratic-funding-dapp-f484fe6a506f?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/f484fe6a506f</guid>
            <category><![CDATA[parity-substrate]]></category>
            <category><![CDATA[technical]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[polkadot-network]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Sun, 08 Aug 2021 23:59:28 GMT</pubDate>
            <atom:updated>2021-08-09T00:00:08.521Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey OAK community members,</p><p>As mentioned in our last article, <a href="https://medium.com/oak-blockchain/oak-network-won-the-first-prize-of-the-2nd-polkadot-hackathon-11738da61b9f">OAK Network won the 1st prize of the Polkadot hackathon in July</a>.</p><p>Today we are going to walk you through our hackathon project, a web application for <a href="https://medium.com/oak-blockchain/oak-network-wins-grant-from-web3-to-build-quadratic-funding-module-556811363f2d">the Quadratic Funding pallet sponsored by Web3 Foundation Open Grant</a>.</p><p>Basically, the web dApp provides a neat user interface for developers to easily create grant submission, and for users to view the ongoing and the past grants, as well as to participate by donating OAK token.</p><p>Our marketing manager Leah has created a Youtube video for the user walk-through below.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTVAlt8BexIw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTVAlt8BexIw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTVAlt8BexIw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/418eb76a027c29fdc430c3c8b4f2cbb7/href">https://medium.com/media/418eb76a027c29fdc430c3c8b4f2cbb7/href</a></iframe><h4>1. Background of the project</h4><p>For a detailed explanation of Quadratic Funding, please refer to:</p><p><a href="https://medium.com/oak-blockchain/oak-network-wins-grant-from-web3-to-build-quadratic-funding-module-556811363f2d?source=collection_detail----d77fffb18e43-----6-----------------------">OAK Network won the Web3 Fund to establish a quadratic voting module</a></p><p>For developer tutorial of the Quadratic Funding pallet, please check out:</p><p><a href="https://medium.com/oak-blockchain/tutorial-developer-walk-through-for-polkadot-quadratic-funding-pallet-649927aa1e63">[Tutorial]Developer walk-through for Polkadot quadratic funding palle</a>t</p><p>Quadratic Fuding dApp demo URL:<br><a href="https://polkagrant.com/">https://polkagrant.com/</a></p><h4>2. Product walk-through</h4><p>First, please go to <a href="https://polkagrant.com/">https://polkagrant.com/</a> in your browser for the demo website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6Jj-IzteUiqRT0SoBRqhQ.png" /><figcaption>The landing page of the demo website <a href="https://polkagrant.com/">https://polkagrant.com</a></figcaption></figure><p>Click “Connect a Wallet” at the top right corner to read wallets from the polkadot{.js} extension. For how to create a wallet, please refer to the article below:</p><p><a href="https://medium.com/oak-blockchain/tutorial-get-oak-test-tokens-with-polkadot-js-extension-3d3be8aff4d5">[Tutorial] Get OAK test tokens with Polkadot.js extension</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Ki7jGvIJVjVHCKeD6ZHeQ.png" /><figcaption>The wallet selection pop-up modal</figcaption></figure><p>After selecting a wallet address, the “Connect a Wallet” button is now replaced by the wallet address. Clicking on the address will allow you to re-select a wallet.</p><p>Now, as the below screenshot shown you can choose the past and the current campaigns of the Quadratic Funding. Each campaign lasts for a month and usually will have 6–8 grants in one round.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oiJSUGUX09dM7ZWsR5bjwQ.png" /><figcaption>Selecting different campaign using the dropdown button</figcaption></figure><p>Clicking on a project from the list leads to the Project Detail page, where users can get information about the project such as description, creator, created datetime, voting received, matched funds, and etc.</p><p>Now we’re going to show you how to participate in the funding. First, users need to enter the number of tokens in the input box, and the frontend calculation will show an estimate of the matching funds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vp572lkYIwZcn1pV4pjKlA.png" /><figcaption>The top half of the Project Detail page</figcaption></figure><p>After confirming the number of tokens and the matching funds, click on the “Participate” button. Once clicked, a Polkadot.js extension window will show up to ask for confirmation, and signing password. Once signed, the pop-ups on the top right corner will notify user about the pending state, and the confirmation of the outgoing transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*-KTohGSgEd0fysEz7qvKYg.png" /><figcaption>The Polkadot.js pop-up asking for confirmation and the signature</figcaption></figure><p>Besides, the Project Detail page also shows the project’s creator, social media links, participation history, and team members.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Og85D9b47z-HVrPC9SdTYQ.png" /><figcaption>Bottom half of the Project Detail page showing Social Media, history, and team members</figcaption></figure><p>At the bottom of the page, users can also check the messages left by all users, contributors of the project, and relevant transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oXwFg5xdvDt2Z5TipMV-IA.png" /><figcaption>Comments, Contributors and Transactions at the bottom</figcaption></figure><h4>3. Create a Quadratic Funding grant</h4><p>Now let us return to the polkagrant.com landing page to create a grant for our own project. Click on “Create a Grant” in the top nav menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qmSYFJuQr3QFZBq4jRcuzQ.png" /><figcaption>Click on “Create a Grant” button on the top</figcaption></figure><p>Now we are navigated to the application form for the Quadratic Funding grant. Fill in your project information based on the questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*jmOV2U_AlRZEjuC5ytUVbw.png" /><figcaption>The first question of the Quadratic Funding questionaire</figcaption></figure><p><strong>Project Name<br></strong>The name of your project</p><p><strong>Project Description<br></strong>The long text description of your project</p><p><strong>Project Website<br></strong>The website URL, if there’s any</p><p><strong>Team Members<br></strong>Team members of the projecct</p><p><strong>Twitter Handle<br></strong>The project’s official Twitter handle</p><p><strong>Github URL<br></strong>The official GitHub URL of the project</p><p><strong>Region <br></strong>Select the area of the team</p><p><strong>External Funding Information<br></strong>Explain the current funding situation of the project</p><p><strong>Pick a category<br></strong>Infrastructure, utility, blockchain, smart contract or anything else</p><p>If you have followed through, congratulations! So far you have created a Quadratic Funding grant for your project. Share it with your coworker and friends. A great journey awaits!</p><p>Thanks for reading!</p><p>Stay tuned for further information about the OAK Network here on <a href="https://medium.com/oak-blockchain">Medium</a>, our <a href="https://twitter.com/oak_network">Twitter channel</a> as well as in our <a href="https://discord.gg/7W9UDvsbwh">Discord Server</a>!</p><p>Website: <a href="http://oak.tech/">http://oak.tech/</a></p><p>Email: contact@oak.tech</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f484fe6a506f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/user-tutorial-of-oaks-hackathon-winning-quadratic-funding-dapp-f484fe6a506f">User tutorial of OAK’s hackathon winning Quadratic Funding dApp</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Tutorial] Deploy a Substrate NPoS network in 3 minutes]]></title>
            <link>https://medium.com/avaprotocol/tutorial-deploy-a-substrate-npos-network-in-3-minutes-fab9de5c4c2b?source=rss-9dd0c8ef9484------2</link>
            <guid isPermaLink="false">https://medium.com/p/fab9de5c4c2b</guid>
            <category><![CDATA[polkadot-network]]></category>
            <category><![CDATA[technical]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3-foundation]]></category>
            <category><![CDATA[parity-substrate]]></category>
            <dc:creator><![CDATA[Chris Li]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 01:30:37 GMT</pubDate>
            <atom:updated>2021-08-31T05:11:04.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Hx0VadNwaKnoFxEZXUMHA.png" /></figure><p>Hi Polkadot developers:</p><p>In this article, we are going to explain how to set up a mining network like Polkadot based on Substrate template. Through this article, you will learn:</p><ul><li>Summary of Kusama/Polkadot launch procedure</li><li>What is a NPoS (Nominated Proof of Stake) network? The difference between NPoS and PoA; and why do we need an NPoS network for mining(staking)?</li><li>How to quickly configure the NPoS network based on the <a href="https://github.com/OAK-Foundation/substrate-simple-template">substrate-simple-template</a> we created;</li></ul><h3>1. Summary of Polkadot launch procedure</h3><p>In order to ensure the launch of network smooth, the Kusama and Polkadot network had adopted a phase-by-phase method with the following steps:</p><ol><li>Launch a network with PoA consensus</li><li>Switch the consensus from PoA to PoS</li><li>Enable the democracy module</li><li>Remove sudo permissions</li><li>Enable transfer and other modules</li></ol><p>Generally speaking, in order to launch a network, developers should follow the same procedure, switching to PoS consensus only when the PoA network runs smooth and solid.</p><h3>2. Comparison of Consensus</h3><h4><strong>2.1 PoA</strong></h4><p>PoA stands for <a href="https://en.wikipedia.org/wiki/Proof_of_authority">Proof of Authority</a>, coined by Gavin Wood, co-founder of <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a> and <a href="https://medium.com/u/433b0bc6fa9e">Parity Technologies</a>. Validators are approved accounts recording transactions in blocks and receiving rewards and transaction fees in return.</p><p>In the Substrate official <a href="https://github.com/substrate-developer-hub/substrate-node-template">substrate-node-template</a> repo, a consensus module called Aura is used to implement PoA, which generates blocks with a set of pre-determined authority accounts.</p><p>The Aura module is quick and easy for setup, and less error-prone, but the downside is that other people cannot easily participate in mining.</p><h4><strong>2.2 NPoS</strong></h4><p>NPoS stands for Nominated Proof of Stake. Let’s take Polkadot network as an example to explain the mining process, which is usually referred to as staking.</p><p>The mechanism is designed with two kinds of participants, validators and nominators. Participants interested in maining the network can run a node as validator, and nominators can parcipate by backing up trusted validator candidates with their DOTs. Both get rewarded by the network.</p><p>In Substrate, the NPoS consensus requires BABE (Blind Assignment for Blockchain Extension) module. For detailed information about BABE please check out <a href="https://substrate.dev/docs/en/knowledgebase/advanced/consensus#babe">Substrate.dev page</a>.</p><p>Unlike PoA, NPoS consensus allows DOT holders to participate in mining.</p><h4><strong>2.3 Ways to launch a NPoS network</strong></h4><p>Since the official Substrate node template uses PoA, there are two ways for a developer to implement the NPoS consensus in Substrate.</p><p>a) Quick Start: use the <a href="https://github.com/OAK-Foundation/substrate-simple-template">simple Substrate node template</a> we prepared in Github, which includes all Substrate default modules, plus the NPoS consensus composed of BABE and GRANDPA modules;</p><p>b) Custom and Complex: based on the PoA Substrate node template, manually add BABE module, staking configuration, and a few other related modules.</p><p>For the b), there’s a detailed tutorial “<a href="https://zhuanlan.zhihu.com/p/161293660">Substrate deployment of public test network</a>” written by Kaichao from Parity. (Unfortunately there’s only a Chinese version.</p><h3>3. Configure and launch the NPoS network</h3><h4><strong>3.1 Introduction to substrate-simple-template</strong></h4><p>The <a href="https://github.com/OAK-Foundation/substrate-simple-template">substrate-simple-template</a> is a code template based on Substrate, that helps developers quickly launch a NPoS network.</p><p>Note that since we don’t want to maintain code of each individual pallet, the pallets in this template references those in the official Substrate node template. Therefore, when there’s a new version of any pallet, you can simply bump the version number in the Cargo.toml of the corresponding pallet.</p><p>We have documented the configuration and startup procedures in<a href="https://github.com/OAK-Foundation/substrate-simple-template/blob/main/README.md"> the REAME.md file in the repo</a>.</p><h4><strong>3.2 Quick Start</strong></h4><p><strong>3.2.1 Download the source code</strong></p><p>git clone <a href="/service/mailto:git@github.com">git@github.com</a>:OAK-Foundation/substrate-simple-template.git</p><p><strong>3.2.2 Install Rust and required components</strong></p><p>Follow the steps linked below to install the required libraries.</p><p><a href="https://github.com/substrate-developer-hub/substrate-node-template/blob/master/docs/rust-setup.md">https://github.com/substrate-developer-hub/substrate-node-template/blob/master/docs/rust-setup.md</a></p><p><strong>3.2.3 Configure Rust toolchain</strong></p><p>Note that the latest nightly version of Rust should work. You can change the below nightly version in the command-line to the latest.</p><pre>rustup default nightly-2021-03-01<br>rustup target add wasm32-unknown-unknown --toolchain nightly-2021-03-01</pre><p><strong>3.2.4 Compile the code</strong></p><pre>cargo build --release</pre><p><strong>3.3 Spin up multiple nodes</strong></p><p><strong>3.3.1 Set the validator’s session keys</strong></p><p>Run the following command to generate 3 validator session public keys. Note that the 12-keyword should only be used for local development and not anywhere else.</p><pre>SECRET=&quot;panda dose welcome ostrich brief pull lawn table arrest worth ranch faculty&quot; sh scripts/prepare-test-net.sh 3</pre><p>The output should be as below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*ltM6n7Rxv0xQAtMpfI62Ww.jpeg" /></figure><p>Replace the keys with vec![…] in node/cli/src/chain_spec.rs with above generated keys.</p><pre>fn staging_testnet_config_genesis() -&gt; GenesisConfig {<br>let initial_authorities: Vec&lt;(AccountId, AccountId, GrandpaId, BabeId, ImOnlineId, AuthorityDiscoveryId)&gt; = vec![...];<br>#--snip--<br>}</pre><p><strong>3.3.2 Generate a chain configuration file</strong></p><pre>// compile<br>cargo build --release</pre><pre>// Generate configuration file<br>./target/release/substrate build-spec --disable-default-bootnode --chain staging &gt; customSpec.json</pre><p>The generated file includes the configuration for startup nodes, the genesisi block, and etc.</p><p><strong>3.3.3 Configure the startup node</strong></p><p>Generate the startup node’s public key with below command. Note that the 12-keyword should only be used for local development and not anywhere else.</p><pre>subkey inspect --scheme ed25519 &quot;fire penalty pony chase gift loan grid mule tape wrestle stuff salute&quot;</pre><p>The output should look like,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*k-PqQfRIaUA-Nn1_4hJ0AQ.jpeg" /></figure><p>Start the node with the generated public key</p><pre>./target/release/substrate --tmp --dev --node-key 0x74a8cfbadb5d2b0178ec124791bfa8346ac3550a4f689923c806428090055277</pre><p>The output should look like,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*ZjONUUdxnebRDtNqP4xk2w.jpeg" /></figure><p>Save the highlighted node identity “12D3Koo….” from the the screenshot.</p><p>Change “BootNodes”: [] section to below string in customSpec.json.</p><pre>[&quot;/ip4/127.0.0.1/tcp/30333/p2p/12D3KooWRm651Kd5GmsLTHJbgX5chQS5npx9ttLgo46UsegCMoNM&quot;]</pre><p><strong>3.3.4 Configure sudo account</strong></p><p>Now we generate a public key for the sudo account with below command. The 12-keyword should only be used for local development and not anywhere else.</p><pre>subkey inspect --scheme sr25519 &quot;royal novel glad piece waste napkin little pioneer decline fancy train sell&quot;</pre><p>The output should look like below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*nRO71Z4LN77g5e0bXL9Vww.jpeg" /></figure><p>Find palletSudo key in the customSpec.json and change it to,</p><pre>&quot;palletSudo&quot;: {<br>　　&quot;key&quot;: &quot;5Fk6QsYKvDXxdXumGdHnNQ7V7FziREy6qn8WjDLEWF8WsbU3&quot;<br>},</pre><p>Run the build command to re-compile.</p><pre>cargo build --release</pre><p><strong>3.3.5 Generate a network config file from the customSpec.json</strong></p><pre>// Generate testnet.json<br>./target/release/substrate build-spec --disable-default-bootnode --chain customSpec.json &gt; node/cli/res/testnet.json</pre><pre>// recompile<br>cargo build --release</pre><p><strong>3.3.6 Start 3 validator nodes</strong></p><pre>// First validator node<br>./target/release/substrate --chain testnet -d data/validator1 --name validator1 --in-peers 256 --validator --ws-external --rpc-external --rpc-cors all --rpc-methods=unsafe --node-key 0x74a8cfbadb5d2b0178ec124791bfa8346ac3550a4f689923c80642809005527</pre><pre>// Second validator node 2<br>./target/release/substrate --chain testnet -d data/validator2 --name validator2 --validator --port 30334 --ws-port 9946 --rpc-port 9934 --ws-external --rpc-external --rpc-cors all --rpc-methods=unsafe</pre><pre>//Third validator node<br>./target/release/substrate --chain staging -d data/validator3 --name validator3 --validator --port 30335 --ws-port 9947 --rpc-port 9935 --ws-external --rpc-external --rpc-cors all --rpc-methods=unsafe</pre><p><strong>3.3.7 Set the node’s session keys</strong><br>Run the command to set the node’s session keys</p><pre>cd scripts/session_keys<br>sh run.sh</pre><p>Restart the node with the commands in chapter 3.3.6, you can see that blocks are being finalized.</p><pre>2021-06-11 09:40:45  ✨ Imported #3 (0xf18c…97f0)<br>2021-06-11 09:40:48  ✨ Imported #4 (0x4bdc…aa87)<br>2021-06-11 09:40:48  💤 Idle (2 peers), best: #4 (0x4bdc…aa87), finalized #1 (0xad8e…f0aa), ⬇ 5.0kiB/s ⬆ 4.8kiB/s<br>2021-06-11 09:40:51  ✨ Imported #5 (0x4064…6d67)<br>2021-06-11 09:40:53  💤 Idle (2 peers), best: #5 (0x4064…6d67), finalized #3 (0xf18c…97f0), ⬇ 2.5kiB/s ⬆ 2.2kiB/s</pre><p>Once all three nodes producing blocks smoothly you have completed the tutorial and set up a network for staking!</p><p>Thanks for reading through the article dear friends. If you think it is helpful, please give us a thumb-up below!</p><h3>3. References</h3><ul><li><a href="https://zhuanlan.zhihu.com/p/161293660">How does Polkadot’s NPoS mechanism work?</a></li><li><a href="https://substrate.dev/docs/en/knowledgebase/getting-started/">Substrate.dev Knowledge Base</a></li><li><a href="https://github.com/substrate-developer-hub/substrate-node-template">Substrate node template repo on Github</a></li></ul><p>Stay tuned for further information about the OAK Network here on <a href="https://medium.com/oak-blockchain">Medium</a>, our <a href="https://twitter.com/oak_network">Twitter channel</a> as well as in our <a href="https://discord.gg/7W9UDvsbwh">Discord Server</a>!</p><p>Website: <a href="http://oak.tech/">http://oak.tech/</a></p><p>Email: contact@oak.tech</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fab9de5c4c2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avaprotocol/tutorial-deploy-a-substrate-npos-network-in-3-minutes-fab9de5c4c2b">[Tutorial] Deploy a Substrate NPoS network in 3 minutes</a> was originally published in <a href="https://medium.com/avaprotocol">Ava Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>