<?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 Anurag Srivastava on Medium]]></title>
        <description><![CDATA[Stories by Anurag Srivastava on Medium]]></description>
        <link>https://medium.com/@anuragsrivastava.zeon?source=rss-41bb666b148d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*fHGqVJ-Ag8t2d7wq.</url>
            <title>Stories by Anurag Srivastava on Medium</title>
            <link>https://medium.com/@anuragsrivastava.zeon?source=rss-41bb666b148d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:40:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anuragsrivastava.zeon/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[Interacting with Smart Contracts using Solidity &  Web3]]></title>
            <link>https://medium.com/zeonlab-blockchain-semantic-blog/interaction-with-solidity-using-web3-5a4f1a7166f3?source=rss-41bb666b148d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a4f1a7166f3</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[deeptech]]></category>
            <dc:creator><![CDATA[Anurag Srivastava]]></dc:creator>
            <pubDate>Thu, 14 Dec 2017 13:01:34 GMT</pubDate>
            <atom:updated>2017-12-21T06:31:56.395Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qH4N6Vp6bc_PuajD4z2Gyw.png" /><figcaption>Solidity using web3.js</figcaption></figure><h3>Interacting with Smart Contracts using Solidity &amp; Web3</h3><p>Everything we do on the Ethereum Blockchain happens at the level of geth, which is a command line level interface on geth console. We do not expect an end user to be typing commands on some terminal for every small thing that he does on Ethereum. So there needs to be a way by which we can interact with the command line level interface using codes running on browsers. How do we make sure that a simple click by the user is interpreted as a command on the black-box terminal geth is running on? The answer to all these questions is web3.js.</p><p>web3.js is a collection of libraries which allows us to interact with a local or remote ethereum node, using a HTTP or IPC connection. Simply speaking, it provides us with JavaScript APIs to communicate with geth. It uses <strong>JSON-RPC</strong> internally to communicate with geth, which is a light-weight remote procedure call (RPC) protocol.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/0*rttyP_dhNmkS_KTO." /></figure><h3>Ethereum Node Setup:</h3><p>Before we proceed any further, it’s necessary to have a mining node of Ethereum running locally. In an earlier post, we have discussed on how to set up an Ethereum node. If you landed on this page without following along from the previous lessons, just copy and paste the following command in the terminal:</p><pre>geth — datadir &lt;path to your testnet directory&gt; — networkid 12345 — rpc — rpcaddr “localhost” — rpcport 8545 — rpccorsdomain “*” — rpcapi “eth,net,web3,personal,admin,mine” — mine — minerthreads 1 — nodiscover — maxpeers 0 miner</pre><h3>Sample Smart Contract:</h3><p>In the following section, an example will be presented that will make use of web3.js to allow interaction with the contracts via a web page served over a simple HTTP web server. This can be achieved by following these steps:</p><pre>pragma solidity ^0.4.11;<br>contract sample {<br> string public name = “ZeonLab”;<br> function set(string _name) {<br>    name = _name;<br> }<br> <br> function get() constant returns (string) {<br>   return name;<br> }<br>}</pre><h3>Creating UI for smart contract functions</h3><p>Open up your preferred code editor and create an index.html in the project folder.</p><p>We’re not going to create anything too fancy rather the UI would just have 2 buttons; One for the set() function and other for the get() function.</p><p>To get started, paste the following contents into the empty index.html file:</p><pre>&lt;html&gt;<br> &lt;head&gt;<br>  &lt;title&gt;Web3 — Simple Demo&lt;/title&gt;<br> &lt;/head&gt;<br> &lt;body class=”container”&gt;<br>  &lt;h3&gt;Web3 — Usage Example&lt;/h3&gt;<br>   &lt;div class=”tab-content”&gt;<br>   &lt;div role=”tabpanel” class=”tab-pane active” id=”blockchain”&gt;<br>  &lt;h3&gt; 1. Set the value in the blockchain&lt;/h3&gt;<br>   &lt;div class=”form-group form-inline”&gt;<br>    &lt;input type=”text” class=”text form-control” value=”Siri”&gt;<br>      &lt;button class=”set btn btn-primary”&gt;Set Value&lt;/button&gt;<br>        &lt;p&gt;Once you set the value, an event will be created which will be used to identify the status of the transaction.&lt;/p&gt;<br>   &lt;/div&gt;<br>  &lt;h3&gt; 2. Get the current value&lt;/h3&gt;<br>   &lt;div class=”form-group”&gt;<br>   &lt;div&gt;<br>     current value is &lt;span class=”value”&gt;&lt;/span&gt;<br>   &lt;/div&gt;<br>    &lt;button class=”get btn btn-primary”&gt;Get Value&lt;/button&gt;<br>      &lt;p&gt;Click the button to get the current value. The initial value of the variable name is “ZeonLab”.&lt;/p&gt;<br>   &lt;/div&gt;<br>  &lt;h3&gt; 3. Contract Calls &lt;/h3&gt;<br>      &lt;p&gt;Javascript calls being made: &lt;/p&gt;<br>   &lt;/div&gt;<br>   &lt;/div&gt;<br>&lt;/body&gt;<br>  &lt;script&gt;&lt;/script&gt;<br>&lt;/html&gt;</pre><h3>Using Web3.js to Interact with the Smart Contract</h3><p>Having the HTML code ready, we need to import web3 module to interact with smart contract from HTML.</p><p>If you do not have web3.js already, download it from the following link:</p><p><a href="https://github.com/ethereum/web3.js">https://github.com/ethereum/web3.js</a></p><p>Once downloaded, web3 module can be imported into Javascript using the script tag as:</p><pre>&lt;script src=”web3.js-develop/dist/web3.js”&gt;&lt;/script&gt;</pre><p>Once the file is successfully referred in JS, web3 needs to be initialized by an HTTP endpoint. This HTTP endpoint is exposed by the Geth client on which a node was setup.</p><p>Web3 provider can be set by adding the following lines of code between the script tags:</p><pre>var Web3 = require(‘web3’);<br>var web3 = new Web3();<br>web3.setProvider(new web3.providers.HttpProvider(“http://localhost:8545&quot;));</pre><p>Next, we need to use the web3.eth.contract() method to initialize (or create) the contract on an address. It accepts one parameter, which is referred to as the ABI (Application Binary Interface).</p><p>This ABI allows you to call functions and receive data from your smart contract.</p><p>To retrieve the ABI of the contract, copy the contract code and paste it in Remix IDE(<a href="http://remix.ethereum.org/">http://remix.ethereum.org</a>). Next click on the ‘Details’ button in ‘Compile’ tab. Scroll down to see the contract ABI. Copy the ABI by clicking on the icon shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/0*yqSlfvciKcj2axXu." /></figure><p>Once done paste the ABI code into script against the variable sampleContractABI. Your code should look something like this:</p><pre>var sampleContractABI = [{“constant”:true,”inputs”:[],”name”:”name”,”outputs”:[{“name”:””,”type”:”string”}],”payable”:false,”stateMutability”:”view”,”type”:”function”},{“constant”:false,”inputs”:[{“name”:”_name”,”type”:”string”}],”name”:”set”,”outputs”:[],”payable”:false,”stateMutability”:”nonpayable”,”type”:”function”},{“constant”:true,”inputs”:[],”name”:”get”,”outputs”:[{“name”:””,”type”:”string”}],”payable”:false,”stateMutability”:”view”,”type”:”function”},{“anonymous”:false,”inputs”:[{“indexed”:false,”name”:”name”,”type”:”string”}],”name”:”LogSet”,”type”:”event”}];</pre><p>Next initialize the smart contract with web3.eth.contract method as follows:</p><pre>var sampleContract = web3.eth.contract(sampleContractABI);</pre><p>Now that we have the interface for interacting with our contract through the sampleContract variable, the last thing to do is to define the actual contract address.</p><p>Go back to Remix and click the Run tab, and click on the copy icon next to the contract that we created earlier on the right column. Then add the following lines of code to the script.</p><pre>var sampleContractInstance = sampleContract.at(&lt;contract address&gt;);</pre><p>Great! Now let’s attach simple JQuery functions to the get and set buttons in the HTML.</p><pre>$(“#blockchain button.set”).click(function() {<br>var value = $(“#blockchain input.text”).val();<br>var params = {<br>gas: 40000,<br>from:<br>};<br>SimpleStorage.sendTransaction.set(value, params);<br>});<br>$(“#blockchain button.get”).click(function() {<br>var value = SimpleStorage.get.call();<br>$(“#blockchain .value”).html(value);<br>});</pre><p>In the set(), we’re simply sending a transaction to the <em>‘SampleContract’</em> with the params specified. Whereas in the get(), we’re simply making a call and the result is set to an element with the class name <em>‘value’.</em></p><p>If you did everything correctly, you can now view index.html in the browser, with get and set buttons.</p><p>This is all about using TestRPC with Web3.js to interact with smart contracts through a browser. If you are still facing troubles write to us at hello@blockchainsemantics.com .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a4f1a7166f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zeonlab-blockchain-semantic-blog/interaction-with-solidity-using-web3-5a4f1a7166f3">Interacting with Smart Contracts using Solidity &amp;  Web3</a> was originally published in <a href="https://medium.com/zeonlab-blockchain-semantic-blog">Zeonlab &amp; Blockchain Semantics Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to install Testnet for the Ethereum blockchain client]]></title>
            <link>https://medium.com/zeonlab-blockchain-semantic-blog/how-to-install-testnet-for-the-ethereum-blockchain-client-27d8be4beecb?source=rss-41bb666b148d------2</link>
            <guid isPermaLink="false">https://medium.com/p/27d8be4beecb</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[deeptech]]></category>
            <dc:creator><![CDATA[Anurag Srivastava]]></dc:creator>
            <pubDate>Sun, 10 Dec 2017 06:54:00 GMT</pubDate>
            <atom:updated>2017-12-10T06:54:00.879Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://blockchainsemantics.com/">Blockchain Semantics</a> has had a lot of people reach out and tell us they have trouble installing testnet for the Ethereum blockchain. Needless to say, this is the first step in being able to develop smart contracts on Ethereum.</p><p>So, here is a set-by-step ready reckoner for getting your testnet going!</p><h3>Ethereum Client:</h3><p>Ethereum client provides an interface to create transactions, mine blocks and various other blockchain interactions. Currently three client implementations are available for Ethereum.</p><ol><li>Eth — C++ client</li><li>Geth — Go lang client</li><li>PyEthApp — Python client for Ethereum</li></ol><p>Of these three, this article covers Geth. First let’s have a look at the installation instructions for Geth.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fy1zAqdo3LiI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dy1zAqdo3LiI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fy1zAqdo3LiI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3a78cf94a720bf18b2e52b7f35ae2ca9/href">https://medium.com/media/3a78cf94a720bf18b2e52b7f35ae2ca9/href</a></iframe><h3>Installing Geth:</h3><p>Geth is available for Linux, Windows and OS X. Let’s see how to install it in various operating systems.</p><h4>1. Installation Instructions for Ubuntu</h4><ul><li>Installing from PPA</li><li>To install GETH on ubuntu, open Terminal using Ctrl + Alt + T and type:</li></ul><p>sudo apt-get install software-properties-common</p><p>Now hit Enter. The program will ask you to type the password. Enter your password and press Enter. You should see a result similar to the figure shown. Next type the following command at the prompt and type Enter.</p><p>sudo add-apt-repository -y ppa:ethereum/ethereum<br> sudo apt-get update<br> sudo apt-get install ethereum</p><p>When the program asks whether you’d like to allow the installation to take some hard drive space, type Y(yes) and press Enter. After the installation is finished, you can check geth by typing the following at the prompt:</p><p>geth version</p><h4>2. Installation Instructions for Windows</h4><ul><li>Install from binary</li><li>Geth packages are built and can be downloaded from <a href="https://geth.ethereum.org/downloads/">https://geth.ethereum.org/downloads/</a>.</li></ul><p>The download page provides an installer as well as a zip file.</p><p>Download exe file from the page.</p><p>Once the file has finished downloading, open and install geth.exe</p><h4>3. Installation Instructions for Mac</h4><ul><li>Installation from source</li><li>GETH installation for MAC requires GO compiler to be installed. If you don’t have GO compiler, install it first using:</li></ul><p>brew install go</p><p>Then clone the geth repository from github by running the following command at the terminal:</p><p>git clone <a href="https://github.com/ethereum/go-ethereum">https://github.com/ethereum/go-ethereum</a></p><p>Once the repository has cloned, change the working directory.:</p><p>cd go-ethereum</p><p>Finally, build the Geth program using:</p><p><em>make geth</em></p><h3>Using Go-Ethereum to Setup your Own Custom Ethereum Blockchain:</h3><p>Go-Ethereum enables a user to set up a “testnet” Ethereum chain that is separate from the main Ethereum chain. This is useful for testing distributed apps without having to expose your trials to the real Ethereum network which costs Ether. On your custom Ethereum chain, you can either pre-generate or mine your own Ether; so it is a much more cost effective way of trying out Ethereum. Having discussed about the advantages of custom ethereum chain, let’s look into the details of how to create a testnet chain.</p><p>The first step in creating your own testnet chain is to setup a genesis file.</p><h4>1. The Genesis File:</h4><p>The Genesis file is used to define the initial parameters of the blockchain for eg., chain configuration, level of difficulty to mine blocks etc. The consensus algorithm of Ethereum ensures that a node gets connected to your testnet chain only if they have the same genesis file.</p><p>Let us create a <em>mygenesis.json</em> file with the parameters shown. It is recommended that you make a random nonce for your custom Ethereum network to avoid the chance of someone connecting to your blockchain.</p><p>{</p><p>“config”:{</p><p>},</p><p>“mixhash”: “0x00000000000000000000000000000000000000647572616c65787365646c6578”,</p><p>“nonce”: “0x00000000”,</p><p>“difficulty”: “0x2”,</p><p>“coinbase”: “0x0000000000000000000000000000000000000000”,</p><p>“timestamp”: “0x00”,</p><p>“parentHash”: “0x0000000000000000000000000000000000000000000000000000000000000000”,</p><p>“extraData”: “0x”,</p><p>“gasLimit”: “9223372036854775807”,</p><p>“alloc”: {</p><p>}</p><p>}</p><p>Let us now discuss the meaning for parameters in genesis file:</p><ul><li>config — Specifies the configuration parameters for the network</li><li>mixhash — It is a 256 bit hash.</li><li>nonce — It is a 64-bit hash, which upon combination with mixhash allows to verify that the mathematical condition specified in Proof-of-Work (PoW) algorithm is satisfied.</li><li>difficulty — the difficulty level applied during the nonce discovering of this block. The higher the difficulty, the more calculations a Miner must perform to discover a valid block. On the test network, we keep this value low so that blocks get mined quickly.</li><li>coinbase — It is a 160-bit address. Upon successful mining of each block, mining reward would be transferred to this address. Rewards transferred are a sum of the block mining reward and the transaction fee.</li><li><em>timestamp</em> — specifies time at the inception of genesis file. By setting the value to 0, geth automatically sets timestamp to the current time.</li><li>parentHash — It is the keccak 256-bit hash of the entire parent block header. For a genesis block, it would be 0 since a Genesis block is the first block and so doesn’t have any parent block.</li><li>gaslimit — It defines the maximum amount of gas expenditure allowed per block. For example, let’s say we have 5 transactions where each transaction has a gas limit of 10, 20, 30, 40, 50 and 120. If the block gas limit is 100, then only the first four transactions can fit in the block. If you try to include the last transaction, it will be rejected by network and geth throws error “that transaction gas exceeds block gas limit”. It cannot be included at all unless the block gas limit is increased to 120 or more. Hence it is important to set the block gas limit value high.</li><li>alloc — alloc parameter allows to define a list of accounts pre-filled with ether.</li></ul><p><strong>Note: </strong>We’ve lowered the difficulty level on testnet, so that mining of block goes faster.</p><ul><li>The next thing we need to know is how to setup a genesis file. Open terminal and type:</li></ul><p>geth — datadir &lt;path to an empty folder&gt;(e.g., /home/vishy/testNet/) init mygenesis.json</p><ul><li>Here datadir parameter specifies the path of the directory which will store your chain data.</li></ul><p><strong>Note: </strong>We’re using a custom <em>datadir</em> flag to separate the data for the testnet blockchain from the real one.</p><p>Once you have setup your <em>mygenesis.json</em> file, type the following command at the terminal to start your testnet chain.</p><p>geth — datadir &lt;folder specified in earlier command&gt; — networkid 12345 — rpc — rpcaddr “localhost” — rpcport 8545 — rpccorsdomain “*” — rpcapi “eth,net,web3,personal,admin,mine” — nodiscover — maxpeers 0 console</p><p>This command opens a geth console session, which can be used for creating accounts, carrying transactions and any other blockchain interactions.</p><p>In the above command:</p><ul><li>datadir specifies path of the directory which will store your chain data. This should be the same folder as specified in the earlier command.</li><li>networkid — Can be any ID other than 1; Id 1 is reserved for frontier(Main) network.</li><li>rpc — enables RPC interface on your node.</li><li>rpcapi — dictates what APIs that are allowed to be accessed over RPC. This will give everyone access to the API who can access this interface. By default, Geth enables the web3 interface over RPC.</li><li>rpccorsdomain — dictates what URLs can connect to your node in order to perform RPC client tasks. Specifying ‘*’ will allow any url to connect to your interface.</li><li>nodiscover — This is to make sure that your node is not discoverable by people who do not manually add you. Otherwise, there is a chance that your node may be inadvertently added to a stranger’s node if they have the same genesis file and network id.</li><li>maxpeers 0 prevents anyone else connecting to your test chain. Alternatively, you can adjust this number if you know exactly how many peers you want connecting to your custom Ethereum chain.</li></ul><h3>Pre seeding Accounts with local ether:</h3><p>In order to carry out transactions on testnet chain, ether is required. Therefore you need to pre-allocate Ether to your account.</p><ol><li>First create a new Ethereum account in your testnet chain. To do this, open geth console and type:</li><li>personal.newAccount()</li></ol><p>This will request for a passphrase. Enter the passphrase and keep it safe. This passphrase would be required each time you want to carry out transaction.</p><ol><li>Once you’ve generated your account, quit geth console with ctrl+c. Now remove every folder except keystore from your datadir. Open terminal and type:</li><li>cd &lt;datadir specified earlier&gt;<br>rm -rf `ls | grep -v keystore</li><li>Copy your new account address</li><li>Add the following command to your mygenesis.json file:</li></ol><p>“alloc”:<br>{ <br> “&lt;your account address e.g. 0x1fb891f92eb557f4d688463d0d7c560552263b5a&gt;”:<br> { “balance”: “20000000000000000000” } <br>}</p><p>5. Save your genesis file and re-run your testnet chain command. Let’s check the balance of the address once geth is fully loaded. Type the following in your geth console.</p><p>var primary = “0x2…021516”;</p><p>balance = web3.fromWei(eth.getBalance(primary), “ether”);</p><p>This should return you 20 Ether in your account. The reason we had to put such a large number in the alloc section of your genesis file is because the “balance” field takes a number in wei which is the smallest sub-unit of Ether. Recall that 1 Ether = ¹⁰¹⁸ wei.</p><h3>Using the testnet chain:</h3><p>For all the transactions to get executed and included in the Blockchain, mining session needs to be enabled. Start a miner instance for your custom testnet chain. Open terminal and type the following command:</p><p>geth — data dir &lt;path to your testnet directory&gt; — networkid 12345 — rpc — rpcaddr “localhost” — rpcport 8545 — rpccorsdomain “*” — rpcapi “eth,net,web3,personal,admin,mine” — mine — minerthreads 1 — nodiscover — maxpeers 0 miner</p><ul><li>datadir specifies path of the directory which will store your chain data. This should be the same folder as specified in the earlier command.</li><li>networkid — should be the same network id as specified earlier.</li><li>rpcapi “mine” — Enables running miner commands in Javascript using ethereum webapi like web3.js or ethereum JS</li><li>mine — Enables mining</li><li>minerthreads — Number of CPU threads to be used for mining. “Successfully sealed new block”.</li></ul><p><strong><em>Troubleshooting tip:</em></strong><em> If your console session gets stuck saying “Commit new mining work”, clear all the files from /home/usr/.ethash directory and restart the miner session.</em></p><p>You should see the mining process going on with the logs displaying the message “Commit new mining work”. In order to carry out transactions, you need to attach another geth session.</p><p>Open another console/terminal and type the ‘geth attach’ command:</p><p>cd &lt;your datadir&gt;</p><p>geth — datadir &lt;path to test network directory&gt; — networkid 12345 attach ipc:geth.ipc</p><ul><li>datadir — path of the directory which will store your chain data. This should be the same folder as specified in the earlier command.</li><li>networkid — the same network id as specified earlier.</li><li>geth attach — will connect your second console to the geth instance on your first console.</li></ul><p>Now you can carry all your transactions and run commands from this session.</p><p>Each time you want to carry out a transaction, make sure your account is unlocked. If not, type the following in geth console.</p><p>personal.unlockAccount(‘&lt;Your account address&gt;’)</p><p>Or You may unlock your account for the entire geth session using:</p><p>geth — data dir &lt;path to your testnet directory&gt; — networkid 12345 — rpc — rpcaddr “localhost” — rpcport 8545 — rpccorsdomain “*” — rpcapi “eth,net,web3,personal,admin,mine” — mine — minerthreads 1 — unlock 0 — nodiscover — maxpeers 0 miner</p><ul><li>datadir specifies path of the directory which will store your chain data. This should be the same folder as specified in the earlier command.</li><li>networkid — should be the same network id as specified earlier</li></ul><p>This should be it for setting-up the testnet correctly. If you are still facing troubles, just watch the videos and repeat the steps more carefully. And if you are still stuck, write to us at hello@blockchainsemantics.com .</p><p><strong>Useful Links:</strong></p><ul><li><a href="http://ethdocs.org/">Ethereum Docs</a></li><li><a href="https://github.com/ethereum/go-ethereum/wiki/Installing-Geth">Geth Install Instructions</a></li><li><a href="https://github.com/ethereum/go-ethereum/wiki/JavaScript-Console">Geth Javascript Console Wiki</a></li><li><a href="https://github.com/ethereum/wiki/wiki/JSON-RPC">Geth JSON-RPC Wiki</a></li><li><a href="https://etherscan.io/">Etherscan</a></li><li><a href="https://github.com/etherparty/explorer">Ether explorer for testnet chain</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27d8be4beecb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zeonlab-blockchain-semantic-blog/how-to-install-testnet-for-the-ethereum-blockchain-client-27d8be4beecb">How to install Testnet for the Ethereum blockchain client</a> was originally published in <a href="https://medium.com/zeonlab-blockchain-semantic-blog">Zeonlab &amp; Blockchain Semantics Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>