<?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 McTrick on Medium]]></title>
        <description><![CDATA[Stories by McTrick on Medium]]></description>
        <link>https://medium.com/@mctrick?source=rss-3c01d6941267------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6iaPZuIiCDdexJ1jPAtIMA.jpeg</url>
            <title>Stories by McTrick on Medium</title>
            <link>https://medium.com/@mctrick?source=rss-3c01d6941267------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:00:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mctrick/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[Aleo Mainnet Final Leap: Aleo Testnet Recap]]></title>
            <link>https://mctrick.medium.com/aleo-mainnet-final-leap-aleo-testnet-recap-1a2d8e6c61da?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a2d8e6c61da</guid>
            <category><![CDATA[zero-knowledge-proofs]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[aleo]]></category>
            <category><![CDATA[testnet]]></category>
            <category><![CDATA[mainnet]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Sun, 10 Mar 2024 19:23:56 GMT</pubDate>
            <atom:updated>2024-03-10T19:23:56.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_EJ33EbYg_mDcpejbcA8A.png" /></figure><h3>Table of Contents</h3><ol><li><em>Introduction</em></li><li><em>Aleo Testnet Statistics</em></li><li><em>Aleo GitHub Statistics</em></li><li><em>What a journey!</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pxHIfAp3t22v8ViCu-mV4A.png" /></figure><p>Aleo mainnet will be released in the near future, and it is clear that all attention is currently attracted to it. However, we would like to remind you of the memorable Aleo testnet since it definitely deserves your attention. Having collected the available statistics, we tried to structure it and present it in the most accessible and understandable format.</p><p>Since Aleo’s testnet has been running for more than three years, we decided to divide our statistics into 2 sections including general network statistics and the results of the team’s work and community on the project’s github.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QHfNm-jY-LEdWyYjvhr5Dw.png" /></figure><ul><li><strong>Block Height</strong>: 1 675 980</li></ul><p>Block height refers to a specific location in a blockchain, measured by how many confirmed blocks precede it. It is primarily determined by counting the number of validated and confirmed blocks that precede a particular block in the chain. Each block in a blockchain contains a bundle of transactions, cryptographic hash pointers to the previous block, and a timestamp, forming an immutable and sequential ledger of transactions.</p><ul><li><strong>Network Validators</strong>: 11</li></ul><p>Validators are infrastructure service providers that secure the network through AleoBFT, a Proof-of-Stake-based consensus method that makes use of Bullshark, a recent consensus research tool, and its directed-acyclic-graph (DAG) Narwhal-Style memory pool. AleoBFT is designed to be an especially safe and economical consensus method. Users can submit less data-intensive proofs by packaging information offchain, which significantly lowers the Network fees — sometimes referred to as “gas” fees — needed to participate. By encapsulating sensitive data in zero-knowledge proofs, they are able to limit the amount of sensitive data they communicate while maintaining the tested security of Proof of Stake models. Validators participate in Aleo’s consensus process to reach a consensus on state and use SnarkOS software to verify and confirm blocks of transactions. When building blocks, they can incorporate evidence from provers and receive payments and prizes for their efforts to secure the network. Every validator possesses a minimum of one million Aleo Credits.</p><ul><li><strong>Network Delegators</strong>: 13 098</li></ul><p>Delegators are blockchain participants who allocate their tokens to a chosen validator or delegate. To support the network, delegators aim to maximize APR (regularly equals to lowest commission rate) stake to larger validators to keep their assets in the active set (if the concept is applicable), keep track of the commission rate and avoid staking to sus validators/pools support geographical and data centre decentralization care for consensus breaking stake concentrations and stake accordingly.</p><ul><li><strong>Network Miners (Provers)</strong>: 736</li></ul><p>Provers (sometimes called ZK Miners or ZK Provers) are a unique form of infrastructure unique to zero knowledge that contributes to the Aleo Network. Provers on Aleo compete with one another to produce SNARK proofs, which are solutions to PoSW (Proof-of-Succinct-Work) Coinbase puzzles, utilizing specialized GPUs and CPUs. Provers will have a better chance of winning Aleo Coinbase awards if they can solve the riddles more quickly and effectively. Provers can split the Coinbase prizes among themselves according to how many legitimate puzzle solutions they submit.</p><ul><li><strong>Most called programs in the past</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CEb8FeFvyftZZlVtwat8Ww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jx9zkZBacVtztoJ63G1lZA.png" /></figure><ul><li><strong>Followers</strong>: 4 854</li><li><strong>Repositories</strong>: 41</li></ul><p>A repository is the most basic element of GitHub. It’s a place where users can store their code, files, and each file’s revision history. Repositories can have multiple collaborators and can be either public, internal, or private.</p><ul><li><strong>Tutorial Badge</strong>: 13 176</li></ul><p>Holders of the badge have completed the Developer Toolkit tutorial. I’ve also done a tutorial on hope to claim the badge, check it out here:</p><ul><li><strong>Code Badge</strong>: 20</li><li><strong>Total Badges</strong>: 13 296</li><li><strong>Total Issues</strong>: 21 206</li></ul><p>GitHub Issues are items users have created in a repository to plan, discuss and track work. Issues are simple to create and flexible to suit a variety of scenarios. Usually, issues are used to track work, give or receive feedback, collaborate on ideas or tasks, and efficiently communicate with others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EA_Wt2m457WAhgvbO14FNg.png" /></figure><p>Hope you enjoyed this trip to the depths of Aleo testnet history and let’s keep bringing Aleo Mainnet closer together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oUtDIXLQm69LNem0D3ef2Q.png" /></figure><ul><li><strong><em>Website</em> </strong>— <a href="https://aleo.org/">aleo.org</a></li><li><strong><em>Twitter</em> </strong>— <a href="https://twitter.com/AleoHQ">twitter.com/AleoHQ</a></li><li><strong><em>Discord </em></strong>— <a href="https://discord.gg/aleo">discord.gg/aleo</a></li><li><strong><em>GitHub </em></strong>— <a href="https://github.com/AleoHQ">github.com/AleoHQ</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a2d8e6c61da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aleo Mainnet Final Leap: How Aleo Mainnet Brings Innovations to the Crypto Industry and the World]]></title>
            <link>https://mctrick.medium.com/aleo-mainnet-final-leap-how-aleo-mainnet-brings-innovations-to-the-crypto-industry-and-the-world-af0ff4470a52?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/af0ff4470a52</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[aleo]]></category>
            <category><![CDATA[zero-knowledge-proofs]]></category>
            <category><![CDATA[real-life]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Sat, 09 Mar 2024 17:34:21 GMT</pubDate>
            <atom:updated>2024-03-09T17:34:21.558Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NI90Mp6ZZaoA_6_9iBbRCw.png" /></figure><h3>Table of Contents</h3><ol><li><em>Introduction</em></li><li><em>Off-chain</em></li><li><em>On-chain</em></li><li><em>Real life</em></li><li><em>So what is Aleo’s contribution to zkML?</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pxHIfAp3t22v8ViCu-mV4A.png" /></figure><p>In previous articles, we have already explored Aleo’s path to launching its main network. We’ve looked at the structure of Aleo itself, its product, and the network’s ecosystem projects. It becomes clear that Aleo is a strong project with a developed technical infrastructure, ecosystem, and community. However, you may still wonder what fundamentally new Aleo brings to the industry.</p><p>In this article, we would like to cover this issue more and consider one of Aleo’s innovative initiatives — <strong>zkML (Zero-Knowledge on Machine Learning)</strong>. Machine learning has crept into our daily lives in the form of tailored product recommendations and expertly managed social media feeds, making you feel instantaneously understood on an individual level. Zero-knowledge cryptography tackles several of the most pressing issues in the machine learning industry. Zero-knowledge proofs are an effective method for validating the accuracy of a calculation without disclosing the input data or computation itself. This makes them especially valuable in machine learning, where sensitive data such as medical records or financial information must be kept secure.</p><p>The functionality of zkML allows it to be used in many ways, including both real-life and online applications. To be precise, let’s give a couple of examples of <strong>zkML use cases</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVC28DsipTWFufcBco6rXw.png" /></figure><ul><li><strong>Ensuring the use of machine learning in high-assurance industries.</strong></li></ul><p>When lives are on the line, it is vital to verify that machine learning models deliver reliable findings that have not been hacked or manipulated by malevolent actors. Any machine learning models used in the military, self-driving vehicles, or medical imaging and diagnostics, for example, should have additional validation software that can validate a zero-knowledge evidence that sensor data was correctly evaluated.</p><ul><li><strong>Protecting proprietary machine learning models.</strong></li></ul><p>Many firms have already developed proprietary machine-learning models that they do not wish to publish publicly. Because these models may have been trained on private data or utilized in highly regulated businesses, it may be necessary to demonstrate that a result came from that specific model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNcXWKtrMBqvR-ZI1rtImQ.png" /></figure><ul><li><strong>Developing privacy-preserving credit ratings.</strong></li></ul><p>When cryptocurrency traders borrow, the lender must ensure that the borrower is trustworthy. Borrowers may operate on a global scale, even using aliases. A machine learning model may be used to assess borrowers’ creditworthiness in a privacy-preserving manner, allowing borrowers to be paired with lenders who best suit their requirements.</p><ul><li><strong>Establishing private KYC processes.</strong></li></ul><p>As part of the KYC procedure, new users are frequently required to upload a photo of their driver’s license and then complete a liveness test that includes gazing into their camera and tilting their head. To safeguard the user’s personal privacy, a machine learning model might be constructed with zero information that conducts the liveness test, compares it to a user’s driver’s license photo, and gives a score for how closely they match, as well as verification that the model was run correctly.</p><ul><li><strong>Creating reliable stablecoin exchange rates.</strong></li></ul><p>Oracles play a key role by bringing off-chain data on-chain, which is necessary since smart contracts cannot access information outside of the blockchain network. They are frequently employed in stablecoins, whose security assumptions are based on the regular and timely reporting of an exchange rate between an asset (such as ETH) and a stablecoin that is expected to stay tied to a real-world currency. Machine learning can improve the accuracy and robustness of this reporting, while zero-knowledge proofs ensure that the oracle did the calculation correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qmgXpBQ_D6Es1BwuENswHA.png" /></figure><p>Machine learning will affect every aspect of our life in the not-too-distant future, whether we like it or not. Aleo’s innovation aims to add a layer of security to numerous critical use cases, both on-chain (public blockchain transactions) and off-chain (transactions validated outside of the main blockchain network).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c4yxEaL9QgRNAU4XGkuJdA.png" /></figure><p>To answer this question, we have to tell you about Aleo’s zkML transpiler, an open-source SDK that bridges Python — one of the most popular programming languages for machine learning developers — and zero-knowledge cryptography. Developers may train their machine learning model as usual, and then use the transpiler to convert it to Leo, a ZK-friendly programming language that works with Aleo’s zero-knowledge layer 1 solution. The transpiler can be used for decision tree models, a popular form of machine learning technique that can generate both classification and regression models. It may eventually be developed to incorporate models such as random forest ML, rudimentary neural networks, linear regression, and others. Using the zkML transpiler, the Leo programming language, and maybe additional tools, developers can begin developing verified machine learning models, revealing important potential use cases for the whole AI domain.</p><p>A variety of businesses might profit from such applications, particularly those with high regulatory and data security demands, including Financial Services, Healthcare, and Human identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_55P_laj6Bvm3LSdB3An9Q.png" /></figure><ul><li><strong><em>Website</em> </strong>— <a href="https://aleo.org/">aleo.org</a></li><li><strong><em>Twitter</em> </strong>— <a href="https://twitter.com/AleoHQ">twitter.com/AleoHQ</a></li><li><strong><em>Discord </em></strong>— <a href="https://discord.gg/aleo">discord.gg/aleo</a></li><li><strong><em>GitHub </em></strong>— <a href="https://github.com/AleoHQ">github.com/AleoHQ</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af0ff4470a52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aleo Mainnet Final Leap: Aleo Ecosystem at the Mainnet Launch]]></title>
            <link>https://mctrick.medium.com/aleo-mainnet-final-leap-aleo-ecosystem-at-the-mainnet-launch-4421667e516a?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/4421667e516a</guid>
            <category><![CDATA[zero-knowledge-proofs]]></category>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[aleo]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Thu, 07 Mar 2024 18:46:20 GMT</pubDate>
            <atom:updated>2024-03-07T18:46:20.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sto9LayQ8zsERGw87Kie-w.png" /></figure><h3>Table of Contents</h3><ol><li><em>Introduction</em></li><li><em>How does Aleo accelerate the development of its ecosystem?</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghLKmMvsgBIF8liH9_atVQ.png" /></figure><p>As Aleo approaches the launch of the main network, it will be useful for us to know not only about the technical aspects of the protocol, but also the products and applications that are built on it. As you may have already realized, today we would like to talk about Aleo ecosystems.</p><p>During the last year, the Aleo ecosystem saw a rapid growth, according to Electric Capital’s 2023 Crypto Developer Report, Aleo has one of the top five fastest-growing ecosystems by total developers (150+ devs), with an overall growth rate of 167% when comparing Q4 2023 to Q4 2022.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HiiytniNvBfNlDdiXN2tqg.png" /></figure><p>According to the survey, the number of monthly active developers (9,357) working on the top 200 ecosystems besides Bitcoin and Ethereum is down 31% year on year. Despite this, Aleo increased developer engagement across quarters via a combination of testnets, grant programs, and incentive programs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m4xERFHIFWMT2BLLZ2Glxg.png" /></figure><p>Aleo managed to achieve such an impressive developer performance by conducting the Aleo Tooling &amp; Infrastructure Grants Program, zkMeetups, Bug Bounties, and Deploy Incentives. The program welcomed<strong> </strong>all sorts of tooling and infrastructure, with the exception of block explorers.</p><p>Aleo’s $1M grant program is absolutely worth mentioning, the initiative is divided into two different grant types for intermediate and expert level developers. Intermediate level developers can apply for the Aleo Blueprint Grants. These grants amass $10K — $100K and are usually given for building pre-specified projects, also known as, Request for Proposals (RFPs).</p><p>On the other hand, Launch Grants intended for seasoned developers proposing full-featured, multi-milestone projects with $10K — $200K+ in grants. Among grants winning projects are: Leo Wallet, Boloney, Zenet, and Leo Program Runner among others.</p><p>This is where we come to <strong>Aleo’s ecosystem projects</strong>. For easier perception, we propose to divide all ecosystem projects into the following categories:</p><ul><li>DeFi</li><li>Gaming</li><li>Bridges</li><li>Wallets</li><li>NFT</li></ul><p>The current <strong>DeFi</strong> realm on Aleo is mostly consists of decentralized exchanges, among the category leaders are:</p><ul><li>AleoSwap</li><li>Privx</li><li>AleoSwap</li><li>AtomiK</li><li>AlphaSwap</li></ul><p>Among Aleo-based <strong>Gaming </strong>projects are:</p><ul><li>Boloney</li><li>Zenet</li><li>Battleship</li></ul><p>Gateways to Aleo (<strong>Bridges</strong>):</p><ul><li>Izar</li></ul><p>Ecosystem <strong>Wallets</strong>:</p><ul><li>Leo Wallet</li><li>AvailWallet</li></ul><p><strong>NFT</strong> Applications:</p><ul><li>VolcaniX</li><li>Artefact</li><li>Aleo.store</li></ul><p>Hope this article will help you to collect at least a rough picture and scheme of the Aleo ecosystem, learn about its current leaders and possibly join it yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6_FEQzgPJyU2cL2V7iBCw.png" /></figure><ul><li><strong><em>Website</em> </strong>— <a href="https://aleo.org/">aleo.org</a></li><li><strong><em>Twitter</em> </strong>— <a href="https://twitter.com/AleoHQ">twitter.com/AleoHQ</a></li><li><strong><em>Discord </em></strong>— <a href="https://discord.gg/aleo">discord.gg/aleo</a></li><li><strong><em>GitHub </em></strong>— <a href="https://github.com/AleoHQ">github.com/AleoHQ</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4421667e516a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aleo Mainnet Final Leap: Zero-Knowledge Proofs and Aleo Mainnet]]></title>
            <link>https://mctrick.medium.com/aleo-mainnet-final-leap-zero-knowledge-proofs-and-aleo-mainnet-cb53985abec0?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb53985abec0</guid>
            <category><![CDATA[zkcloud]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[mainnet]]></category>
            <category><![CDATA[aleo]]></category>
            <category><![CDATA[zero-knowledge-proofs]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Wed, 06 Mar 2024 11:37:22 GMT</pubDate>
            <atom:updated>2024-03-06T11:37:22.915Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8udQaC6QjByyrrVb-DI4nA.png" /></figure><h4>Table of Contents</h4><ol><li><em>Introduction</em></li><li>But how does it work from the inside?</li><li>Shielded identities</li><li>Shielded transactions</li><li>zkCloud</li><li>References</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SDzBRzlY8aaF5OE2mw367A.png" /></figure><p>Now that we have a general understanding of what the ZKP technology is, let’s dive into its implementation on Aleo Mainnet.</p><p>First of all, we need to keep in mind that Aleo’s mission is to enable developers to build truly private applications. By allowing parties on a decentralized network to prove knowledge of some information without revealing the underlying facts that make it true, Aleo’s ZKP unlocks a whole variety of business models and applications that weren’t possible before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MKgIiwEe57LCP_wBEBD6Ow.png" /></figure><p>At its core, every programming language has a so-called primitive, an atomic unit that acts as a fundamental building block of the language. They reflect the fundamental elements of every solution that may be merged and improved upon to produce new solutions, and they offer a first-principles approach to emerging technologies.</p><p>Zero-knowledge applications based on <strong>Aleo Mainnet</strong> will have its primitives as well. They are:</p><ul><li>Shielded identities</li><li>Shielded transactions</li></ul><p>These primitives act in an environment called <strong>zkCloud</strong> — a component of the Aleo stack that forms the basis for a more secure, private, and personalized paradigm for applications.</p><p>The working process of these three components can be visualized as following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Kp7OXTXn04iZoXnMqAOxw.png" /></figure><p>To get the full understanding of the process let us examine the role and tasks of every component separately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IwQ_CgYQYvMJ5deJcCsBqA.png" /></figure><p>Similar to a firewall that guards a specific individual or entity’s private information, shielded identities do the same. Shielded identities function similarly to a driver’s license that conceals from the questioner any information deemed unnecessary by cryptography. Through the use of shielded identities, people, smart contracts, DAOs, and businesses can communicate with one another while keeping only the information that is absolutely necessary to know. An exchange or dark pool’s on-chain know-your-customer (<strong>KYC</strong>) procedure serves as a straightforward illustration. Shielded identities allow a user to authenticate to an application while remaining totally anonymous, in contrast to Ethereum, where a user would have to expose their whole account and all of their asset holdings under a pseudonym.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EIjEf1JSSPSkub3d14-z4Q.png" /></figure><p>Zcash invented shielded transactions as a primitive. However, transfers of assets are not the only kind of shielded transactions in Aleo. They explain every type of interaction that takes place between a person and a program. Liquidity provisioning, governance voting, identity authentication, decentralized alerts, and more are a few instances that go beyond straightforward payments. Malicious third parties are unable to discover the specifics of an interaction or take advantage of it in any way as only the persons involved are aware of its details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rhv6K4PrFfyUYVD3sznSbA.png" /></figure><p><strong>zkCloud </strong>is an off-chain, trustless execution environment where individual entities, or shielded identities, interact with one another through shielded transactions. A form of peer-to-peer, decentralized, private computing called zkCloud allows shielded identities to communicate programmatically (via a smart contract) or directly (with an asset transfer). Aleo ensure privacy and increase transaction performance by transferring this conversation off-chain. The Aleo blockchain is connected to the interactions of one or more parties within zkCloud through shielded transactions. Cryptographic evidence proving the validity of those interactions is contained in these transactions. However, they by default withhold the identity of participants and the application that was run. These transactions are recorded on the Aleo blockchain and can be consulted at any moment to ascertain the overall status of an application.</p><p>Applications built using zkCloud can be executed locally on a user’s PC or assigned to an outside proving-service, which creates proofs and submits transactions on the user’s behalf. This opens the door to a new marketplace for delegated private computers and makes a wider range of applications feasible on Aleo today.</p><p>Offloading execution off-chain, facilitated by zkCloud, provides various advantages over typical blockchains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hpf8wBuC4UmwmIBGQxqNeQ.png" /></figure><p>As a result of separating compute and state, zkCloud offers <strong>infinite application runtime</strong>. Programs that execute in zkCloud can take seconds, minutes, or days; it makes no difference as long as the protected transaction is submitted at the end of the calculation. This allows for a much wider range of applications than is conceivable with an on-chain execution architecture like Ethereum, where program runtime is restricted by “gas.”</p><p>Furthermore, off-chain execution in zkCloud results in much <strong>increased privacy</strong> for consumers engaging with applications. Because only proofs are provided on-chain, no one can see or exploit transaction data.</p><p>Even with these added benefits, Aleo’s technique maintains security because the zero-knowledge proofs that comprise a shielded transaction cryptographically guarantee accurate program execution. This contrasts with other blockchains and many layer-2 systems, which merely provide crypto-economic guarantees that a state transfer was completed correctly. However, in Aleo, a proof indicates whether a program ran correctly or not, eliminating the need for the user or smart contract developer to make additional trust assumptions.</p><p>Finally, zkCloud is intended to enable developers create private, <strong>scalable </strong>projects. By separating execution from state and uploading only proofs to the blockchain via shielded transactions, zkCloud allows Aleo to realize its aim of a private, programmable, and performant network. By exposing the primitives of shielded transactions and shielded identities within zkCloud, Aleo Mainnet provides the building blocks required to construct these applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W7wFWZFEzf9fF2CfG1DX0A.png" /></figure><p><a href="https://aleo.org/post/zero-knowledge-primitives-by-aleo">aleo.org/post/zero-knowledge-primitives-by-aleo<br></a><a href="https://aleo.org/post/zkcloud">aleo.org/post/zkcloud</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6_FEQzgPJyU2cL2V7iBCw.png" /></figure><ul><li><strong><em>Website</em> </strong>— <a href="https://aleo.org/">aleo.org</a></li><li><strong><em>Twitter</em> </strong>— <a href="https://twitter.com/AleoHQ">twitter.com/AleoHQ</a></li><li><strong><em>Discord </em></strong>— <a href="https://discord.gg/aleo">discord.gg/aleo</a></li><li><strong><em>GitHub </em></strong>— <a href="https://github.com/AleoHQ">github.com/AleoHQ</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb53985abec0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aleo Mainnet Final Leap: Basic understanding of Aleo blockchain and zkSNARKs]]></title>
            <link>https://mctrick.medium.com/aleo-mainnet-final-leap-basic-understanding-of-aleo-blockchain-and-zksnarks-337a58be9cbe?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/337a58be9cbe</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[aleo]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[zksnark]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Tue, 05 Mar 2024 15:14:03 GMT</pubDate>
            <atom:updated>2024-03-05T15:14:03.460Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2N8cg7gPdObmfXhI6ysQQ.png" /></figure><h3>Table of Contents</h3><ol><li><em>Introduction</em></li><li>Mathematical and cryptographic primitives</li><li>Polynomials</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghLKmMvsgBIF8liH9_atVQ.png" /></figure><p>Aleo has announced the start of its Road to Mainnet and as the project gets closer to launching its main network, we’d like to help the community brush up on their Aleo technical knowledge and be prepared for the big launch. In this first article, we have gathered information that will help readers get or actualize a basic understanding of Aleo blockchain and zkSNARKs. Aleo uses zkVM as the underlying privacy-preserving iteration of the Aleo network.</p><p>As we all know, Aleo uses zero-knowledge proofs as the underlying privacy-preserving iteration of the Aleo network. But what is this technology itself? A zero-knowledge proof is a method that allows one party to prove to another that p1 knows a secret value that fulfills some constraints — without revealing any additional information to p2, only that it knows this secret value. Zero-knowledge proofs are a critical cryptographic solution to protecting user privacy on the web, particularly when scaling toward mass adoption on the blockchain, where they can also help solve computational issues. There are currently two major ways to do this: zkEVMs and zkVMs.</p><p>The notion of a Proof and a Proof System is centric in the realm of ZKPs. In computer science, a “proof” is a formal demonstration that a particular statement is true. Proofs are formalized using “proof systems.” Information-theoretic proof systems play a crucial role as a one of components of zkSNARKs and zkSTARKs.</p><p>The term “information-theoretic” describes the proof system’s capacity to deliver completeness and soundness, even in the face of adversaries with infinite computing power. It is therefore challenging to implement the idealistic assumptions made by an information-theoretic proof system in the real world. For example, it can presume that the verifier is a reliable source with limited access to the evidence. An information-theoretic proving system is worthless as a stand-alone item as it doesn’t care how this assumption is handled in the real world. But as you’ll see in a moment, it can be helpful when paired with a cryptographic compiler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*US1Stl0IZ7tYl_m37IRSjg.png" /></figure><p>The information-theoretic proof system’s idealized presumptions are eliminated by the cryptographic compiler. How? by the use of cryptographic primitives like a generic bilinear group, a random oracle, or a collision-resistant hash function. The result is a practical proof system that is only safe under a prover and/or verifier that is computationally constrained (a presumption that all cryptographic protocols make). In addition, the cryptographic compiler can give the information-theoretic proof system other desirable features like removing interaction, simplifying communication, or including a zero-knowledge feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J5wi5lgJBEP4MzTT_NIY1g.png" /></figure><p>Polynomials are mathematical expressions that look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rLp_pGkrz-LrvXHfXT0FbA.png" /></figure><p>Polynomials facilitate ZKPs usage in three following ways:</p><ul><li>they can encode an unbounded amount of data</li><li>they can encode relationships between data</li><li>they let developer efficiently check whether two pieces of data are the same</li></ul><p>These three use cases emerge thanks to Polynomials’ feature to encode information via coefficients and exponents. Making each coefficient of a polynomial represent a piece of information. Developers can even convert a sizable portion of code into a polynomial. Additionally, code is in the proper format for applying cryptography after it is converted to a polynomial. Not only can one encode a lot of data within polynomials, but also encode relationships between data. This action is possible thanks to so called “polynomial interpolation,” which involves taking a set of data points and approximating a polynomial that passes through all of them. That special polynomial encodes the relationship between all of the data points. And, finally, in a proof system, we can encode hidden information that the prover knows into a polynomial. The tricky part is having the prover prove their knowledge of the secret polynomial without revealing it. To accomplish this, we simply check if the secret polynomial is equal to another polynomial that’s publicly known. If they’re equal, then the prover knows the private polynomial.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_mFbKX21waz1YYtAuyRsw.png" /></figure><ul><li><strong><em>Website</em> </strong>— <a href="https://aleo.org/">aleo.org</a></li><li><strong><em>Twitter</em> </strong>— <a href="https://twitter.com/AleoHQ">twitter.com/AleoHQ</a></li><li><strong><em>Discord </em></strong>— <a href="https://discord.gg/aleo">discord.gg/aleo</a></li><li><strong><em>GitHub </em></strong>— <a href="https://github.com/AleoHQ">github.com/AleoHQ</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=337a58be9cbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aleo Mainnet Final Leap: The Biggest Aleo FAQ]]></title>
            <link>https://mctrick.medium.com/aleo-mainnet-final-leap-the-biggest-aleo-faq-c4ba4d8a9988?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4ba4d8a9988</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[faq]]></category>
            <category><![CDATA[aleo]]></category>
            <category><![CDATA[guide]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Mon, 04 Mar 2024 13:52:34 GMT</pubDate>
            <atom:updated>2024-03-04T13:53:02.851Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohZXoidERTxsteLAvGpKIA.png" /></figure><h4>Table of Contents</h4><ol><li><em>What is Aleo?</em></li><li><em>Aleo’s Idea</em></li><li><em>How to Get Test Tokens?</em></li><li><em>When is the Next Round of the Ambassador Program?</em></li><li><em>When’s the Mainnet?</em></li><li><em>How can I Participate?</em></li><li><em>Leo Contributor Badge</em></li><li><em>What is a zk-SNARK?</em></li><li><em>What is a SNARKos?</em></li><li><em>What is a SnarkVM?</em></li><li><em>Ecosystem</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gxhcziIXzG1bL_Yz5cqJGg.png" /></figure><p><strong>Aleo</strong> is revolutionizing the Layer-1 blockchain landscape by empowering developers to create a more secure and private internet. Unlike <em>Ethereum </em>and other traditional blockchains that mandate public data disclosure, Aleo leverages zero-knowledge technology. This innovative approach enables the Aleo Network to foster collaboration among diverse nodes, including computers, phones, and other devices, to jointly manage a ledger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x47_dy9D_Z0wX5YpyP3MRg.png" /></figure><p>The Aleo project prioritizes privacy and confidentiality in decentralized applications (dApps) by utilizing <strong>zero-knowledge proofs</strong> (ZKPs). Our platform addresses privacy concerns in traditional blockchain networks and provides a secure and scalable foundation for developers to build privacy-preserving applications. Furthermore, running your applications on the Aleo blockchain can significantly contribute to the growth and development of the ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_SZMJP8tZ2k3-4P5qlDShA.png" /></figure><p>Aleo ecosystem partners, Puzzle and Leo Wallet, are now both running two faucets. Please follow the link below for detailed instructions:</p><ul><li><strong>Puzzle</strong>: <a href="https://dev.puzzle.online/faucet">faucet.puzzle.online</a></li><li><strong>Leo Wallet</strong>: <a href="https://link.leo.app/discord">link.leo.app/discord</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yz_LPC8JfwqWo7XiOjih3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFOCc8vvfYQFnSH6UAgsJQ.png" /></figure><p>The <strong>last round</strong> of the Aleo Ambassador Program will take place on <strong>March 10</strong>. Mark this day in your calendars and prepare a resume.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m_be8hsLPkYHEWl7zKTkpg.png" /></figure><p><strong>Aleo Mainnet</strong> launch is scheduled for <strong>Q1 2024</strong>. We encourage you to stay informed about the latest updates by following their <a href="https://discord.com/channels/700454073459015690/722549434520699030">announcements</a>. Furthermore, we have established a direct communication channel with the community to ensure that you are kept up-to-date.</p><p>To read the official article about mainnet, you can read it <a href="https://aleo.org/post/the-road-to-aleo-mainnet/"><strong>here</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JL59ms4qwWgOV2jsG631zA.png" /></figure><p>At this stage, you can participate in the <strong>Ambassador Program</strong>. The resume submission form will be opened on <strong>March 10</strong>, stay tuned for updates.</p><p>You can also test applications from the Aleo <a href="https://aleo.org/ecosystems/">ecosystem</a>, looking for bugs and bugs to improve these dApps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q6lJ_CXQCgXtUXvV5nKgXQ.png" /></figure><p>On December 19, 2023, badge submissions for contributions were <strong>completed</strong>. All valid pull requests submitted on time were awarded badges.</p><p>The Leo Contributor Badge for Tutorials was awarded to <strong>13,358</strong> users, while <strong>220</strong> users received it for Code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZY2tE-tMcpIN7_irpTWNMw.png" /></figure><p><strong>zk-SNARK</strong>s are a powerful cryptographic technique that provides unparalleled privacy in the blockchain landscape. They are a versatile tool that can be used for a variety of purposes, including authentication, digital identity, and secure transactions. By utilizing zk-SNARKs, users can be confident in the security and privacy of their transactions and knowledge proofs.</p><p>Additionally, zk-SNARKs allow for the protection of sensitive information without compromising privacy, making them an ideal solution for a wide range of applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7wQh5GI6TWyqWr2298LJVA.png" /></figure><p><a href="https://github.com/AleoHQ/snarkOS"><strong>snarkOS</strong></a><strong> </strong>is a decentralized operating system for zero-knowledge applications. This code forms the backbone of Aleo network, which verifies transactions and stores the encrypted state applications in a publicly-verifiable manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TehQWTc18Bkc1Io0rEo9SQ.png" /></figure><p><a href="https://github.com/AleoHQ/snarkVM"><strong>SnarkVM</strong></a> is a remarkable demonstration of the powerful combination of virtual machines and zero-knowledge proofs (zk-SNARKs). It provides a secure and dependable runtime environment for executing code with zk-SNARKs, ensuring the utmost privacy and reliability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nG_amKfSIwOr0YrZ69K0tg.png" /></figure><h4>Defi</h4><ul><li><a href="http://izar.xyz/">IZAR</a></li><li><a href="http://arcane.finance/">Arcane Finance</a></li><li><a href="https://privx.exchange/">PrivX</a></li><li><a href="https://alphaswap.pro/">AlphaSwap</a></li><li><a href="https://shadowfi.xyz/">Shadow Finance</a></li></ul><h4>NFT</h4><ul><li><a href="https://www.privacypride.com/">PRIVACY PRIDE</a></li><li><a href="https://art.privacypride.com/">Art Factory</a></li><li><a href="https://aleo.store/">Aleo.store</a></li><li><a href="https://artgo.io/">Artgo</a></li></ul><h4>Explorer</h4><ul><li><a href="https://explorer.aleo.org/">Aleo Explorer</a></li><li><a href="https://explorer.hamp.app/">Haruka’s Aleo Explorer</a></li><li><a href="https://aleo123.io/">Aleo123</a></li></ul><h4>Gaming</h4><ul><li><a href="https://kryha.io/">Kryha</a></li></ul><h4>Wallets</h4><ul><li><a href="https://www.leo.app/">Leo Wallet</a></li><li><a href="https://puzzle.online/">Puzzle Wallet</a></li><li><a href="https://avail.global/">Avail Wallet</a></li></ul><h4>Name Services</h4><ul><li><a href="https://testnet3.aleonames.id/">Aleo Names</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RX9zdDlLZ4kUIuHsinhPKw.png" /></figure><ul><li><strong><em>Website</em> </strong>— <a href="https://aleo.org/">aleo.org</a></li><li><strong><em>Twitter</em> </strong>— <a href="https://twitter.com/AleoHQ">twitter.com/AleoHQ</a></li><li><strong><em>Discord </em></strong>— <a href="https://discord.gg/aleo">discord.gg/aleo</a></li><li><strong><em>GitHub </em></strong>— <a href="https://github.com/AleoHQ">github.com/AleoHQ</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4ba4d8a9988" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming a Validator Babylon Chain]]></title>
            <link>https://mctrick.medium.com/becoming-a-validator-babylon-chain-8ad8448990a4?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ad8448990a4</guid>
            <category><![CDATA[babylon-chain]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 08:26:51 GMT</pubDate>
            <atom:updated>2024-01-19T08:26:51.737Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn how to become a Validator for Babylon.</p><p>In this guide we are going to go through the steps for someone to become a validator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mhUTjDP2al3BDW7U__wQdg.png" /></figure><h3>Prerequisites<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/become-validator#prerequisites">​</a></h3><p>Having a full node setup and synced by following this <a href="https://medium.com/@mctrick/setting-up-a-full-node-babylon-chain-d9dfa84df63f">guide</a></p><h3>Create a Keyring and Get Funds<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/become-validator#1-create-a-keyring-and-get-funds">​</a></h3><p>Validators are required to have funds for two reasons:</p><ol><li>They need to provide a self delegation</li><li>They need to pay for transaction fees for submitting BLS signature transactions</li></ol><p>NOTE</p><p>Currently, validators can only use the test keyring backend. In the future, Babylon will support other types of encrypted backends provided by the Cosmos SDK for validators.</p><p>The <a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/getting-funds">Getting Testnet Tokens</a> page contains detailed instructions on how to create a keyring and get funds for it through a faucet.</p><h3>Create a BLS key<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/become-validator#2-create-a-bls-key">​</a></h3><p>Validators are expected to submit a BLS signature at the end of each epoch. To do that, a validator needs to have a BLS key pair to sign information with.</p><p>Using the address that you created on the previous step ($ADDR variable):</p><pre>babylond create-bls-key $ADDR</pre><p>This command will create a BLS key and add it to the ~/.babylond/config/priv_validator_key.json. This is the same file that stores the private key that the validator uses to sign blocks. Please ensure that this file is secured properly.</p><p>After creating a BLS key, you need to restart your node to load this key into memory. If you followed the <a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/setup-node">setting up a node guide</a>, you would have to</p><pre>sudo systemctl stop babylond<br>sudo systemctl start babylond</pre><h3>Modify the Configuration<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/become-validator#3-modify-the-configuration">​</a></h3><p>A Babylon validator needs to send BLS signature transactions at the end of each epoch. This process is done automatically through the Babylon codebase which identifies which key to use from the ~/.babylond/config/client.toml file. Edit this file and set the keyring backend that you&#39;re using. In this guide&#39;s case:</p><pre>keyring-backend = &quot;test&quot;</pre><p>Furthermore, you need to specify the name of the key that the validator will be using to submit BLS signature transactions under the ~/.babylond/config/app.toml file. Edit this file and set the key name to the one that holds funds on your keyring:</p><pre>key-name = &quot;val-key&quot; # replace with your key name</pre><p>Finally, it is strongly recommended to modify the timeout_commit value under ~/.babylond/config/config.toml. This value specifies how long a validator will wait before commiting a block before starting on a new height. More information can be found <a href="https://docs.tendermint.com/v0.33/tendermint-core/configuration.html#consensus-timeouts-explained">here</a>. Given that Babylon aims to have a 10 second time between blocks, set this value to:</p><pre>timeout_commit = &quot;10s&quot;</pre><h3>Create the Validator<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/become-validator#4-create-the-validator">​</a></h3><p>Contrary to a vanilla Cosmos SDK chain, a validator for Babylon is created through the babylond tx checkpointing create-validator command. This command expects that a BLS validator key exists under the ~/.babylond/config/priv_validator_key.json.</p><p>INFO</p><p>Note: Babylon validators are required to submit a BLS signature transaction every epoch (with current parameters every ~30mins). Those transactions currently cost a static gas fee of 100ubbn. Therefore, it is important that validators maintain enough unbonded funds in their keyring to pay for those transaction fees.</p><p>To create the validator (using sample parameters):</p><pre># Note the variables<br># - $AMOUNT the amount to delegate in ubbn, e.g. 10000000ubbn (must be less than the delegator&#39;s balance)<br># - $CHAIN_ID the chain ID<br># - $VAL_KEY the name of the key (with a test keyring backend) used for the validator<br>babylond tx checkpointing create-validator \<br>    --amount=&quot;$AMOUNT&quot; \<br>    --pubkey=$(babylond tendermint show-validator) \<br>    --moniker=&quot;My Validator&quot; \<br>    --chain-id=$CHAIN_ID \<br>    --gas=&quot;auto&quot; \<br>    --gas-adjustment=1.2 \<br>    --gas-prices=&quot;0.0025ubbn&quot; \<br>    --keyring-backend=test \<br>    --from=$VAL_KEY \<br>    --commission-rate=&quot;0.10&quot; \<br>    --commission-max-rate=&quot;0.20&quot; \<br>    --commission-max-change-rate=&quot;0.01&quot; \<br>    --min-self-delegation=&quot;1&quot;</pre><p>INFO</p><p>Note: In order to become an active validator, you need to have more ubbn tokens bonded than the last validator ordered by the tokens bonded (or the validator set to not be full) as well as have at least 10000000ubbn bonded.</p><h3>Verify your Validator<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/become-validator#5-verify-your-validator">​</a></h3><p>On the Babylon system, one can become a validator only after an epoch ends. For the testnet, an epoch lasts for around 30 minutes.</p><p>To verify that you have become a validator, first find your validator address:</p><pre>babylond keys show $KEYNAME -a --bech val</pre><p>where $KEYNAME is the name of the key that you used for the self-delegation (e.g. val-key on our example). This will return an address which you can use as the $ADDR variable to perform the following query:</p><pre>babylond query staking validator $ADDR</pre><p>If all goes well, you should see a response indicating the parameters that you specified on the create-validator transaction.</p><p>After the epoch ends and if you have enough stake to be an active validator, performing this query will return you a status BOND_STATUS_BONDED. Congrats! You are now a validator on the Babylon system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ad8448990a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Checkpointing Module Babylon Chain]]></title>
            <link>https://mctrick.medium.com/checkpointing-module-babylon-chain-67a74618875b?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/67a74618875b</guid>
            <category><![CDATA[babylon-chain]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Tue, 16 Jan 2024 00:16:52 GMT</pubDate>
            <atom:updated>2024-01-16T00:16:52.674Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn what the Babylon Checkpointing Module is and how it operates.</p><h3>Summary</h3><p>The Checkpointing module is responsible for generating and maintaining checkpoints for each epoch. These checkpoints will be submitted to BTC by <a href="https://docs.babylonchain.io/docs/developer-guides/modules/submitter">vigilante submitters</a> once having accumulated sufficient voting power via BLS signatures. This module plays a critical role in Babylon’s security story as it produces a canonical sequence of epochs.</p><h3>Problem Statement</h3><p>Babylon’s checkpointing is to empower Babylon with BTC-level security by perpetuating the Babylon ledger on BTC. The checkpointing module needs to generate a succinct checkpoint that involves sufficient voting power for each epoch. For the above purpose, the Checkpointing module adopts the <a href="https://datatracker.ietf.org/doc/html/draft-boneh-bls-signature-00">BLS signature scheme</a> which aggregates multiple signatures into a single signature. With the help of BLS signatures, a checkpoint is fixed in size and can be converted into two BTC transactions in the OP_RETURN field with a limit of 80 bytes. Therefore, the checkpointing module needs to handle all the messages related to BLS signatures such as signing, verifying and accumulating BLS signatures.</p><h3>Design</h3><p>The Checkpointing module makes the following design decisions:</p><ul><li><a href="https://docs.babylonchain.io/docs/developer-guides/modules/checkpointing#bls-key-registration">Validator registration</a></li><li><a href="https://docs.babylonchain.io/docs/developer-guides/modules/checkpointing#sending-and-processing-bls-signatures">Sending and processing BLS signatures</a></li><li><a href="https://docs.babylonchain.io/docs/developer-guides/modules/checkpointing#checkpoint-status-change">Checkpoint status change</a></li><li><a href="https://docs.babylonchain.io/docs/developer-guides/modules/checkpointing#checkpoint-verification-and-panicking">Checkpoint verification and panicking</a></li></ul><h3>BLS Key Registration</h3><p>Each validator must register its BLS public key before voting in the Babylon network. Each validator can only register a unique BLS public key, which can only be registered by a unique validator. The registration requires the validator to provide its BLS public key as well as proof which proves its ownership of this key (proof-of-possession, or PoP). The PoP is needed to defend against <a href="https://eprint.iacr.org/2021/377.pdf">rogue key attacks</a>, in which a specially crafted public key (the “rogue” key) is used to forge an aggregated signature. The purpose of PoP is to prove that one validator owns the corresponding BLS private key and the corresponding Ed25519 private key associated with the public key used in Tendermint consensus. The PoP is calculated as the following:</p><p>PoP = sign(key = BLS_sk, data = sign(key = Ed25519_sk, data = BLS_pk)].</p><h3>Sending and Processing BLS Signatures<a href="https://docs.babylonchain.io/docs/developer-guides/modules/checkpointing#sending-and-processing-bls-signatures">​</a></h3><p>The Checkpointing module is initiated with a BLS signer which signs a BLS signature at each epoch boundary and sends it to Tendermint for consensus. The signature is signed over epoch_number concatenated with last_commit_hash obtained from the epoch boundary block&#39;s <a href="https://github.com/tendermint/spec/blob/8dd2ed4c6fe12459edeb9b783bdaaaeb590ec15c/spec/core/data_structures.md">header</a>. Upon receiving a BLS signature transaction, the Checkpointing module accumulates the voting power of the signature for a specific epoch. Once sufficient signatures are accumulated (e.g., &gt; 1/3 in terms of voting power), the checkpoint will become SEALED and no longer accumulate new signatures.</p><h3>Checkpoint Status Change<a href="https://docs.babylonchain.io/docs/developer-guides/modules/checkpointing#checkpoint-status-change">​</a></h3><p>Checkpoints are maintained by the checkpointing module with five statuses: ACCUMULATING, SEALED, SUBMITTED, CONFIRMED, and FINALIZED. We describe the checkpoint status change as below.</p><p>At each epoch boundary, the Checkpointing module generates an empty checkpoint of this epoch with ACCUMULATING. Once it accumulates sufficient voting power, the checkpoint changes the status to SEALED, waiting for a <a href="https://docs.babylonchain.io/docs/developer-guides/modules/submitter">vigilante submitter</a> to submit it to BTC. When a valid checkpoint is reported back to Babylon, meaning that the checkpoint has been submitted to BTC, the status of the checkpoint is changed to SUBMITTED. If a SUBMITTED checkpoint is observed on a forked BTC chain (non-canonical chain), the status will be reverted back to SEALED.</p><p>When a checkpoint receives sufficient confirmations (e.g., k-deep) on the BTC header chain maintained by the btclightclient module, its status will be changed to CONFIRMED. Similarly, as the header chain grows, a checkpoint will eventually change its status to FINALIZED when more confirmations are received (e.g., up to w-deep). The last three statuses are controlled by the btccheckpoint module and the btclightclient as the Checkpointing module requires BTC information from them.</p><h3>Checkpoint Verification and Panicking<a href="https://docs.babylonchain.io/docs/developer-guides/modules/checkpointing#checkpoint-verification-and-panicking">​</a></h3><p>The Checkpointing module verifies raw checkpoints reported from BTC to Babylon by a <a href="https://docs.babylonchain.io/docs/developer-guides/modules/reporter">vigilante reporter</a>. Reported checkpoints are first processed by the btccheckpoint module for decoding and then sent to the Checkpointing module for verification. The verification workflow is as the following:</p><ol><li>check whether the BLS signature of the checkpoint is valid,</li><li>check whether the BLS signature has accumulated sufficient voting power, and</li><li>check whether the signed last_commit_hash of the checkpoint equals to that of the corresponding checkpoint at the same epoch stored locally.</li></ol><p>Step 3 is a critical step to detect forks. If Step 1 and Step 2 pass but Step 3 does not, it means that a fork exists and the validator should panic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67a74618875b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Epoching Module Babylon Chain]]></title>
            <link>https://mctrick.medium.com/epoching-module-babylon-chain-6f28e6f5aae0?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f28e6f5aae0</guid>
            <category><![CDATA[babylon-chain]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Tue, 16 Jan 2024 00:13:26 GMT</pubDate>
            <atom:updated>2024-01-16T00:13:26.527Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn what the Babylon Epoching Module is and how it operates.</p><h3>Summary</h3><p>The epoching module is responsible for reducing and parameterising the frequency of updating the validator set in Babylon. The Babylon blockchain is divided into epochs, and each epoch contains a fixed number of consecutive blocks. All staking-related messages (creating validator, delegating, undelegating, and redelegating) are enqueued to the message queue of the current epoch. At the end of each epoch, the epoching module will execute all staking-related messages, then update the validator set w.r.t. the voting power distribution of validators. After that, the checkpointing module will generate a checkpoint containing the commitment to the epoch’s validator set, then submit the checkpoint to Bitcoin.</p><h3>Problem Statement</h3><p>In Cosmos SDK, the validator set can change upon every block: staking-related messages that affect the validator set’s voting power distribution (e.g., bond/unbond, delegate/undelegate/redegate, slash) can be executed in any block. Since checkpointing the validator set to Bitcoin is necessary for Babylon to obtain Bitcoin security, the frequency of checkpointing to Bitcoin has to be same as the frequency of validator set updates. If the validator set changes upon every block, then Babylon has to checkpoint to Bitcoin upon every new block, which is impractical given Bitcoin’s block interval of 10 minutes. In addition, the Cosmos community also observed that frequent validator set updates make it challenging to implement threshold cryptography, light clients, fair leader election, and staking derivatives, as discussed in <a href="https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-039-epoched-staking.md">ADR-039</a>.</p><p>In order to reduce the frequency of validator set updates, a natural solution is to implement the epoching mechanism (aka epoched staking), which divides the blockchain into epochs and triggers a validator set update per epoch. The idea of epoching was proposed and formalised in <a href="https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-039-epoched-staking.md">ADR-039</a>, and there have been multiple efforts of implementing it. Since Babylon has some extra design goals (e.g., checkpointing epochs) and these efforts have discontinued, Babylon implements its own epoching module.</p><p>In addition, in order to achieve slashable safety, Babylon has to implement Bitcoin-assisted unbonding, where an unbonding request is finished only when the corresponding block has been checkpointed on Bitcoin. With the epoching mechanism, all unbonding requests in an epoch will be finished upon this epoch has been checkpointed on Bitcoin.</p><h3>Design</h3><p>Babylon implements the epoching module in order to reduce the frequency of validator set updates, and thus the frequency of checkpointing to Bitcoin. Specifically, the epoching module is responsible for the following tasks:</p><ul><li>Dividing the blockchain into epochs</li><li>Disabling some functionalities of the staking module</li><li>Disabling messages of the staking module</li><li>Delaying staking-related messages (thus validator set updates) till the end of the epoch</li><li>Releasing the unbonding queue until the corresponding epoch has been checkpointed on Bitcoin.</li></ul><h3>Dividing the Blockchain into Epochs</h3><p>The epoching mechanism introduces the concept of epochs. The blockchain is divided into epochs, each consists of a fixed number of consecutive blocks. The number of blocks in an epoch is called <em>epoch interval</em>, which is a system parameter. At the moment, Babylon uses the epoch interval of 900 blocks, which take about 30 minutes.</p><h3>Disabling Functionalities of the Staking Module</h3><p>Babylon disables two functionalities of the staking module, namely the validator set update mechanism and the 21-day unbonding mechanism.</p><p>In Cosmos SDK, the staking module handles staking-related messages and updates the validator set upon every block. Consequently, the staking module updates the validator set upon every block. In order to reduce the frequency of validator set updates to once per epoch, Babylon disables the validator set update mechanism of the staking module.</p><p>In addition, the staking module enforces the 21-day unbonding rule: an unbonding validator or delegation will become unbonded after 21 days (called *mature validators**). Babylon departs from Cosmos SDK by employing Bitcoin-assisted unbonding that leverages Bitcoin security to achieve slashable safety, where a validator has to be slashed if performing a safety attack. In order to implement Bitcoin-assisted unbonding, Babylon disables the 21-day unbonding mechanism as well.</p><p>In order to disable the two functionalities, Babylon disables staking module’s EndBlocker function that updates validator sets and unbonds mature validators upon a block ends. Instead, upon an epoch has ended, the epoching module will invoke the staking module&#39;s function that updates the validator sets. In addition, upon an epoch has been checkpointed to Bitcoin, the epoching module will invoke the staking module&#39;s function that unbonds mature validators.</p><h3>Disabling Messages of the Staking Module</h3><p>In order to keep the validator set unchanged in the middle of epochs, the epoching module intercepts and rejects staking-related messages that affect validator sets via AnteHandler, but instead defines wrapped versions of them and forwards their unwrapped forms to the staking module upon an epoch ends.</p><p>Recall that a Cosmos SDK module contains protobuf files for messages in transactions. In the staking module, these messages include</p><ul><li>MsgCreateValidator for creating a new validator</li><li>MsgEditValidator for editing an existing validator</li><li>MsgDelegate for delegating coins from a delegator to a validator</li><li>MsgBeginRedelegate for redelegating coins from a delegator and source validator to a destination validator.</li><li>MsgUndelegate for undelegating from a delegator and a validator.</li><li>MsgCancelUnbondingDelegation for cancelling unbonding delegation for a delegator</li></ul><p>Within these messages, MsgCreateValidator, MsgDelegate, MsgBeginRedelegate, and MsgUndelegate affect the validator set. Since Babylon requires the validator set to be unchanged within an epoch, it has to avoid processing these messages in the middle of epochs. To this end, the epoching module defines an AnteHandler to reject these messages. Instead, it defines wrapped versions for them in the epoching module: MsgWrappedCreateValidator, MsgWrappedDelegate, MsgWrappedBeginRedelegate, and MsgWrappedUndelegate. The epoching module receives these messages at any time, but will only process them at the end of each epoch.</p><h3>Delaying Wrapped Messages to the End of Epochs</h3><p>The epoching module will handle wrapped staking-related messages at the end of each epoch. To this end, the epoching module maintains a message queue for each epoch. Upon each wrapped message, the epoching module performs basic sanity checks, then enqueue the message to the message queue. When the epoch ends, the epoching module will unwrap the queued messages and forward them to the staking module. Consequently, the staking module receives and handles staking-related messages, thus performs validator set updates, at the end of each epoch.</p><h3>Bitcoin-assisted Unbonding</h3><p>Bitcoin-assisted unbonding is the mechanism that an unbonding validator or delegation becomes unbonded only when the block containing the associated unbonding request is checkpointed by Bitcoin. The mechanism is necessary for achieving slashable safety where a validator has to be slashed if performing a safety attack.</p><p>Babylon implements the Bitcoin-assisted unbonding mechanism by invoking the staking module upon an epoch becomes checkpointed. Specifically, the staking module’s ApplyMatureUnbondings is responsible for identifying and unbonding mature validators and delegations that have been unbonding for 21 days, and is invoked upon every block. Babylon has disabled the invocation of ApplyMatureUnbondings per block, and implements the state management for epochs. Upon an epoch becomes finalized, the epoching module will invoke ApplyMatureUnbondings to unbond all unbonding validators and delegations before the end of this epoch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f28e6f5aae0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up a Full Node Babylon Chain]]></title>
            <link>https://mctrick.medium.com/setting-up-a-full-node-babylon-chain-d9dfa84df63f?source=rss-3c01d6941267------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9dfa84df63f</guid>
            <category><![CDATA[babylon-chain]]></category>
            <dc:creator><![CDATA[McTrick]]></dc:creator>
            <pubDate>Thu, 11 Jan 2024 21:54:03 GMT</pubDate>
            <atom:updated>2024-01-11T21:54:03.718Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn how to set up the full node for the Babylon system.</p><p><strong>This guide requires having Babylon installed on a Linux System.</strong></p><h3>1. Initialize the Node Directory<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/setup-node#1-initialize-the-node-directory">​</a></h3><p>First, initialize a node configuration directory under ~/.babylond. The $NODENAME variable specifies the name you aim to give your node.</p><pre>babylond init $NODENAME --chain-id bbn-test-2</pre><p>Then, retrieve the genesis file and place it in the node directory:</p><pre>wget https://github.com/babylonchain/networks/raw/main/bbn-test-2/genesis.tar.bz2<br>tar -xjf genesis.tar.bz2 &amp;&amp; rm genesis.tar.bz2<br>mv genesis.json ~/.babylond/config/genesis.json</pre><h3>2. Add Peers and Modify Configuration<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/setup-node#2-add-peers-and-modify-configuration">​</a></h3><p>Edit the configuration file at ~/.babylond/config/config.toml and modify the seeds and persistent_peers attributes to contain appropriate seeds and peers of your choice. The full list of Babylon approved seeds and peers can be found under the <a href="https://github.com/babylonchain/networks/tree/main/bbn-test-2">bbn-test-2 network info page</a>.</p><p>Edit the configuration file at ~/.babylond/config/app.toml and modify the btc-network attribute to contain the appropriate BTC network parameters as below.</p><pre>[btc-config]<br>network = &quot;mainnet&quot;</pre><p>On the same file, you can also modify the minimum-gas-prices attribute and set it to a value of your choosing. For example,</p><pre>minimum-gas-prices = &quot;0.00001ubbn&quot;</pre><h3>3. Setup Cosmovisor<a href="https://docs.babylonchain.io/docs/user-guides/btc-timestamping-testnet/setup-node#3-setup-cosmovisor">​</a></h3><p>To install the latest version of Cosmovisor</p><pre>go install cosmossdk.io/tools/cosmovisor/cmd/cosmovisor@latest</pre><p>Create the necessary directories</p><pre>mkdir -p ~/.babylond<br>mkdir -p ~/.babylond/cosmovisor<br>mkdir -p ~/.babylond/cosmovisor/genesis<br>mkdir -p ~/.babylond/cosmovisor/genesis/bin<br>mkdir -p ~/.babylond/cosmovisor/upgrades</pre><p>Copy the babylond binary into the cosmovisor/genesis folder</p><pre>cp $GOPATH/bin/babylond ~/.babylond/cosmovisor/genesis/bin/babylond</pre><p>Setup a cosmovisor service:</p><pre>sudo tee /etc/systemd/system/babylond.service &gt; /dev/null &lt;&lt;EOF<br>[Unit]<br>Description=Babylon daemon<br>After=network-online.target<br><br>[Service]<br>User=$USER<br>ExecStart=$(which cosmovisor) run start --x-crisis-skip-assert-invariants<br>Restart=always<br>RestartSec=3<br>LimitNOFILE=infinity<br><br>Environment=&quot;DAEMON_NAME=babylond&quot;<br>Environment=&quot;DAEMON_HOME=${HOME}/.babylond&quot;<br>Environment=&quot;DAEMON_RESTART_AFTER_UPGRADE=true&quot;<br>Environment=&quot;DAEMON_ALLOW_DOWNLOAD_BINARIES=false&quot;<br><br>[Install]<br>WantedBy=multi-user.target<br>EOF</pre><h3>4. Start the Node</h3><pre>sudo -S systemctl daemon-reload<br>sudo -S systemctl enable babylond<br>sudo -S systemctl start babylond</pre><p>You can check the status of the node by running</p><pre>systemctl status babylond</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9dfa84df63f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>