<?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[Exploring the Blockchain - Medium]]></title>
        <description><![CDATA[Series of notes on how to deploy different aspect on blockchains. - Medium]]></description>
        <link>https://medium.com/exploring-the-blockchain?source=rss----586cb2b1e5b0---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Exploring the Blockchain - Medium</title>
            <link>https://medium.com/exploring-the-blockchain?source=rss----586cb2b1e5b0---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:15:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/exploring-the-blockchain" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Zilliqa + Scilla | Exploring Sharding]]></title>
            <link>https://medium.com/exploring-the-blockchain/zilliqa-scilla-exploring-sharding-73902f039ba6?source=rss----586cb2b1e5b0---4</link>
            <guid isPermaLink="false">https://medium.com/p/73902f039ba6</guid>
            <category><![CDATA[scilla]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[zilliqa]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <dc:creator><![CDATA[Nico Zahniser]]></dc:creator>
            <pubDate>Sat, 31 Aug 2019 00:58:30 GMT</pubDate>
            <atom:updated>2019-09-11T02:07:01.837Z</atom:updated>
            <content:encoded><![CDATA[<p>Sharding is a concept that’s widely used in databases, to make them more efficient. A shard is a horizontal portion of a database, with each shard stored in a separate server instance.</p><p>In essence of using a blockchain, nodes that maintain a shard maintain information only on that shard in a shared manner, so within a shard, the decentralization is still maintained.</p><p>Let’s get started into <a href="https://zilliqa.com/">Zilliqa</a>, which is the first sharding blockchain on mainnet. It uses Scilla, short for Smart Contract Intermediate-Level Language, is an intermediate-level smart contract language being developed for Zilliqa.</p><p>HelloWorld is usually good place to start for practice, we also have to find a good editor, or IDE that can help verify contracts before trying to deploy.</p><h3>HelloWorld.scilla</h3><p>Let’s start with a look at the classical “HelloWorld” contract.</p><p><strong>Libraries</strong></p><p>A Scilla contract may come with some helper libraries that declare purely functional components of a contract. <br>‍<br>A library is declared in the preamble of a contract using the keyword library followed by the name of the library. <br>HelloWorld contract code has a function one_msg in the library and two global constants.<br>‍<br>Standard libraries shipped with the language can be added using the keyword import followed by the name of the library.</p><p><strong>Code Snippet: “HelloWorld”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*Pz7pJioly0lTr94LN-SKBA.png" /></figure><p><strong>(Im)mutable variables</strong></p><p>Scilla contracts use two types of state variables: mutable and immutable. <br>‍<br>Immutable variables are those that get initialized at the time of contract creation. Once initialized, their values cannot be changed. HelloWorld has one immutable variable named owner.<br>‍<br>Mutable variables are those whose value will change even after the contract has been created. HelloWorld has one mutable variable named welcome_msg.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*1bpJT2NTrpOtobM_juVzdg.png" /></figure><h3>Functions // Transitions</h3><p>Transitions are functions that change the value of mutable variables and can communicate with other contracts. <br>‍<br>The first transition, <em>setHello</em>, takes a String as input, updates welcome_msg and informs the caller of the success/failure.</p><p>The second transition, <em>getHello</em>, simply sends out a message to the caller with the current value of welcome_msg.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*qPsXcWE4pMRb6bmY5myceA.png" /></figure><p><strong>Finding an IDE</strong></p><p>Scilla developed an easy way to test basic contracts out in a browser environment. <a href="https://scilla-lang.org/">Scilla IDE</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uH4IwEEHATDuIltgbAUyvg.png" /></figure><p>From there you can go to the far right tab and deploy the contract and see if you have success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*wPQa1aXRzkbmYtjCVctIdg.png" /></figure><p>While yes, I think we all got PTSD from “Along Came Polly” , and the infamous discovery of the word ‘sharting’. Sharding does have great potential</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fz9JGxGsdeZ82c%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fz9JGxGsdeZ82c%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fz9JGxGsdeZ82c%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="174" frameborder="0" scrolling="no"><a href="https://medium.com/media/31b5eca1fade310cba1797553a1c754a/href">https://medium.com/media/31b5eca1fade310cba1797553a1c754a/href</a></iframe><p><strong>Final Thoughts</strong></p><p>Hopefully you gained some more information about a sharding blockchain and just a little bit of understanding of how the code works.</p><p>Wider adoption of sharding requires the blockchain and crypto developers to work on an important area.</p><p>While communication between nodes within a shard is smooth, inter-shard communication is currently not easy and requires the development of a separate protocol.</p><p>Addressing this key requirement will potentially result into a wider adoption of sharding, and that’ll help blockchains handle higher transaction throughput .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73902f039ba6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/exploring-the-blockchain/zilliqa-scilla-exploring-sharding-73902f039ba6">Zilliqa + Scilla | Exploring Sharding</a> was originally published in <a href="https://medium.com/exploring-the-blockchain">Exploring the Blockchain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Connecting Quorum 7 Node to Epirus]]></title>
            <link>https://medium.com/exploring-the-blockchain/connecting-quorum-7-node-to-epirus-f897f3315ea3?source=rss----586cb2b1e5b0---4</link>
            <guid isPermaLink="false">https://medium.com/p/f897f3315ea3</guid>
            <category><![CDATA[quorum]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[quorum-blockchain]]></category>
            <dc:creator><![CDATA[Nico Zahniser]]></dc:creator>
            <pubDate>Sat, 24 Aug 2019 17:04:03 GMT</pubDate>
            <atom:updated>2019-08-24T17:04:03.208Z</atom:updated>
            <content:encoded><![CDATA[<p>As we start off exploring more into the realms of blockchain, we need to understand that most on-chain development or deployment uses the terminal for the UI.</p><p>That means ingesting a lot of information via the terminal. We live in the post-modern dial-up, the least we can do is provide some good visuals to make sense of all the data.</p><p>I think exploring ways in which to actual view the data on/off-chain is vital to understanding the full dimensions of the ability of ‘<a href="https://www.jpmorgan.com/global/blockchain">the blockchain + distributed ledger technology</a>’.</p><p>In the Summer of June 2017, JP Morgan launched a fork of Ethereum called, Quorum.</p><h3>Let’s Start with Quorum. What is it?</h3><p>In Summer of June 2017, JP Morgan launched a fork of Ethereum called, Quorum.</p><p>“Based on Ethereum, Quorum is an open source blockchain platform that combines the innovation of the public Ethereum community with enhancements to support enterprise needs.</p><p>Our mission is to make adopting blockchain a seamless process. We’re not just a platform — we provide full-service support.” -<a href="https://www.goquorum.com/">GoQuorum</a></p><p>We are going to deploy a UI that will allow us to see the interactions on/off-chain.</p><h3>What in the name is Epirus?</h3><p>Well a quick Wikipedia search says,</p><p><em>“Epirus, is a traditional geographic and modern administrative region in northwestern Greece.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*YX3YXUf3CBxulQ1i" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/0*XDbgytLTLe4rynoG.png" /></figure><p>For this example the best way to remember it is think of it as the bridge to you and your blockchain data, contract creation, and asset tracking.</p><p>Epirus is an interface that allows you to interact with your blockchain assets, that you deploy to the Quorum. First, in order to interact with Epirus you have to deploy a <strong>Quorum Node, </strong>the one we are going to use today is called <a href="https://github.com/jpmorganchase/quorum-examples/tree/master/examples/7nodes">7nodes</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vYwY77KBnlhmeLel.png" /></figure><p>Let’s get the basics to run this on our computers.</p><h3>Setting up Vagrant</h3><ol><li>Install <a href="https://www.virtualbox.org/wiki/Downloads">VirtualBox</a></li><li>Install <a href="https://www.vagrantup.com/downloads.html">Vagrant</a></li><li>Download and start the Vagrant instance (note: running vagrant uptakes approx 5 mins):</li></ol><pre>git clone <a href="https://github.com/jpmorganchase/quorum-examples">https://github.com/jpmorganchase/quorum-examples</a><br>cd quorum-examples<br>vagrant up<br>vagrant ssh</pre><p>4. To shutdown the Vagrant instance, run vagrant suspend. To delete it, run vagrant destroy. To start from scratch, run vagrant up after destroying the instance.</p><h3>Connecting Epirus to Quorum 7 Node Example</h3><p>Get Quorum 7 node example</p><pre>git clone <a href="https://github.com/jpmorganchase/quorum-examples">https://github.com/jpmorganchase/quorum-examples</a><br>cd quorum-examples<br>docker-compose up</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*IYnMw1zYHeKki_CV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/344/0*rujzUcT-g2TdBH8Y.png" /><figcaption>You should see this in your terminal</figcaption></figure><h3>Set up Epirus-Free</h3><pre>git clone <a href="https://github.com/blk-io/epirus-free.git">https://github.com/blk-io/epirus-free.git</a><br>cd epirus-free</pre><p>You need to make some minor changes to the docker-compose.yml file so that epirus can connect a running node.</p><p>Change the networks name property from epirus-net to quorum-examples-net in the networks settings:</p><p>sed -i &#39;s/name: epirus-net/name: quorum-examples-net/g&#39; docker-compose.yml</p><p>The networks property should now looks like this:</p><pre>networks:<br>  epirus:<br>    name: quorum-examples-net<br>    driver: bridge<br>    ipam:<br>      driver: default<br>      config:<br>        - subnet: 172.16.239.0/24</pre><p>Now you can start epirus with the following command.</p><p>NODE_ENDPOINT=http://172.16.239.11:8545 docker-compose up</p><blockquote><em>Note: we are connecting to node 1 — you will only see private transactions for that node.</em></blockquote><p>You should see the following happening in the terminal window. This means that everything has started successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*ysU6OR5QkSKtWNnR" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/0*xI8vjS8H3biQwncl.png" /></figure><blockquote><em>Note: The logs are verbose and you will see various errors before all services are started. The important logs to look at are on the api. You can access them with the following</em></blockquote><blockquote><em>docker-compose logs -f api</em></blockquote><p>Navigate to <a href="http://localhost/">localhost</a> and you should see the loading page:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FTjwPWMN4geNLvoih58%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FTjwPWMN4geNLvoih58%2Fsource.mp4&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FTjwPWMN4geNLvoih58%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="204" frameborder="0" scrolling="no"><a href="https://medium.com/media/c74f57afe18cbb9113ccd9097e1cb52d/href">https://medium.com/media/c74f57afe18cbb9113ccd9097e1cb52d/href</a></iframe><p>This may to several minutes for Epirus to be displayed, (MacBook Pro ~ 20+ minutes).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*RubhgILMfvs5mQRu" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RTxbyY9YrBZCUz_N.png" /></figure><p>This should now show up in your browser when you go to <em>localhost;</em>if you click on blocks you will see this same UI.</p><p>To close Epirus or Quorum you can execute the following line in your terminal:</p><p>docker-compose down</p><p>For more information check out the GitHubs:</p><p><a href="https://github.com/blk-io/epirus-free/blob/master/examples/Quorum_Example.md">https://github.com/blk-io/epirus-free/blob/master/examples/Quorum_Example.md</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f897f3315ea3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/exploring-the-blockchain/connecting-quorum-7-node-to-epirus-f897f3315ea3">Connecting Quorum 7 Node to Epirus</a> was originally published in <a href="https://medium.com/exploring-the-blockchain">Exploring the Blockchain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>