<?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 Praveen Pendyala on Medium]]></title>
        <description><![CDATA[Stories by Praveen Pendyala on Medium]]></description>
        <link>https://medium.com/@pkpio?source=rss-d72b82d89292------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gV1CluUx9FAS7o625oU-zg.jpeg</url>
            <title>Stories by Praveen Pendyala on Medium</title>
            <link>https://medium.com/@pkpio?source=rss-d72b82d89292------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:50:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pkpio/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[Fund Raiser For Ukraine]]></title>
            <link>https://medium.com/plaincrypto/fund-raiser-for-ukraine-with-nfts-1bbafa884397?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bbafa884397</guid>
            <category><![CDATA[ukraine-crisis]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ukraine]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Sat, 05 Mar 2022 19:28:05 GMT</pubDate>
            <atom:updated>2022-03-05T19:38:21.617Z</atom:updated>
            <content:encoded><![CDATA[<p>These are challenging times. The people of Ukraine are fighting an unprovoked, unlawful, and unjust invasion by Russia. Ukraine is dealing with the <a href="https://www.globalfirepower.com/country-military-strength-detail.php?country_id=russia">2nd most powerful military in the world</a> and they have been asking for help in every way possible. The government of Ukraine has setup official accounts to accept donations.</p><ul><li>Fiat donations: <a href="https://bank.gov.ua/en/news/all/natsionalniy-bank-vidkriv-spetsrahunok-dlya-zboru-koshtiv-na-potrebi-armiyi">https://bank.gov.ua/en/news/all/natsionalniy-bank-vidkriv-spetsrahunok-dlya-zboru-koshtiv-na-potrebi-armiyi</a></li><li>Crypto donations: <a href="https://twitter.com/Ukraine/status/1497594592438497282">https://twitter.com/Ukraine/status/1497594592438497282</a></li></ul><p>The Crypto donations have <a href="https://www.cnbc.com/2022/03/03/ukraine-raises-54-million-as-bitcoin-donations-surge-amid-russian-war.html">surpassed over $54 million dollars</a>! With over <a href="https://etherscan.io/address/0x165CD37b4C644C2921454429E7F9358d18A45e14">$6M currently sitting in the official Ethereum</a> address. We want to keep the momentum going and offer yet another way to raise funds for Ukraine through the use of NFTs. Here is an overview of our approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1xv8F_CIsUOIhwxW7EMXsA.png" /><figcaption>Raising donations for Ukraine through NFTs</figcaption></figure><p>The proposition is simple:</p><ol><li>People donate to official Ukraine wallets through our NFT contract</li><li>100% of the money donated will go to the official Ukraine wallet</li><li>The donor gets an NFT that symbolizes their support forever</li></ol><p>More details about our approch(es) below.</p><blockquote>Ukraine declared independence on <strong>24 August, 1991</strong>. We will use the number 0.0<strong>24</strong>08<strong>1991</strong> in our pricing of the NFTs</blockquote><h3>Fixed cost NFTs</h3><ul><li>Each NFT is listed for a fixed price (0.0<strong>24</strong>08<strong>1991</strong> ETH)</li><li>Money is donated automatically to the official government address after every 2 Ether raised</li><li>This approach<strong> raises a fixed amount</strong> from primary sales (mint)</li><li>100% of revenue from secondary sales will also be donated to the official government address</li></ul><h3>Auctioning NFTs</h3><ul><li>All NFTs are listed for auction at a starting price of 0.0<strong>24</strong>08<strong>1991</strong> ETH each.</li><li>The auction runs seperately for each NFT</li><li>The highest bidder gets the NFT when the auction ends and the proceeds go to, you guessed it, official Ukraine address</li><li>The aution ends for an NFT when there is a highest bidder on an NFT and there are no further bids on that NFT in a 12 hour period</li><li>Each bid will extend the end of auction to 12 hours from the time of latest bid</li><li>This approach <strong>maximizes the amount of donations</strong> through primary sales (mint)</li><li>100% of revenue from secondary sales will also be donated to the official government address</li></ul><h3>Join us</h3><p>We are looking for volunteers — <strong>artists, web developers, designers</strong>. Join us in our mission to raise funds for Ukraine in these challenging times. From the tech side, we already have:</p><ul><li>✅ Smart contracts ready to go — auctioning model is in the works</li><li>✅ Generative art engine — if you are looking to contribute generative art</li><li>🛠️ Project website and mint page — Core tech is ready, need to finalise the visual design</li><li>🛠️Art work — we have a couple of artists onboard. Looking for more contributors.</li></ul><p>As an artist, you can choose if you would like to have your name or pseudonym associated in the metadata of each NFT art you contributed, and on the project page.</p><h3>Other projects</h3><ul><li><a href="https://www.ukrainedao.love/">UkraineDAO</a> is raising funds with a similar approach but the bid is complete and only direct donations are supported now.</li><li><a href="https://holywater.tech/save-ukraine">World Save Ukraine by Holy Water</a>: NFT collection from over 200+ Ukrainian artists with all proceeds going directly to official address.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bbafa884397" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plaincrypto/fund-raiser-for-ukraine-with-nfts-1bbafa884397">Fund Raiser For Ukraine</a> was originally published in <a href="https://medium.com/plaincrypto">Plain Crypto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Are DAOs And How They Work?]]></title>
            <link>https://medium.com/plaincrypto/what-are-daos-and-how-they-work-cb4a8fba8e5e?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb4a8fba8e5e</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Thu, 10 Feb 2022 16:33:38 GMT</pubDate>
            <atom:updated>2022-02-10T16:40:03.111Z</atom:updated>
            <content:encoded><![CDATA[<p>DAOs are gaining a lot of traction in the blockchain space. They are a crucial building block for the next version of the Internet — Web 3.0. But what is a DAO and how does a DAO work? We will answer these questions and more in this article. This is also available as video if you prefer.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fc7koELvEfBo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dc7koELvEfBo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fc7koELvEfBo%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/14f7b8742e4911d9d770bc88be2a3204/href">https://medium.com/media/14f7b8742e4911d9d770bc88be2a3204/href</a></iframe><h3>Background</h3><p>The best way to understand a new concept is by relating to something we are familiar with. So, in order to understand DAOs let’s start with a concept we come across everyday.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Ra9XA-sZ9EsnaDBOFY4zA.png" /><figcaption>Structure of a football club</figcaption></figure><p>Organisations, or more informally clubs. Suppose you are part of a Football club. To promote the club, all the members contributed some money to the club’s fund. When the club gets big enough it will naturally have a management structure with roles like manager, treasurer etc. The management is expected to lead the club and they have access to the club’s fund. You have to trust them to be honest and use the money only to promote the interests of the club. The future of the whole club relies heavily on the integrity and ability of these few people. The key here is trust — something that’s broken all too often these days. This is where DAOs can help!</p><h3>Why Do We Need a DAO</h3><p>Well, in this example, if you use a DAO to run the club, you don’t need to trust anyone else in the group, just the DAO’s code, which is 100% transparent and verifiable by anyone. DAO will facilitate coordination among the members to achieve the goals of the group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*72Dew65NOAk5CQwacdVZMQ.png" /></figure><h3>What Is a DAO</h3><p>At its core, a DAO is a smart contract. A piece of code which defines the rules of how the organisation should run. Unlike traditional organizations, there is no hierarchy to DAOs. To align interests of the organization with that of its members, DAOs incentivize their users to achieve their goal. A key distinction from traditional organisation is that the control is decentralised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Y6y_0LWuX3EoModNBuvrQ.png" /><figcaption>What is a DAO?</figcaption></figure><h3>How DAOs Work</h3><p>Forming a DAO typically involves the following steps.</p><h4><strong>Establishing a cause</strong></h4><p>First you need a reason to form a DAO. It can be anything that brings people together. For example, things like forming a:</p><ul><li><strong>Charitable trust:</strong> People from around the world donate money to the trust and the group can decide how they want to spend donations.</li><li>An Investment fund or simply</li><li>Giving the users the rights to govern an organisation</li></ul><p>Once the purpose is established and the rules of how the DAO runs are written into smart contracts. They typically enter a Funding phase.</p><h4><strong>Funding phase</strong></h4><p>Any who wishes to be part of the DAO can contribute to the DAOs fund and the DAO will issue tokens proportional to the size of their contribution. These tokens will give you voting rights to steer the direction of the DAO. This is similar to how companies issue shares today except DAOs are more decentralised. At the end of the funding phase, the DAO is considered live and operational. Moving forward, all key decisions surrounding the organization are made through governance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iuvnCTZ7PJw0iZnjX1Ot5A.png" /><figcaption>Steps to form a DAO</figcaption></figure><h4><strong>Governance</strong></h4><p>All users who own the DAO tokens vote on proposals. The weight of their votes will be proportional to the share of tokens they hold. So, if the DAO issued a total of 1000 tokens and you hold 100 of them, your vote will carry a 10% weight. When a consensus is reached, the result of the vote can be automatically actioned by the DAO’s code.</p><h3>How Are DAOs Being Used Today?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*602tFH1VCsviveBy" /><figcaption>State of DAO landscape today. Original photo — <a href="https://twitter.com/Cooopahtroopa/status/1407458878246121475/photo/1">https://twitter.com/Cooopahtroopa/status/1407458878246121475/photo/1</a></figcaption></figure><p>Here’s an overview of the DAO landscape. Pretty much every reputable dApp or protocol uses a DAO structure. UniSwap, Aave, Curve are all popular protocols with Billions of dollars at stake, controlled by DAOs. MolochDAO is funding the development of public infrastructure related to Eth 2.0. People are also using DAOs to invest together — for example, if you want to buy an NFT from the BAYC collection, the cheapest one is 83 ETH (nearly 300,000 USD) — even if you have that kind of money, it’s a lot of risk for most people. So, instead you could form a DAO, pool funds from people, and buy a few NFTs through the DAO. This way, you can diversify your collection and have fractional ownership of many expensive NFTs. Social DAOs like Gitcoin are providing grants to fund builders and creators for their work. Personally, I hope to apply for a Gitcoin grant if this channel gets enough traction. So, you would do me a huge favor by hitting that subscribe button.</p><h3>Benefits</h3><p>There are several benefits to using a DAO to run an organisation. Such as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zl30d2JgDl03ehLGWV5h1Q.png" /><figcaption>Benefits of DAOs</figcaption></figure><ul><li><strong>Transparency: </strong>Since all actions of a DAO are public, this builds trust with the community.</li><li><strong>Decentralisation: </strong>DAOs eliminate the need for central hierarchies like management boards.</li><li><strong>Strong Community: </strong>People in a DAO community feel valued and often more engaging because they have a say in the future of the organisation.</li></ul><h3>Downsides</h3><p>It’s not all sunshine and rainbows though. DAOs have their share of downsides too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*1fow0pP6YyMXnbCbyQAnpg.png" /><figcaption>Downsides of DAOs</figcaption></figure><ul><li><strong>Bugs in code: </strong>Exposes them to risk of hacking. In fact the first ever DAO, called The DAO, was hacked and 3.6 million ether were stolen from the DAOs fund. That’s over $12 billion at today’s prices!</li><li><strong>Delays from voting: </strong>Given the decentralised nature of DAOs, each proposal needs to be voted on by the community and that can take a few days to weeks. While this is good under normal circumstances, this is a big issue when developers want to fix a critical bug but need the community approval. In the case of The DAO, a fix was available but the community couldn’t reach consensus in time to apply the fix. And the result was a devastating hack!</li></ul><p>I want to finish on a positive note. Most DAOs today are basically copies of well tested DAO frameworks. They run on minimal code that went through a lot of scrutiny so there’s less scope for bugs. If you find DAOs that align with your values, I think it’s worth being part of that community — after all, we are all working towards building a better world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qplp5q90YfXn-N_MUddmww.png" /><figcaption>Final thoughts on DAOs</figcaption></figure><p>If you find this helpful, clap this upto 50 times, subscribe to my <a href="https://www.youtube.com/c/PlainCrypto">YouTube channel</a>. Thanks for reading all the way. I will see you again soon :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb4a8fba8e5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plaincrypto/what-are-daos-and-how-they-work-cb4a8fba8e5e">What Are DAOs And How They Work?</a> was originally published in <a href="https://medium.com/plaincrypto">Plain Crypto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Measuring Android app size with each change]]></title>
            <link>https://medium.com/microsoft-mobile-engineering/measuring-android-app-size-in-ci-c6f886b88a3?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6f886b88a3</guid>
            <category><![CDATA[app-size]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Tue, 09 Nov 2021 14:51:23 GMT</pubDate>
            <atom:updated>2021-11-09T14:51:23.649Z</atom:updated>
            <content:encoded><![CDATA[<p>App size is crucial for conversions (viewing your app listing to installing it) and retention (keeping your app installed). In a previous post we talked about how at Microsoft SwiftKey, we reduced our app size significantly by adopting various techniques available at the time.</p><p><a href="https://medium.com/microsoft-mobile-engineering/app-size-reduction-at-microsoft-swiftkey-f77d7d5916b">App size reduction at Microsoft SwiftKey</a></p><p>Reduced app size is not a steady state. We have to make a conscious effort to keep it that way. The best way to do this is by measuring app size changes across each change in the codebase — on each PR, ideally. In this post we want to share about an extension to measure app size changes using your CI.</p><p><a href="https://github.com/microsoft/android-app-size-diff">GitHub - microsoft/android-app-size-diff: Android app size measuring in your CI</a></p><p>The repository contains a <a href="https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps">GitHub Workflow Action</a> and an <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/tasks?view=azure-devops&amp;tabs=yaml">Azure DevOps Task</a>. If you use either of these CI systems, you can start using it like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9609c79468d10ef5d78e2be5f85af1cd/href">https://medium.com/media/9609c79468d10ef5d78e2be5f85af1cd/href</a></iframe><p>At the time of this writing, the extension produces a markdown summary of app size changes across the following metrics:</p><ul><li>apkSize: The raw size of the APK files given as inputs</li><li>installSize: Estimated install of the APK. As discussed in our app size reduction post, install size is always greater than the raw APK size. This metric gives an estimated install size change between the 2 APKs.</li><li>dexFiles: Size differences in the bytecode of the 2 input APKs.</li><li>arscFile: A measure of the size of resources in your APKs.</li><li>nativeLibs: The size of native libraries in your APKs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*hv0Jcr2g8U25T0Gm_QxaZw.png" /><figcaption>A markdown summary of different app size metrics generated by running the extension</figcaption></figure><p>To install this in your CI, head over to:</p><ul><li>GitHub Marketplace: <a href="https://github.com/marketplace/actions/android-app-size-difference">https://github.com/marketplace/actions/android-app-size-difference</a> or</li><li>Visual Studio Marketplace: <a href="https://marketplace.visualstudio.com/items?itemName=MSSwiftKey.android-app-size-diff-utils">https://marketplace.visualstudio.com/items?itemName=MSSwiftKey.android-app-size-diff-utils</a></li></ul><p>The extension is cross-platform compatible so it is can be used on Windows, Linux, or Mac agents / runners. We are open for community contributions (through GitHub PRs) and requests to expand support (through GitHub issues) for additional app size metrics, reporting formats, and features.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6f886b88a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/microsoft-mobile-engineering/measuring-android-app-size-in-ci-c6f886b88a3">Measuring Android app size with each change</a> was originally published in <a href="https://medium.com/microsoft-mobile-engineering">Microsoft Mobile Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CI / CD at SwiftKey (Part 3)]]></title>
            <link>https://medium.com/microsoft-mobile-engineering/ci-cd-at-swiftkey-part-3-7e27f4ebb4e?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e27f4ebb4e</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Wed, 26 May 2021 14:53:08 GMT</pubDate>
            <atom:updated>2021-06-07T09:35:57.743Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This is the third part of our multi-part series. You can find the previous part below. In this article, we will cover how we leverage various Azure Pipeline features to enforce our release processes.</blockquote><p><a href="https://medium.com/microsoft-mobile-engineering/ci-cd-in-swiftkey-part-2-860768a6e871">CI / CD at SwiftKey (Part 2)</a></p><p>We use several Azure DevOps features across all our pipelines. In this article, we will discuss how we leverage some of these features to reliably enforce our release processes. But first, let us start with a quick overview of SwiftKey’s release process.</p><h3>SwiftKey’s release process</h3><p>There are 3 variants of our SwiftKey Android app that go through our release process at a 2-week cadence. The variants are:</p><ul><li><strong>Cesar</strong>: Our dogfood variant for Microsoft employees only</li><li><strong>Beta</strong>: Public beta which has its own <a href="https://play.google.com/store/apps/details?id=com.touchtype.swiftkey.beta">Google Play Store listing</a></li><li><strong>Market</strong>: The main variant of the app with <a href="https://play.google.com/store/apps/details?id=com.touchtype.swiftkey">over 500 million downloads</a></li></ul><p>Every two weeks, we release a sprint’s worth of work to Cesar* and this rolls out the app to all Microsoft employees who have opted-in. Once we are confident that everything is functioning as expected, we update our Beta variant on the Play Store. After monitoring the stability of Beta, we roll out to 1% of our Market users — incremental rollouts are important for Market variant because we noticed that users who opted to install the Beta variant tend be on the latest hardware so they are not very representative of the Market user base. If we are happy with the state of the release from the 1% rollout, we increase the rollout to 99% and eventually 100% of our user base. Rolling out to 99% first gives us the opportunity to abort the release before going to most of our users should we detect any anomalies that did not show up in earlier stages.</p><p><em>*We also do mid-sprint releases for Cesar. However mid-sprint releases do not go through the full release cycle to public users.</em></p><h3>Release process in code — Multi-stage pipeline</h3><p>The whole release process we described in the previous section is coded into a single <strong>multi-stage pipeline</strong>. Within each stage we have one or more jobs with their own dependency graph. This pipeline gives us a clear overview of the state of release for any given version of our app. Having an overview across multiple app versions is important to us because at any given time we have between 2 to 3 versions of the app in different stages of our release pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q0x6-K2xjiPeqO08Wl-2zA.png" /><figcaption>Using multistage pipeline feature we can defined our release process in code. This reduced the scope for human error and gives a visual overview of the current stage of each release.</figcaption></figure><h3>Parallel vs Sequential jobs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*IekKc-8i8eh07td4dN07DQ.png" /><figcaption>Using a combination of Parallel and Sequential jobs we get a balance between speed and reliability</figcaption></figure><p>Our release pipeline starts with the <em>build</em> stage. First, we perform some <em>prebuild</em> <em>checks</em> that make sure we are building the correct branch and version number etc. We setup our job dependencies so that <em>Build</em> jobs run after <em>Prebuild checks</em> and only if it passes. Once that has passed, all variants are built in parallel.</p><blockquote>ADO’s built-in checkout task makes sure that each job in a pipeline checks out the same commit. This eliminates the risk of working on different commits in each job.</blockquote><h3>Manual Approvals</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0UKHhsdkUIyFXOK1WYMClg.png" /><figcaption>Rolling out the app to each stage is gated using manual approvals. This allows us to pause the pipeline run. Developers manually check different data sources and look for anomalies in the rollout of the previous stage. This gives a chance to manually approve or reject the rollout.</figcaption></figure><p>After executing a stage, the release pipeline will pause and wait for manual approval before proceeding with the next stage. This is important because we always wait multiple days for users to update the app and receive the latest data to decide if it is safe to proceed to the next stage. If we notice any issues with the latest roll-out, we can reject it at the manual gating and the pipeline would halt the release from proceeding to any of the next stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eaXwQtR3WI9CLoXBDlgKTQ.png" /><figcaption>Manual gating can be configured for approvals from a group or individuals</figcaption></figure><h3>Manual Validations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZpIMsX8x21WaOBFstAI4g.png" /><figcaption>Manual validations provide a pipeline run within a single stage (compared to manual approvals which pauses between stages).</figcaption></figure><p>Within each rollout stage, we have 3 jobs. The first of which, named <em>Run release tests</em>, runs tests that verify critical metrics such as crash rates, telemetry events health, number of users, etc. for the rollout from the previous stage. If any of the health metrics deviate from the expected range, the second job, titled <em>Manually confirm release</em>, in the stage pauses the current stage for a manual review. At this point, we can either approve to proceed with the release or abort the whole release. If all metrics are healthy, the pipeline automatically proceeds to the <em>publish</em> job in that stage.</p><h3>YAML based config</h3><p>On Azure Pipelines we can configure a pipeline entirely using Classic UI (GUI editor view) or define a pipeline config using YAML files. We use YAML based config for almost all our pipelines. This has several advantages:</p><ul><li><strong>Version control: </strong>Each commit has its own version of config so we don’t have to keep a single config that works for all versions of the app (as we may have to when using UI based configuration).</li><li><strong>Code reviews: </strong>The pipeline config lives in the repository alongside the rest of the code so all changes go through the same review process as the rest of the codebase.</li><li><strong>Reusable: </strong>We can define the pieces of config once and reuse it multiple times.</li></ul><h3>Templates for config re-use</h3><p>We use the templates feature on ADO extensively and maintain templates for commonly performed tasks, jobs or stages. Templates also support parameters. One commonly reused logic for Android teams can be spinning an emulator.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8ad59b567bf54b26b5dddbb2275c8461/href">https://medium.com/media/8ad59b567bf54b26b5dddbb2275c8461/href</a></iframe><h3>Dashboards</h3><p>We use dashboard to monitor the state of different pipelines at a glance. Azure dashboard comes with support for a plethora of widgets. The widgets are highly configurable and we use them to monitor the state of pipelines on specific branches. There are many other scenarios that can be tracked using dashboards. Checkout the <a href="https://docs.microsoft.com/en-us/azure/devops/report/dashboards/overview?view=azure-devops">dashboards documentation</a> for a more comprehensive overview.</p><h3>Next Up</h3><p>In the next article in this series, we will discuss about our infrastructure improvements using self-hosted agents to address stability and scalability of agents and emulators, our learnings and future plans.</p><p><a href="https://medium.com/microsoft-mobile-engineering/ci-cd-at-swiftkey-part-4-bfe10d7f9f03">CI/CD at SwiftKey (Part 4)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e27f4ebb4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/microsoft-mobile-engineering/ci-cd-at-swiftkey-part-3-7e27f4ebb4e">CI / CD at SwiftKey (Part 3)</a> was originally published in <a href="https://medium.com/microsoft-mobile-engineering">Microsoft Mobile Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CI / CD at SwiftKey (Part 2)]]></title>
            <link>https://medium.com/microsoft-mobile-engineering/ci-cd-in-swiftkey-part-2-860768a6e871?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/860768a6e871</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Wed, 28 Apr 2021 15:14:50 GMT</pubDate>
            <atom:updated>2021-06-02T15:54:24.589Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This is the second part of our multi-part series. You can find the previous part below. In this article, we will cover the building blocks of Azure Pipelines and how we set up agents within the SwiftKey Android team.</blockquote><p><a href="https://medium.com/microsoft-mobile-engineering/ci-cd-in-swiftkey-part-1-30e283f6068f">CI/CD at SwiftKey (Part 1)</a></p><p>Let us start with some key concepts of Azure Pipelines.</p><h3>Key concepts</h3><p>If you are familiar with how Azure Pipelines work, feel free to jump ahead to the <strong><em>SwiftKey Agents setup</em></strong> section below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V6YtR_Lrqfk4f4lOeiHwgg.jpeg" /><figcaption>An overview of key concepts of Azure Pipelines</figcaption></figure><ul><li>A <strong>trigger</strong> tells a pipeline to run.</li><li>A <strong>pipeline </strong>is made up of one or more stages. A pipeline can deploy to one or more environments.</li><li>A <strong>stage </strong>is a way of organising jobs in a pipeline and each stage can have one or more jobs.</li><li>Each <strong>job </strong>runs on one agent. A job can also be agentless.</li><li>An <strong>agent </strong>runs a job that has one or more steps.</li><li>A <strong>step </strong>can be a task or script and is the smallest building block of a pipeline.</li><li>A <strong>task </strong>is a pre-packaged script that performs an action, such as invoking a REST API or publishing a build artifact.</li><li>An <strong>artifact </strong>is a collection of files published by a run.</li></ul><p>Azure Pipelines come with certain built-in tasks to enable basic build and deployment scenarios. The full <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/index?view=azure-devops">catalogue of built-in tasks can be found here</a>. Visual Studio Marketplace has a plethora of additional custom extensions from Microsoft or 3rd Parties. Installing a custom extension, expands the task catalogue in your own Azure DevOps (ADO) subscription and it requires a security approval from the subscription admin.</p><h3>Azure Pipeline Execution</h3><p>This is a high-level overview of the series of events that take place in executing a pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDywC3QHNB9apzKTeNz4jQ.jpeg" /><figcaption>Series of events that happen between starting a pipeline run to reporting the results back.</figcaption></figure><ol><li><strong>Start a pipeline: </strong>Either a developer or one of the trigger events starts the pipeline on Azure DevOps (ADO).</li><li><strong>Agent lookup: </strong>ADO looks at the pipeline configuration to find all jobs that can run in parallel and finds a suitable agent for each job based on the demands specified in the job configuration.</li><li><strong>Submit job: </strong>Once an agent is allocated, ADO submits that job to the agent. Every job is executed on an agent except agentless jobs which run on the ADO server.</li><li><strong>Job execution: </strong>Agent executes each step defined in the job sequentially and report the results back to ADO.</li><li><strong>Logs and artifacts: </strong>ADO gathers all the execution logs from each step and artifacts in every job and makes them accessible through ADO.</li></ol><h3>Agents on Azure Pipelines</h3><p>An agent on Azure Pipelines is the entity on which jobs are executed. An agent can be a physical machine, virtual machine or a docker container. Agents are grouped into agent pools. Broadly there are two types of agent pools: Microsoft-hosted agents and Self-hosted agents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4QjSft4GqJ8milE2FNwPDQ.png" /><figcaption>There are two types of agent pools on Azure Pipelines. Both of them connect to the ADO server.</figcaption></figure><h4>Microsoft-hosted agents</h4><p>These are managed entirely by Microsoft, so software updates and maintenance are taken care of. These agents are re-imaged between each job so we can expect clean and predictable state for each job. They come pre-installed with commonly used tools and packages. At the time of writing, these agents have the following limitations:</p><ul><li>Custom packages need to be installed at runtime*</li><li>Run on Azure DSv2-series VMs</li><li>10 GB of storage</li><li>360 mins execution time limit</li></ul><p>*Microsoft-hosted agents based on Windows 2019 and Ubuntu <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/container-phases?view=azure-devops#hosted-agents">support running jobs in docker containers</a>. This could speed up jobs that depend on installing custom packages.</p><h4>Self-hosted agents</h4><p>ADO supports deploying an agent pool where the agents are entirely self-managed. These agents can be based on Windows, Linux, or Mac operating systems. Users have full control over how these agents are built and configured so, it is possible to:</p><ul><li>Pre-install any custom packages</li><li>Use more-powerful machines</li><li>Add agents to internal networks (useful if certain resources are available only over internal network)</li><li>Host agents on-premises to attach physical devices such as Android phones</li></ul><h3>SwiftKey Agents setup</h3><p>At SwiftKey we need agents with different capabilities as we discussed in the part 1 of this series. Our agents are broadly divided into three categories:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HmI0bdenu1mnAnPnWTGe2g.png" /><figcaption>Overview of different types of agent pools used at SwiftKey and their ownership divided between Android and Infrastructure team.</figcaption></figure><h4><strong>Microsoft-hosted agents</strong></h4><p>These agents are managed by ADO. We use them for build jobs which use only the pre-installed packages. Jobs that run on these agents include builds for open-source repositories, and builds that are not time critical.</p><h4><strong>Self-hosted agents in Cloud</strong></h4><p>These agents are fully managed by us and contain custom packages that are required for certain jobs. These agents are Docker containers deployed on Azure Cloud Infrastructure. We use these agents for jobs that have at least one of the following requirements:</p><ul><li>Need an emulator</li><li>Need custom packages</li><li>Need more memory or CPU</li></ul><p>Jobs that typically run on these agents include Android nightly tests, and APK builds.</p><h4><strong>Self-hosted agents on-premises</strong></h4><p>These agents are also fully managed by us, containerised using the same image as the <em>Self-hosted agents in Cloud</em>. These agents are used for jobs that have at least one of the following requirements:</p><ul><li>Need a physical device</li><li>Need to access resources available only on the internal network</li></ul><p>Jobs that run on these agents are performance tests, smoke tests etc.</p><h4><strong>Config ownership</strong></h4><p>As shown in the figure above, the Android team now owns bigger part of our CI/CD infrastructure. This allows us to rapidly iterate on changes to the agents and their configurations. Our Cloud Infrastructure (CLI) team owns the infrastructure which deploys agents following the configuration defined by the Android team.</p><h3>Next Up</h3><p>In the next article in this series, we will discuss different Azure Pipeline features and how we leveraged them in our CI / CD processes.</p><p><a href="https://medium.com/microsoft-mobile-engineering/ci-cd-at-swiftkey-part-3-7e27f4ebb4e">CI / CD at SwiftKey (Part 3)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=860768a6e871" width="1" height="1" alt=""><hr><p><a href="https://medium.com/microsoft-mobile-engineering/ci-cd-in-swiftkey-part-2-860768a6e871">CI / CD at SwiftKey (Part 2)</a> was originally published in <a href="https://medium.com/microsoft-mobile-engineering">Microsoft Mobile Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cryptocurrencies: Workings and Value proposition]]></title>
            <link>https://medium.com/plaincrypto/cryptocurrencies-workings-and-utility-dbe04518b6f0?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbe04518b6f0</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[utilities]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[value-proposition]]></category>
            <category><![CDATA[usefulnes]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Fri, 15 Jan 2021 20:24:50 GMT</pubDate>
            <atom:updated>2021-02-06T12:21:04.843Z</atom:updated>
            <content:encoded><![CDATA[<p>This post is part of a series. Checkout the previous chapter to understand how blockchain works — the technology upon which cryptocurrencies are built.</p><p><a href="https://medium.com/cryptosimplified/how-blockchain-works-4b98f167d10e">How blockchain works — Crypto Simplified 2.0</a></p><p><strong>Cryptocurrency</strong> is a digital or virtual currency that is secured by cryptography. They are by design, nearly impossible to counterfeit or double-spend. They are generally not issued by any central authority, making them theoretically immune to interference by central banks or governments. Currently there are 100s of cryptocurrencies in circulation and new ones are being added on a regular basis as the barriers to deploying a cryptocurrency are lower than ever.</p><p>This post will cover the broader value proposition of cryptocurrencies and future posts in this chapter will selectively cover each of the top cryptocurrencies — how they work, their utility, and value creation.</p><h3>Valuation</h3><p>Crypto<strong><em>currencies </em></strong>are not widely accepted as a form of payment by highstreet vendors. The prices of food, clothing and other everyday utilities are quoted in fiat currencies so it easier to understand the value of a single unit of a fiat currency — in terms of the utility derived from products they can fetch. While progress is underway to facilitate transacting with high street vendors using cryptocurrencies, the prices are still quoted in fiat and generally a <em>crypto-to-fiat conversion</em> takes place at the point of sale. But for now, cryptocurrencies are not very ‘currency-like’ — hence they are often referred as “crypto assets”. The value asserted, in fiat terms, to a single cryptocurrency can vary widely from <strong>zero </strong>to<strong> some finite number </strong>depending on whom we ask. The valuations of cryptocurrencies are often highly volatile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0CKQBiacWuTd8RoYLdDWQ.png" /><figcaption>Crypto assets are generally more volatile when exchanging with fiat currencies or services</figcaption></figure><p>Beyond these volatile valuations there are cryptocurrencies that aim to offer meaningful utility. Utilities that could one day make their valuation more clear and justified — whatever that number might be. The general populous are still deeply divided on how to value cryptocurrencies, so we will focus on utility and let the audience decide how they value this utility.</p><h3>Utility</h3><p>Almost all public blockchains have at least one native cryptocurrency. The native currency is the ‘legal’ tender to pay for services offered on that blockchain — very similar to how countries have a fiat-currency as legal tender to pay for goods and services. Here are some popular blockchains and their native cryptocurrencies:</p><ul><li><strong>Bitcoin</strong> — Bitcoin (BTC)</li><li><strong>Ethereum</strong> — Ether (ETH)</li><li><strong>RippleNet </strong>—Ripple (XRP)</li><li><strong>Zilliqa</strong> — ZIL Token (ZIL) and Governance ZIL (gZIL) — some blockchains have more than one native currency.</li></ul><p>Let’s consider the top 2 public blockchains and the utility of their native currency, asset or token — also referred to as <strong>token economics.</strong></p><p><strong>Bitcoin</strong> is the first and by far the largest blockchain network in terms of allocated computational resources. At the time of this writing, the network is running at152 EH/s — that’s <em>152,000,000,000,000,000,000 hashes per second!*</em> To put in plain terms, anyone aiming to undermine the security of the Bitcoin network would need to consistently compute more than 152 EH/s — that’s <a href="https://www.coindesk.com/bitcoin-network-out-muscles-top-500-supercomputers">at least <strong>150 times faster than the top 500 supercomputers</strong></a> in the world, <em>combined</em>!</p><blockquote>*The importance of using hashes per second as a metric to measure Bitcoin network capacity will become clear in a Bitcoin specific post in future.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_gGs6fEHOt-IA8JB-5EXNg.png" /><figcaption>Map shows concentration of reachable Bitcoin nodes found in countries around the world.</figcaption></figure><p>We are now living in a world where even the top technology companies and government organizations are falling victims to nation state sponsored cyber attacks.</p><p><a href="https://en.wikipedia.org/wiki/2020_United_States_federal_government_data_breach">2020 United States federal government data breach</a></p><p>Cyber security is paramount and truly scarce right now. Bitcoin offers, among other propositions, a secure network free of interference from anyone and resistant to cyber attacks by design. The <strong>security guarantees of transacting on the Bitcoin network using its native currency is a great utility for any transactions that could benefit from it </strong>— most likely high value transactions. There are more utilities atop the strong security benefits and this will be covered in a post exclusive to Bitcoin.</p><p><strong>Ethereum</strong>, the second biggest blockchain by market capitalization, took the ideals established by Bitcoin and added functionality to support deploying smart contracts on the blockchain. This allows developers to build decentralized applications (DApps) that act as a interface between end users and the smart-contracts running on the Ethereum blockchain. Essentially, the <strong>Ethereum network aims to be the world computer.</strong></p><blockquote>A <strong>smart contract</strong> is a computer program or a transaction protocol which is intended to automatically execute, control or document legally relevant events and actions according to the terms of a contract or an agreement.</blockquote><p>To understand the true potential of a programmable blockchain like Ethereum, we should look at how services like Google, Amazon, Netflix or any internet application for that matter work. These applications must be hosted somewhere and typically developers pay to cloud services such as AWS, Azure or Google Cloud, to rent the infrastructure. The availability of these applications is limited by the underlying infrastructure which can and has failed time and again, leading to outages of many services.</p><ul><li><a href="https://www.theverge.com/2020/11/25/21719396/amazon-web-services-aws-outage-down-internet">Prolonged AWS outage takes down a big chunk of the internet</a></li><li><a href="https://en.wikipedia.org/wiki/2020_Google_services_outages">2020 Google services outages</a></li></ul><p>Ethereum smart contracts can run on any node on the Ethereum network and have virtually no down time. Whenever users interact with the blockchain using a DApp, they pay a fee for running the smart contract. These fee go to the node that executed the smart contract. Fees are denoted in Ether (ETH), the native currency of the Ethereum blockchain. This essentially gives utility to the cryptocurrency — a medium of payment for executing a contract on blockchain. Drawing a stark parallel to how developers pay cloud services in fiat-currencies for hosting their applications. This utility creates demand for Ether among the users of smart contracts.</p><p>There are many other blockchains and even more utilities for each of their native currencies. We will cover them in greater detail in dedicated articles. The goal of this post is to briefly discuss the utility of at least the top 2 cryptocurrencies and set the stage to talk about how different cryptocurrencies work.</p><blockquote>The ideas discussed in this post are by no means an endorsement or disapproval of the financial valuations of any cryptocurrency.</blockquote><blockquote>If you liked this post, please consider showing your support through <strong>claps</strong>👏 (medium allows upto 50 claps per person) and <strong>sharing</strong>. See you again on this channel soon!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbe04518b6f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plaincrypto/cryptocurrencies-workings-and-utility-dbe04518b6f0">Cryptocurrencies: Workings and Value proposition</a> was originally published in <a href="https://medium.com/plaincrypto">Plain Crypto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How blockchain works]]></title>
            <link>https://medium.com/plaincrypto/how-blockchain-works-4b98f167d10e?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b98f167d10e</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[distributed-ledgers]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ledger]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Thu, 17 Dec 2020 15:58:13 GMT</pubDate>
            <atom:updated>2021-02-06T12:19:56.106Z</atom:updated>
            <content:encoded><![CDATA[<p>The first widely adopted implementation of Blockchain was designed to facilitate the invention of Bitcoin — a decentralized digital currency. More details around the circumstances of its creation are discussed in the previous post, linked below.</p><p><a href="https://medium.com/cryptosimplified/why-blockchain-was-created-crypto-simplified-1-0-b8cf510af75f">Why blockchain was created — Crypto Simplified 1.0</a></p><p>Before decentralized digital currencies and blockchain technology came along, the financial system was almost entirely managed by central entities such as Banks and other financial institutions. All transactions are processed and recorded in what’s commonly referred to as a <strong>ledger</strong>.</p><h3><strong>Ledger</strong></h3><p>A ledger, by definition, is a book or other collection of financial accounts. There are many ways to represent a ledger but for the sake of simplicity, imagine ledger as an <strong>ordered list</strong> of transactions for a given account as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ufmsmMmMoj4xZLxUueMNHg.png" /><figcaption>An example bank statement which could be thought as a form of ledger — all transactions on an account are recorded in the order they happen and balance updated after each transaction.</figcaption></figure><h3>Centralized Ledgers</h3><p>In the current system, this ledger is maintained by a central entity — such as a bank. Each transaction requires an interaction with the central ledger to verify its validity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uk82X3J4NumaMH90IRmNQQ.png" /><figcaption>Centralized ledger is maintained by a single entity</figcaption></figure><p>While this is simple by design, it has its drawbacks — most notably the following:</p><ul><li><strong>Loss of control: </strong>Asset needs to be transferred to central entities; users lose control of their data. Under some circumstances, users can be denied access to assets.</li><li><strong>Hackable: </strong>Centralized systems are more susceptible to hacks. It is easier to attack a single entity than commandeering multiple entities simultaneously.</li><li><strong>Single point of failure: </strong>Downtime in a central system can compromise the availability of the ledger to all users.</li></ul><h3>Distributed Ledgers</h3><p>Distributed ledgers could be thought of as having a copy of the ledger <strong>replicated, maintained and synchronized by multiple entities</strong> — individuals or institutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNyl4a9aPKeZVbL1jx_Dnw.png" /><figcaption>Distributed ledger is managed by multiple entities participating in the network</figcaption></figure><p>Moving from a centralized to distributed ledger requires a fundamentally different approach to how certain features of a ledger are implemented. Some of these aspects are:</p><ul><li><strong>Accounts: </strong>an abstract wallet that hold assets controlled by a user.</li><li><strong>Transactions: </strong>how users transfer assets between accounts.</li><li><strong>Privacy: </strong>the identity and data of the parties transacting on the ledger should be protected.</li><li><strong>Consensus: </strong>refers to how the system comes to an agreement on the state of the ledger.</li><li><strong>Security: </strong>to prevent illegitimate changes to the ledger by malicious actors.</li><li><strong>Scalability: </strong>Scalability is essential for ubiquitous adoption of any ledger.</li><li><strong>Incentives: </strong>are what encourages different parties to allocate resources towards maintaining the system.</li></ul><p><strong>Blockchain</strong> is one way to implement a distributed ledger. It is easier to understand the workings of blockchain by broadly examining its structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VQzPXSICsNBo092zwa1Ayw.png" /><figcaption>High-level structure of a blockchain</figcaption></figure><ul><li><strong>Transactions: </strong>A transaction is the atomic unit of a blockchain system — Homer sending $3 to Apu is one example of a transaction. Transactions form the basis for any ledger.</li><li><strong>Blocks: </strong>A set of transactions is grouped into what can be referred to as a <em>block</em>. New <em>blocks</em> are minted to accommodate the latest set of transactions.</li><li><strong>References: </strong>Each newly minted block contains a reference to the previous block. These backward references within blocks create a virtual chain of blocks — hence the name <strong>Blockchain </strong>🤯. The importance of these references will become clear later in the context of security.</li></ul><p>As evident from the high-level structure, a blockchain uses a slightly different format (data structure in computer science terms) to record transactions in contrast to a traditional ledger. The need for this architecture will become in the next sections. The diagram intentionally omits certain crucial aspects of the blockchain design — these are covered later on.</p><h3>Transactions</h3><p>Transacting on blockchain has certain similarities to the traditional banking system. When Alice opens an account with the bank, she gets an <em>account number</em> and a <em>password</em>. With blockchain, Alice uses a crypto wallet to generate a <em>public key</em><strong> </strong>and a <em>private key — </em>these are elements taken from <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">asymmetric cryptography</a> and the keys always come in pairs.</p><blockquote><strong>Asymmetric cryptography</strong> is used extensively in many <strong>Internet protocols</strong> which stood the test of time. Whenever a webpage is loaded securely (starts with https:// in the url), asymmetric crypto is working its magic behind the scenes.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rS1mcMg5fDeDHZtJWEPAZw.png" /><figcaption>Comparing the elements of traditional banking to blockchain</figcaption></figure><p><strong>Private key </strong>is kept secret and used for authentication and encryption. This is similar to the role of <em>password </em>or any other form of authentication in the tradition banking. In stark contrast to a password, private keys achieve <em>authentication by digitally signing</em> a piece of information — only those who have access to the private key can sign using it. Unlike the real world hand signatures that are susceptible to forgery, private key signatures are highly improbable to imitate.</p><p><strong>Public key:</strong> is publicly known and essential for identification. Its role is very similar to that of <em>account numbers</em> in traditional banking. It is also used to verify the information signed using the corresponding private key.</p><p><strong>Address: </strong>public key is made up of an extremely long string of numbers. So it is compressed and shortened to form the public <em>address</em>. These are the addresses that appear in the transactions on a blockchain. This is analogous to another way of representing <em>account numbers </em>in traditional banking.</p><p>A transaction is essentially a transfer of ownership of an asset — Homer sending 10 coins to Apu necessitates Homer transferring ownership of 10 coins that he owns, over to Apu. So transactions on a blockchain are largely transferring the ownership of a crypto coin from one party to another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yqCG086SgFQZm3Ryz79Xxg.png" /><figcaption>A transaction is a transfer of ownership of an asset. The current owner of the asset signs the transaction to authenticate the transfer. The signature can be verified by anyone using the sender’s public key.</figcaption></figure><p>For a transaction to be valid, it must be signed using the private key of the current owner of the asset — since only the owner has access to the private key, only they can transfer the asset on to another party.</p><blockquote>The adoption of <strong>asymmetric cryptography</strong> fundamentally allows anyone to verify the signature on a transaction while still limiting the ability to sign a transaction to the party that has access to the private key.</blockquote><h3>Privacy</h3><p>The centralized ledger model achieves a level of privacy by limiting access to transaction information to the parties involved and certain trusted third parties. The necessity to announce all transactions publicly or at least to every node in the network precludes this method. Privacy in blockchains can still be maintained by keeping the addresses anonymous. The public can see that someone is sending an amount to someone else, but without information linking the transaction to anyone in the real world. This is similar to the level of information released by stock exchanges, where the time and size of individual trades is made public, but without telling who the parties were.</p><h3>Consensus</h3><p>Blockchains runs on a distributed network and the entities participating in the network are often dispersed geographically. Since there is always a finite delay in propagating information between the nodes in the network, nodes could occasionally go out of sync — the copies of their ledger do not match.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EyZ10RsUYgaBRLByz6ol3A.png" /><figcaption>Blockchain network nodes could go out of sync</figcaption></figure><blockquote>A <strong>consensus algorithm</strong> is a procedure through which all the entities of the Blockchain network reach a <strong>common agreement</strong> about the present state of the distributed ledger. In this way, consensus algorithms achieve reliability in the Blockchain network and establish trust between unknown parties in a distributed computing environment.</blockquote><p>Malicious nodes in the network could also bring about a similar situation in the network, albeit intentionally. Therefore, all implementations of blockchain must incorporate a strategy to reach consensus. There are many implementations of blockchain — Bitcoin, Ethereum, Litecoin, and Polka dot just to name a few, and each of them have their own consensus mechanism. While there are many consensus algorithms, the popular ones are:</p><ul><li><strong>Proof of Work (PoW): </strong>The central idea behind this algorithm is to solve a complex mathematical puzzle and give out a solution. This mathematical puzzle requires a lot of computational power and thus, the node who solves the puzzle as soon as possible gets to create the next block. The solution, once found, can be easily verified by any node.</li><li><strong>Proof of Stake (PoS): </strong>In this, nodes invest in the coins of the system and lock up some of their crypto assets as stake. After that, all the validator nodes will start validating the blocks. The specifics of the node selection and block creation process can vary per implementation. But the central idea is that <em>all nodes have their assets at stake to act honestly</em>.</li></ul><p>More details on how different consensus algorithms work will be covered in future posts.</p><h3>Security</h3><p>The records on a blockchain are secured through cryptography. Users authenticate transactions with digital signatures using their own private key. If a transaction is altered, the signature will become invalid and the participants in the network can detect it. Editing a past transaction and signing it again accurately is also not possible as blocks are immutable by design. Immutability is baked into the design through the use of cryptographic hash functions when creating block references.</p><blockquote>A <strong>cryptographic hash function</strong> (CHF) is a mathematical algorithm that maps data of arbitrary size (the “message”) to a fixed size output (the “hash”). It is a one-way function — a function which is practically infeasible to invert.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U8h1Oa6B7IuxGzQc9DeRbA.png" /><figcaption>Blocks contain a references to previous block — built using cryptographic hash function</figcaption></figure><p>The hash functions adopted by blockchain implementations are such that a small change to the contents will change the hash value so extensively that the new hash value is completely uncorrelated with the old hash value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*kux-gJWHVChQM8JA.png" /><figcaption>A small change in input products a completely different hash output</figcaption></figure><p>Malicious nodes in the network is a widely discussed phenomenon in any blockchain. Since each transaction has to be signed with the private key of the owner of the asset, the nodes cannot arbitrarily transfer assets to themselves. They can however double spend their own assets!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c5QZiSTpFV9cP728rvvVQg.png" /><figcaption>Double spending — when the same asset is spent more than once.</figcaption></figure><p>For example: Mr. Burns, can operate a malicious nodes in the network. Burns can transfer the assets to Lisa, receive the services in return, and then create a new block with a transaction transferring the same assets to Bart. This is referred to as the <strong>Double spend problem</strong>. The attacker can do this by creating a new branch of block(s)— referred to as <strong>forking the chain</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QHvjp1oWR-vS3Ji0mkY27A.png" /><figcaption>Double spend attempt to create a branch or fork of the blockchain</figcaption></figure><p><strong>Branches are not acceptable legal states for a blockchain</strong> and all implementations have mechanics to avoid or eventually resolve branches by discarding all but one branch that will define the new state of the blockchain. In the example of Mr. Burns, it resolves to keeping only one of the 2 conflicting transactions — avoiding double spend. Depending on the implementation and resources, an attacker could convince the network to discard legitimate transactions that are deemed as confirmed by the users. More on these attacks in future posts in the context of each implementation.</p><p>Bugs and other systematic errors are also possible in a blockchain, much like in central ledgers.</p><h3>Scalability</h3><p><a href="https://medium.com/vechain-foundation/what-does-scalability-really-mean-in-blockchain-b8b13b3181c6">Scalability in blockchain could mean many things</a> but this section is limited to transaction throughput.</p><blockquote><strong>Transaction throughput</strong> is the rate at which the network can process transactions.</blockquote><p>This number can vary widely depending on the implementation but the early implementations like <a href="https://eprint.iacr.org/2019/416.pdf"><strong>Bitcoin (27 tps)</strong></a>, <a href="https://publik.tuwien.ac.at/files/publik_280601.pdf"><strong>Ethereum (15 tps)</strong></a> have struggled with low throughputs, causing longer than usual delays in confirming transactions — to put this in perspective, <a href="https://usa.visa.com/dam/VCOM/download/corporate/media/visanet-technology/aboutvisafactsheet.pdf"><strong>Visa network can operate at 65,000+ tps</strong></a>. Limits on transaction throughput are related to the fact that blocks in the blockchain are limited in size and frequency — there’s often a limit on how many transactions can be put in a single block and the rate at which new blocks are generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*k7zEOM2fRmNyEVK_.png" /><figcaption>The blockchain trilemma</figcaption></figure><p>The Blockchain Trilemma, <em>termed by Vitalik Buterin (creator of Ethereum)</em>, addresses the challenges developers face in creating a blockchain that is scalable, decentralized and secure — without compromising on any facet. Blockchains are often forced to make trade-offs that prevent them from achieving all 3 aspects simultaneously:</p><ol><li><strong>Decentralized</strong>: creating a blockchain system that does not rely on a central point of control or co-ordination.</li><li><strong>Scalable</strong>: the ability for a blockchain system to handle an increasingly growing number of transactions.</li><li><strong>Secure</strong>: the ability of the blockchain system to operate as expected, defend itself from attacks, bugs, and other unforeseen issues.</li></ol><p>While some developers believe that the blockchain data structure itself has inherent limitations that prevent it from scaling, many architects believe that it is possible to build a blockchain that hits all three targets. More details on where each blockchain fits in this Trilemma will be covered in future posts.</p><h3>Incentives</h3><p>A blockchain runs on the resources provided by the nodes participating in the network. Incentives are what encourage participants to join and contribute to a specific blockchain network. All practical implementations of blockchain incorporate a model for incentives. Commonly adopted models are:</p><ul><li><strong>Block rewards:</strong> The node that mints the next block is rewarded with a defined number of new tokens.</li><li><strong>Transaction fees:</strong> The node that mints that next block takes a transaction fee from all transactions that make up the block.</li><li><strong>Participation reward: </strong>A mix of the earlier two could be combined with aggregating rewards across the network and re-distributing based on the level of participation of each node.</li></ul><p>These are just some examples of straightforward incentive models. There is plenty of on-going research in the area of <a href="https://scholar.google.co.uk/scholar?q=blockchain+incentive+model&amp;hl=en&amp;as_sdt=0&amp;as_vis=1&amp;oi=scholart">Blockchain incentive models</a>. Incentive models are specific to blockchain implementation.</p><p>While this post gives a general overview on how blockchain technologies work, there are numerous other aspects which are unique and specific to individual implementations. Future posts will explore each of these major implementations and cover the concepts in greater detail. The diagram below summarizes all the high level high-aspects of a blockchain transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oQ_Yl9L7MZBet2O3.png" /><figcaption>Summary of high level aspects of a blockchain transaction</figcaption></figure><blockquote><em>I hope you enjoy reading and learning from this series as much as I enjoy writing it. Show your support through </em><strong><em>claps</em></strong>👏 <em>and </em><strong><em>sharing</em></strong><em>.</em></blockquote><p>See you again on this channel soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b98f167d10e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plaincrypto/how-blockchain-works-4b98f167d10e">How blockchain works</a> was originally published in <a href="https://medium.com/plaincrypto">Plain Crypto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Export Trading212 Transactions as CSV]]></title>
            <link>https://pkpio.medium.com/export-trading212-transactions-as-csv-yahoo-finance-298db9892a43?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/298db9892a43</guid>
            <category><![CDATA[export-csv]]></category>
            <category><![CDATA[trading212]]></category>
            <category><![CDATA[yahoo-finance]]></category>
            <category><![CDATA[stocks]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Tue, 01 Dec 2020 13:31:16 GMT</pubDate>
            <atom:updated>2020-12-03T17:25:55.329Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Permanently moved to</em><strong><em> “</em></strong><a href="https://pkp.io/blog/exporting-trading-212-to-yahoo-finance/"><em>Export Trading212 Transactions as CSV</em></a>”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=298db9892a43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why blockchain was created]]></title>
            <link>https://medium.com/plaincrypto/why-blockchain-was-created-crypto-simplified-1-0-b8cf510af75f?source=rss-d72b82d89292------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8cf510af75f</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[fiat-to-crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Praveen Pendyala]]></dc:creator>
            <pubDate>Thu, 26 Nov 2020 19:17:04 GMT</pubDate>
            <atom:updated>2021-02-06T12:21:19.690Z</atom:updated>
            <content:encoded><![CDATA[<p>Blockchain is indubitably one of the greatest technological creations in our time.</p><p>It’s easy to grasp the significance of the Internet — another great technological advancement, because we use it every day in many ways — bringing us morning weather reports to evening entertainment, and everything in between. We realize the power of AI because we experience it everyday — searching online, detecting faces in pictures, and product recommendations. We understand these already ubiquitous technologies because we can associate them to the problems they solve in our day to day life. Blockchain is a relatively young kid in the block, so in order to understand or appreciate it, we have to look at the problems it aims to solve.</p><p>Blockchain is the technology that enables the existence of cryptocurrency. Bitcoin is the first and most popular cryptocurrency, the one for which blockchain was invented. To understand why Bitcoin was created, we have to understand the drawbacks in our current financial system. For the sake of completeness and to get a sense of how we got to the current system, we will take a quick walk along the history of how money evolved over time. If you wish, you may skip the history lesson and jump to <strong>issues with Fiat currencies.</strong></p><h3>Barter System</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*JrsmDNxwHoFHHhglKUQNUQ.jpeg" /><figcaption>Barter system with bilateral trade</figcaption></figure><p>People exchanged goods and services directly with each other. For example a farmer with excess produce of dairy or meat could exchange with a fisherman with a surplus of fish. This was likely the first system to facilitate trade — which is always essential, as no one can be self-sufficient at all times.</p><p>The problem with this system was immediately apparent when there was no one willing to participate on the other side of the trade — trade is bilateral. In our earlier example, if no fisherman wants to trade fish for meat or dairy, the farmer wouldn’t be able to get fish even though there is value for his meat and dairy. Some of these issues could be solved by involving 3 or more parties in a trade, but it gets complicated quickly — like in the board game <a href="https://www.catan.com/game/catan"><strong>Catan</strong></a>.</p><h3>Commodity money</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*5m1Br6Uf6sm_Zgz7.jpg" /><figcaption>Common commodities are used as medium of exchange</figcaption></figure><p>As time passed, people noticed that certain commodities such as sea shells, salt, corn, copper, silver, and gold are rare and always attractive. People began to quote the value of their everyday items in terms of these commodities. For example:</p><ul><li>a sheep is worth 10 sea shells</li><li>a house is worth 50 bags of corn</li></ul><p>This is an improvement over the barter system as people could sell their goods and services for these commodities. And they can buy the goods and services they need using these commodities. The commodities used for trade had certain characteristics: they were widely desired and therefore, valuable. They were also durable, portable, and easily stored. While this opened up more opportunities for trade, there were still issues with the commodities such as:</p><ul><li><strong><em>Deterioration</em>:</strong> certain commodities, like corn, can deteriorate in quality over time</li><li><strong><em>Bulkiness</em>:</strong> Imagine having to go shopping with a cart full of salt</li><li><strong><em>Indivisibility</em>:</strong> some commodities, like seashells, can’t be meaningfully subdivided</li></ul><h3>Coins</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/0*XSiNO7N6ndzWsJpC.jpg" /></figure><p>People became accustomed to the idea of a medium of exchange for goods and services — aka money. Coins were minted with different denominations and this solved most of the problems associated with commodities. Also, the value of the coin is decoupled from its size and this made the process of moving money around easier. This innovation made it easier and faster to conduct trade.</p><h3>Paper money</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*wU3Pdj-8Zo6AbSJU.jpg" /></figure><p>Merchants and traders were looking for ways to do larger transactions without having to carry large amounts of metal coins, so paper money was created. Bank notes were issued and backed by storing coins of equal value. Anyone holding a bank note could approach the bank and exchange for its value in coins.</p><blockquote>The modern paper money such as Dollar, Euro, and Pound are no longer backed by any physical commodity or asset.</blockquote><p>Paper money is now issued by a central financial entity in each country and <strong>money derives its value from the trust we place in these institutions</strong>. This is called <strong>Fiat money</strong>.</p><h3>Plastic Money</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*_lhHavwDKXAM94Rk.png" /></figure><p>Plastic money was an improvement over paper money. It made it easy to transact on large or small amounts alike. It also opened up a plethora of new possibilities such as credit cards that made short term borrowing easier. Coupled with the innovations on the internet, it created products and services that wouldn’t have been possible without it.</p><p>Plastic money is just a representation of paper money that offers convenient means to transact with ease. The fundamental issues, discussed in the next section, apply to all forms of fiat currencies — such as US Dollar, Euro, Pound.</p><h3>Issues with Fiat currencies</h3><p>To understand the issues with fiat currencies, we need to take a closer look at its definition.</p><blockquote>Fiat money is a government-issued currency that isn’t backed by a commodity such as gold.</blockquote><p>Fiat money gives central banks greater control over the economy because they can control how much money is printed. Central banks printing too much over a short period has led to a total economic collapse time and again.</p><ul><li><a href="https://en.wikipedia.org/wiki/Hyperinflation_in_the_Weimar_Republic">Hyperinflation in Germany in 1920s</a></li><li><a href="https://en.wikipedia.org/wiki/Hyperinflation_in_Zimbabwe">Hyperinflation in Zimbabwe in 2008</a></li><li><a href="https://en.wikipedia.org/wiki/Hyperinflation_in_Venezuela">Hyperinflation in Venezuela in 2016</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0QEA6XZ9eQEyNw5a.jpg" /><figcaption>Zimbabwe banknotes ranging from 10 dollars to 100 billion dollars printed within a one-year period</figcaption></figure><p>Just in the last century there were <a href="https://en.wikipedia.org/wiki/Hyperinflation#Notable_hyperinflationary_periods">13 instances of Hyperinflation</a> — Austria, Bolivia, Brazil, China, Germany, Greece, Hungary, Malaya, North Korea, Peru, Poland, Philippines, Soviet Union, and Venezuela. Through no fault of their own, people in these countries had seen their money erode in value as the <strong>price of commodities doubled every 14.82 hours</strong> (Hungary, July 1946)! All because the central banks hoped to print their way out of trouble. Hyperinflation is an extreme scenario and is typically associated with some form of War.</p><p>During times of crisis — be it war, economic collapse, or pandemic such as the one we are in now, central banks issue unprecedented amounts of money in a short span to support and boost the recovery of the economy. As cool (and unwise) as it would be, this newly created wealth is <em>not dropped from a blimp.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmrvD1QpJyYU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmrvD1QpJyYU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmrvD1QpJyYU%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/42f99adc10fb1f9ad33a87b9f1ace668/href">https://medium.com/media/42f99adc10fb1f9ad33a87b9f1ace668/href</a></iframe><p>The government decides which institutions will receive a bigger chunk of that wealth — in the name of aid, bailout or a rescue package. In the 2008 financial crisis, it was bailing out banks, despite their own faults for the situation — as these banks were “<em>essential to keep the financial system running.</em>” A similar situation in the 2020 crisis. In the US, <a href="https://www.visualcapitalist.com/the-anatomy-of-the-2-trillion-covid-19-stimulus-bill/">large corporations get 25% of the $2 trillion stimulus package</a>. Fiat money gives this unprecedented power to the governments or central banks to do such massive redistribution of wealth — further widening the income gaps in the society, reinforcing the saying:</p><blockquote>The rich get richer and the poor get poorer</blockquote><h3>Bitcoin</h3><p>The issues related to the handling of the 2008 financial crisis was the reason Bitcoin was created. <strong>On 3 January 2009, the bitcoin network came into existence with Satoshi Nakamoto mining the genesis block of bitcoin</strong>. Embedded in this block was the text:</p><blockquote>The Times 03/Jan/2009 Chancellor on brink of second bailout for banks.</blockquote><p>To summarize, Bitcoin was created in the hopes of building a new form of money that is not controlled by a single central entity — such as the central banks. A system where no single person, company or even government has the capacity to manipulate the supply of money. Bitcoin runs on a fully decentralized system. New coins are issued at a defined rate and are distributed in a well-defined structure.</p><h3>Issues with Bitcoin</h3><p>Like any currency, Bitcoin has its own set of problems:</p><ul><li><strong>Not widely accepted:</strong> There are not many merchants — online or offline, that accept Bitcoin as a mode of payment. This is like the classic <a href="https://en.wikipedia.org/wiki/Chicken_or_the_egg">Chicken-and-egg</a> problem. This applies to any currency — digital or otherwise, in its infancy. While fiat currencies could draw upon the trust people have in their governments to enjoy wider adoption. The case for digital currencies is yet to unfold.</li><li><strong>No valuation guarantee:</strong> Since there is no central authority backing Bitcoins, no one can guarantee its minimum valuation. <em>Bitcoin relies on mathematical properties to earn trust</em> and its <em>value is linked to its adoption by a growing base of users, merchants, and startups</em>. If a large group of merchants decide to “dump” Bitcoins and leave the system, its valuation will decrease greatly. This will immensely hurt users who have a large amount of wealth invested in Bitcoins. The decentralized nature of bitcoin is both a curse and blessing.</li><li><strong>Volatile valuation:</strong> The value of bitcoin is highly volatile. This makes it harder to use it for exchanging goods and services. For example, if Alice sold a car for 1 bitcoin on 17th Dec 2017 (1 BTC = 19,166 USD) and decided to use that money to pay for the new year party 2 weeks later on 31st Dec 2017 (1 BTC = 13,060 USD), the value of her car sale has eroded significantly (in real dollar terms) in just under 2 weeks!</li><li><strong>Irreversible transactions:</strong> This is both a strength and weakness of Bitcoin. Once a transaction is confirmed* on the Bitcoin blockchain, it is irreversible. In the current banking system, if your card was stolen and used for fraudulent purchases, or you made a purchase and the seller didn’t send the product; it is possible to reverse the transaction. All confirmed transactions with Bitcoin are irreversible so there are <em>no fraud protections</em>.</li><li><strong>Deflation:</strong> The total number of bitcoins is capped at 21 million. This will cause deflation — the value of money increasing over time. Each bitcoin could be worth more and more as the total number of Bitcoins maxes out. This system is designed to reward early adopters. Since each bitcoin could be valued higher with each passing day, people will be more inclined to save it as an asset; rather than spend it like a currency. Despite its initial intentions, this makes it more of a digital asset than a currency. Infact Bitcoin is now often referred to as Digital gold.</li></ul><p><em>*The definition of a confirmed transaction varies per blockchain implementation. More about this in the next post on </em><strong><em>How blockchains work</em></strong><em>.</em></p><blockquote>Not all cryptocurrencies are deflationary. Ethereum, the second largest cryptocurrency <em>does not have fixed supply</em> — <a href="https://ethereum.org/en/whitepaper/#currency-and-issuance">a maximum of 18,000,000 new coins are issued annually</a>.</blockquote><h3>Blockchain</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/0*7Sz0qH1kuzgT_8_0.png" /></figure><p>One major difference between physical and digital forms of money is that a digital token can be duplicated or falsified and spent over and over — called the <strong>Double spend problem</strong>. This applies to both digital versions of Fiat currencies and cryptocurrencies such as Bitcoin. Fiat currencies use a trusted central entity (bank), which keeps a record of how much money each person has and every time they try to transact, their account is checked to make sure they have enough balance before approving the transaction. With Bitcoin there are no central entities that can provide this service so, a novel technology called blockchain was invented to workaround the double spending problem.</p><p>Although blockchain was invented for supporting a new form of decentralized money such as Bitcoin, <strong>the technology can be used for many applications beyond creation of cryptocurrencies</strong>. The original version of the Internet was created to allow multiple computers to communicate on a single network, and today it has evolved into something much bigger than anyone could have imagined. Blockchain has the potential to be something much bigger! The next post will discuss how blockchain works and how it can be used to power many new types of applications.</p><blockquote>I hope you enjoy reading and learning from this series as much as I enjoy writing it.</blockquote><p>See you again on this channel soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8cf510af75f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plaincrypto/why-blockchain-was-created-crypto-simplified-1-0-b8cf510af75f">Why blockchain was created</a> was originally published in <a href="https://medium.com/plaincrypto">Plain Crypto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>