<?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 Vincent Tran on Medium]]></title>
        <description><![CDATA[Stories by Vincent Tran on Medium]]></description>
        <link>https://medium.com/@vncnttrn?source=rss-42ed7cb440b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OwpgQVN5uoakSfG7jqKpIA.jpeg</url>
            <title>Stories by Vincent Tran on Medium</title>
            <link>https://medium.com/@vncnttrn?source=rss-42ed7cb440b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:44:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vncnttrn/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[How To Airdrop Your First Token]]></title>
            <link>https://medium.com/bitfwd/how-to-airdrop-your-first-token-3ba187ff7cbf?source=rss-42ed7cb440b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ba187ff7cbf</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[airdrop]]></category>
            <category><![CDATA[ico]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Vincent Tran]]></dc:creator>
            <pubDate>Fri, 09 Mar 2018 03:28:24 GMT</pubDate>
            <atom:updated>2018-03-09T03:28:24.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dY5vSl2WI5Udsv7pFE-4-w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/ffypGIy5rOs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Erwan Hesry</a> on <a href="https://unsplash.com/search/photos/parachute?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This is the second tutorial in bitfwd’s <a href="https://github.com/bitfwdcommunity/Tutorials">tutorial series</a> where we teach everyday users (yes! that’s you, my dear reader) how to interact with the blockchain. This is a more advanced tutorial and will require more tools than before but I will do my best to walk you through the steps. Let’s begin!</p><p>In trying to be as inclusive as possible, I have made this tutorial extremely thorough. For more advanced users, feel free to breeze through to Step 4, where you learn how to use export balances.</p><h4><strong>A Note On Asking For Help</strong></h4><p>When asking for help, I only have one rule: try to include as much information as possible. (E.g. the contract address, errors that appear in your terminal, your device type.) This way, we won’t need to go back and forth in the comments. Feel free to join our telegram and ask for help there. I’ll reply as soon as I have time.</p><h4><strong>Prerequisites</strong></h4><p>You need to follow <a href="https://medium.com/bitfwd/how-to-issue-your-own-token-on-ethereum-in-less-than-20-minutes-ac1f8f022793">Moritz Neto’s tutorial</a> on how to deploy your own contract.</p><h4>What You Will Learn Today</h4><ol><li>You will learn the basics of how to navigate on the command line.</li><li>You will learn the basics of how to fork and clone repositories on Github.</li><li>You will learn how to install Nodejs through a version manager called NVM.</li><li>You will learn how to use Parity (A Rust implementation of geth) to extract account balances from the Ethereum blockchain.</li><li>You will learn how to run Parity so that you can broadcast transactions locally from your computer.</li><li>You will learn about token decimal size, which appears in every contract.</li><li>You will (finally!) learn about how to prepare the airdropping script to airdrop tokens for you.</li><li>You will also learn how you can implement your own custom airdropping function so you can determine how many tokens each user should be airdropped.</li></ol><h4>Step I: Navigating The Command Line.</h4><p>Whip open a terminal and start by typing in:</p><pre>pwd</pre><p>This stands for “print working directory” and tells you where you currently are. Pick a name for the directory where you want to store your code and type to create the folder. (mkdir = Make directory, catching on?)</p><pre>mkdir &quot;cool-folder-name-here&quot; </pre><p>Now, let’s navigate into the directory using the next command.</p><pre>cd &quot;cool-folder-name-here&quot;</pre><p>This stands for “change directory” and will move your from your current location into the newly made folder. You can verify this by running pwd again. This will be the extent of the terminal commands that you will be learning today but if you want to learn more, check out this <a href="https://courses.cs.washington.edu/courses/cse390a/14au/bash.html">resource</a> as well as the <a href="https://en.wikipedia.org/wiki/Man_page">man pages</a>. As an exercise, try figure out what the “ls” command does.</p><p>Make sure you have git installed as well. You can find the installation files <a href="https://git-scm.com/downloads">here</a>.</p><h4>Step II: Forking &amp; Cloning.</h4><p>Now that we have our terminal ready, we need to get the code onto our computers. This process is called <a href="https://help.github.com/articles/cloning-a-repository/">cloning</a>. Since we might make changes to the code, it is better to clone a <a href="https://help.github.com/articles/fork-a-repo/">fork</a> of the code than the codebase itself. Forking allows us to make modifications to the code without affecting the original repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6HbMhM7AP3x5y3Ysvi7rKw.png" /><figcaption>Learning to fork…</figcaption></figure><p>So log in to Github and visit the code <a href="https://github.com/bitfwdcommunity/Airdropper">repository</a>. In the top right hand corner there’s a fork button that you can click to fork the repository to your account.</p><p>When it finishes forking, you will notice that it has redirected you to your own copy of the repository (you can tell it’s a copy because in the URL, it will have your name in the middle instead of bitfwdcommunity).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UkZzEQooTMb6NYIGDp4B6w.png" /></figure><p>Near the middle right hand side of the screen there is a “clone or download” button that you will click. Make sure you select “Clone with HTTPS.” Copy the link and paste it into the terminal with this command.</p><pre>git clone &quot;paste-the-url-here&quot;</pre><p>When you hit enter, it will prompt you for your username and then your password (use your Github username and password). Note that password’s do not show up when you type them into terminal. When you are finished, it will begin downloading the code repository onto your computer. Once you are done, type the following command:</p><pre>cd Airdropper</pre><p>This will move you into the Airdropper repository where you will run the commands necessary to use this tool. Now open the Airdropper folder in your favourite text editing tool (my favourite is <a href="https://atom.io/">Atom</a>).</p><h4><strong>Step III: Installing Nodejs.</strong></h4><p>This airdropping script runs on Nodejs, which I recommend you install by going through <a href="https://github.com/creationix/nvm">Node Version Manager</a>. The reason we will install Nodejs using NVM as opposed to any other way is because it allows for more sustainable development. NVM allows you to have fine grain control on which node version you are using, which is helpful if you are working on projects with many different node versions as dependencies.</p><p>To install it, you will use the following command</p><pre>curl -o- <a href="https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh">https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh</a> | bash</pre><p>Restart your terminal when you’re done. Now you can install nodejs! You can do this with a simple</p><pre>nvm install node</pre><h4><strong>Step IV: Exporting Account Balances</strong></h4><p>To be able to successfully airdrop our awesome token to others, we must first get a list of all the addresses that we wish to airdrop to. The easiest way to achieve this is by using Parity’s export state function.</p><p>First thing you need to do is install <a href="https://www.parity.io/">parity</a>.</p><p>After you have installed it, you need to sync it up to the block you want to take a snapshot of. This means that if you want to extract all the balances at block 2 000 000, you have to sync to at least block 2 000 000. Note that you must run it with archive and fat-db mode on. The command that you will use to achieve this is:</p><pre>parity -pruning=archive -fat-db=on -chain=ropsten</pre><p>You may use whichever chain you like but in this tutorial we will be using ropsten. To confirm that parity has the correct settings, it will start up with a bunch of configurations showing. There will be a line that says “State DB Configuration”. Check that this says <strong>archive</strong> and <strong>fat-db</strong>.</p><p>The reason we want archive mode and fat-db turned on is because we do not want to prune the state trie where all the balance information is stored. When parity exports the state, it generates the balance by iterating over the state trie. Once you have synced up to the block at which you would like to export state, you can stop syncing parity.</p><p>Let’s assume that we wish our exported balances to abide by the following rules:</p><ol><li>We want balances in block 2 000 000.</li><li>We want balances above 1 000 RtETH</li><li>We want balances below 500 000 RtETH</li></ol><p>Given these rules, we would use the following code:</p><pre>parity export state --chain=ropsten -no-storage -no-code -min-balance=1000 -max-balance=500000 -at=2000000 balances.json</pre><p>This process may take several hours to complete.</p><p>You will discover while doing this that it is important to set a max balance otherwise a few users with enormous balances may end up with all your tokens.</p><h4><strong>Step V: Broadcasting Transactions</strong></h4><p>Broadcasting transactions to the Ethereum network can be done in two ways via a remote node such as <a href="https://infura.io/">Infura</a> or via a local parity mode. Since we will be broadcasting many transactions, it is better to use your own node. If you have synced your parity node using fat-db and with archive mode on, it is syncing much slower than it would if it was in fast mode. To reset your node and get it to warp sync back to the latest state, you can kill the database and then start it up again using the following commands.</p><pre>parity db kill -chain=ropsten<br>parity -chain=ropsten -pruning=fast -fat-db=off</pre><p>Let this run in the background while we prepare the rest of the tools.</p><h4><strong>Step VI: Token Decimal Size</strong></h4><p>Before we get into configuring the Airdropper, I’ll talk a bit about the decimals field in the token contract. The decimals field basically describes how divisible your token will be. The reason this is important is because not all tokens should be divisible (e.g. do you want a divisible “unicorn” token?). The default value for decimals is 18. The impact of the decimals field is that all token values have to take this into account (i.e. have an extra 18 zeroes).</p><h4><strong>Step VII: Preparing The Airdropper</strong></h4><p>Let’s set up the airdropper now. The main file is in index.js. Let’s take a look at lines 18–23, which contain a few variables that we can modify. We will start off by doing a very basic airdrop of 1 token to each user.</p><pre>AIRDROP_QTY refers to the fixed amount of tokens you are dropping to each user. The default value is set at 1.<br>DURATION is the time in between transaction submissions.<br>GAS_LIMIT &amp; GAS_PRICE are the respective limits and prices that you are willing to pay for your transaction. You can check to see how many <a href="https://ropsten.etherscan.io/txsPending">pending transactions</a> there are on etherscan before you estimate how much gas you are willing to pay per transaction. The default value that I have left it at is 5gwei.</pre><p>As an example, if your contract has 1 000 000 tokens, you will need to set the INITIAL_TOKENS value to 1 000 000 000 000 000 000 000 000. (1 000 000 * 10 ^ d, where d is the decimals values in your contract, with 18 being the default value).</p><p>Next, we need to set up our custom config file. Make a new file in the root directory (next to index.js) called “config.js”. It will look something like this …</p><pre>module.exports = {<br>    privateKey: ‘put-your-private-key-here’,<br>    contractAddress: ‘put-your-deployed-contract-address-here’,<br>    abi: ‘put-your-deployed-contract-abi-here’<br>}</pre><p>If you used a seed instead, you can remove the privateKey field and replace it with a seed field and the Airdropper will still work. If you did not keep a copy of your ABI, you will need to recompile the contract in remix and copy the ABI (it’s underneath the bytecode field).</p><p>Once you have created a config.js file as well as finished customising the modifiable fields, you will now be able to airdrop tokens (finally!). Just before we get to it, we’ll go through a final checklist to make sure everything goes smoothly…</p><h4><strong>Airdrop Checklist</strong></h4><ol><li>Fully synced parity node. (You can check what block you are up to and compare it with <a href="https://ropsten.etherscan.io/">etherscan</a>).</li><li>Enough RtETHs on your account with the tokens. You can get more from our <a href="https://faucet.bitfwd.xyz/">faucet</a>. As a ballpark estimate, 3000 transactions at 5gwei each will cost about 0.5 RtETHs (so make sure you have enough!)</li><li>Your account page open on etherscan (on ropsten!) so you can see the pending transactions being broadcast to the ethereum network.</li></ol><p>If you have both of these things, you will be ready to run the Airdropper with the following command.</p><pre>node index.js</pre><p>You will notice that the script will begin to “hang” and at this point you can refresh the ropsten etherscan page and begin to see the pending transactions roll in. As each transaction is mined, the transaction hash as well as index data will be printed to your terminal. Let it run for a bit and when it finishes, it will terminate by itself.</p><p>You can search up your token contract <a href="https://ropsten.etherscan.io/token-search">here</a>. When you visit the address, you can click on the Token Holders field and then you can see the token distribution of all the tokens. When your contract is finished you will see that the tokens are distributed based on the total RtETH balance. You will notice that all of your tokens are still with your account (because we only sent one each to everyone else!)</p><h4>Step VIII: Custom Airdrop Function</h4><p>In practice, you don’t just want everyone to have one token. Maybe you have a cool idea about how the tokens should be distributed. For example, maybe you think that users should be rewarded tokens proportionally based on the amount of RtETHs they have. For example, if there are only two users that you wish to airdrop to and one owns 10% of the total RtETH and the other owns 90% of the RtETH, then they should receive 10% of the tokens and 90% of the tokens, respectively.</p><p>Fortunately for you, I’ve already implemented this function for you. Now, before we get to airdrop our tokens again, you will have to redeploy your contracts and update the address in your config.js file. You will also have to make sure that the INITIAL_TOKENS value in the index.js file on line 23 matches the exact balance that you have minted. This is important as this value is used in token calculation function.</p><p>As an example, if your contract has 1 000 000 tokens, you will need to set the INITIAL_TOKENS value to 1 000 000 000 000 000 000 000 000. (1 000 000 * 10 ^ d, where d is the decimals values in your contract, with 18 being the default value).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WY61368qLKmmbT4LtJz20g.png" /><figcaption>Custom Airdrop Function</figcaption></figure><p>To update our token calculation function, we will go to the function called “calculationDrop” and comment out line 90 while uncommenting line 84–89. This function here takes in the total balance and the proportional balance and returns the amount of tokens needed to be airdropped to this person. Once you have done this, go through the checklist again and then you can run the code!</p><p>Now you can check your token contract on Etherscan again and this time, you will see that the tokens are much more fairly distributed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWOl9iAZoWXXijrLNuCvEQ.png" /><figcaption>Fairly Distributed Tokens.</figcaption></figure><p>If you’re up for the challenge, try writing your own token distribution function (and then submit a PR and then we can have a whole library of custom airdrop functions!) ;)</p><h3><strong>Conclusion</strong></h3><p>Well, that’s it! By now you will have learnt how to deploy your first contract AND distribute its tokens in an equitable way. Was anything unclear in this tutorial? Got questions about how to deploy it? Let me know in the comments!</p><p>If you liked this content, (or you want me to reply to your questions faster ;)) give me some claps! If you’re interested in all things blockchain, then follow me on <a href="https://twitter.com/vncnttrn">twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ba187ff7cbf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitfwd/how-to-airdrop-your-first-token-3ba187ff7cbf">How To Airdrop Your First Token</a> was originally published in <a href="https://medium.com/bitfwd">Bitfwd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blockchain: From A Humble Experiment To A Decentralised Future]]></title>
            <link>https://medium.com/bitfwd/blockchain-from-a-humble-experiment-to-a-decentralised-future-5c5b6dda7cfe?source=rss-42ed7cb440b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c5b6dda7cfe</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ico]]></category>
            <dc:creator><![CDATA[Vincent Tran]]></dc:creator>
            <pubDate>Wed, 21 Feb 2018 08:37:53 GMT</pubDate>
            <atom:updated>2018-02-22T11:19:48.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*56icJ6WPoNlPAcAlhzEZCg.jpeg" /><figcaption>Photo by NASA on Unsplash</figcaption></figure><p>As the price action of cryptocurrencies has drawn new eyes into the blockchain space, I have frequently been asked to summarise the state of affairs in this space. I hope this article presents a succinct summary of what I believe has transpired in this space since its humble beginnings in 2009.</p><p>Many new blockchain protocols have been developed since Bitcoin’s inception in 2009. The easiest way to categorise them is by dividing them up into three different categories. We will explore each of these generations to better understand the current state of affairs in this space. We will focus primarily on infrastructure (perhaps dApps can be talked about another time).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RTwLszvUJNCOoGsjh1vHtw.jpeg" /><figcaption>Photo by David McBee from <a href="https://www.pexels.com/photo/bitcoins-and-u-s-dollar-bills-730547/">Pexels</a></figcaption></figure><h4><strong>First Generation</strong></h4><p>The inception of Bitcoin took place in 2009 as a way of putting a decentralised programmable money in the hands of the masses (<a href="https://bitcoin.org/bitcoin.pdf">Bitcoin: A Peer-to-Peer Electronic Cash System</a>). Decentralised meaning it was not controlled by any central entity but instead is governed by the rules of the protocol. Programmable in the sense that you could instruct computers to manipulate it according to certain rules.</p><p>And from there the rest is history, with Bitcoin growing from a fledgeling toy currency to a universally accepted store of value. Although much of Bitcoin’s initial utility as a medium of exchange has been lost due to its increase in price, the introduction of layer two infrastructure such as the <a href="https://bitcoin.stackexchange.com/questions/43700/how-does-the-lightning-network-work-in-simple-terms">Lightning Network</a> has the potential to bring back this functionality.</p><p>Bitcoin was first and foremost an experiment. As an experiment, it aimed to test the boundaries of money in our modern society by introducing a digitised version of it. The scope of the experiment had to be limited greatly to increase the likelihood of its success. Bitcoin’s development procedure is also upheld to a similar degree of strictness — each new BIP (<a href="https://en.bitcoin.it/wiki/Bitcoin_Improvement_Proposals">Bitcoin Improvement Protocol</a>) is tested rigorously before being integrated into the protocol.</p><p>First generation protocols like Bitcoin were designed to be used as currency (whether it be as a store of value or a medium of exchange). These protocols come in different flavours such as Litecoin ($LTC), Monero ($XMR), ZCash ($ZEC) and they all share similar characteristics. They have different design goals and have used different techniques to reach them. As an example, Monero and ZCash are two different coins both working on the confidentiality of transactions through different cryptographic techniques. Monero tries to achieve this using <a href="https://getmonero.org/resources/moneropedia/ringsignatures.html">ring signatures</a> whereas ZCash uses <a href="https://z.cash/technology/zksnarks.html">ZK-Snarks</a>.</p><h4><strong>Second Generation</strong></h4><p>Although the restrictive nature of first generation blockchain protocols has allowed them to flourish safely as a currency, it greatly limits their ability to perform complex tasks. This has led a team of developers to build the protocol that we currently know as <a href="https://blockgeeks.com/guides/ethereum/">Ethereum</a>, a blockchain that can be described as a decentralised world computer. Put simply, Ethereum allows users to run complex computations in a way that would be nontrivial on Bitcoin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y6jPwkFXw_mQG25jTYcuow.png" /><figcaption>CryptoKitties: The First Mainstream Digital Asset</figcaption></figure><p>You can think of second generation blockchains as first generation blockchains that have evolved to improve capability by enabling complex business logic in a way that does not require a central server to run through something called a “<a href="https://blockgeeks.com/guides/smart-contracts/">smart contract</a>”. These smart contracts can be used to manipulate digital assets in an automated and decentralised fashion. Existing real world applications tend to require a fee to access the application (think SaaS) or a fee to access a particular service (think Uber or Airbnb). Decentralised smart contracts turn this model on its head by making the applications open source such that anyone can run it provided they pay the cost of running the application on the network.</p><p>Second generation blockchains also come in several flavours such as NEO and ETC which also have different focuses such as scalability or immutability. Although these second generation blockchains have increased the capability provided by blockchains, they also have a larger attack surface. You should also keep in mind that Ethereum began its development in 2014, a whole 5 years after Bitcoin. These systems are still very much experimental technologies.</p><h4><strong>Third Generation</strong></h4><p>As second generation blockchains have matured, it became clear that there were several important issues that needed to be resolved. The three key ones in my opinion are privacy, scalability and formal verification. To get a better understanding of why these things are important, we’ll take a look at each of these individually.</p><p>In the blockchain space, all transactions are broadcasted to all users and are publicly viewable on the ledger. This means that in every transaction, the sender and receiver are not fully anonymous but are pseudo-anonymous (as they<strong> </strong>hide behind an address). For many mainstream transactions, maintaining privacy of the sender and receiver is important which makes privacy a going concern for public blockchains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PZX5oP9FjsSuSiyUIJzfXQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/muC_6gTMLR4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Barcelona</a> on <a href="https://unsplash.com/search/photos/traffic-jam?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Another issue is scalability. First generation blockchains have one primary use case — currency. This means that only throughput related to currency mattered. Second generation blockchains can have millions of applications running on top of them, which could <a href="https://qz.com/1145833/cryptokitties-is-causing-ethereum-network-congestion/">cause the network to grind to a halt</a>, as we saw with CryptoKitties late last year. It is important for this issue to be resolved if blockchains are to be adopted into mainstream use.</p><p>The last issue refers to the large attack surface of second generation blockchains that we have described earlier. Formal verification is a procedure that developers can use to prove or disprove the correctness of an algorithm, thereby allowing you to be certain that the algorithm will behave exactly as you expect it to. This will allow developers to guarantee the safety of the contracts they develop, significantly reducing the attack surface of their application.</p><p>Third generation blockchains such as EOS, Cardano, Tezos, Hashgraph and Corda, to name a few, all attempt to solve variations of these problems by making different tradeoffs, whether it be centralisation or the use of exploration of cutting edge technology. Strictly speaking, Corda is a <a href="https://www.coindesk.com/information/what-is-a-distributed-ledger/">distributed ledger technology</a> (DLT) and not a blockchain as such but I mention it here for completeness. Given that we know Ethereum’s inception was in 2014, we can expect these technologies to be less reliable. It’s important to remember that these projects are still very new in the grand scheme of things and all have potential to succeed as well as fail.</p><h4><strong>Summary</strong></h4><p>In summary, we have reviewed the history of blockchains starting from first generation blockchains that led the charge with programmable money. Then we realised that if we wanted to run complex applications in a decentralised manner, we would need to greatly expand the capability of the blockchains that we used which led to the birth of the second generation blockchains. After having used these newer blockchains for a while, we realised there were still many hurdles ahead of us — scalability, privacy and application correctness. This led to the race to develop the first of the third generation of blockchains which is where we are at today.</p><p>Hopefully this article has helped you better understand the evolution of blockchains over the last decade. Although many of the second and third generation blockchains are new, I expect there to be many improvements over the current system in the future. Each success and failure will teach us new things, bringing us closer to a future where decentralised applications could be commonplace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c5b6dda7cfe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitfwd/blockchain-from-a-humble-experiment-to-a-decentralised-future-5c5b6dda7cfe">Blockchain: From A Humble Experiment To A Decentralised Future</a> was originally published in <a href="https://medium.com/bitfwd">Bitfwd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>