<?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 Puneet Kumar on Medium]]></title>
        <description><![CDATA[Stories by Puneet Kumar on Medium]]></description>
        <link>https://medium.com/@puneet_88128?source=rss-4639c30568b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*QJjzPFLWUElnV7AlWmPRHA.png</url>
            <title>Stories by Puneet Kumar on Medium</title>
            <link>https://medium.com/@puneet_88128?source=rss-4639c30568b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:07:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@puneet_88128/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[Hyperledger Indy: Blockchain Identity Project]]></title>
            <link>https://medium.com/akeo-tech/hyperledger-indy-blockchain-identity-project-54e0bfed9e90?source=rss-4639c30568b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/54e0bfed9e90</guid>
            <category><![CDATA[blockchain-technology]]></category>
            <category><![CDATA[hyperledger-indy]]></category>
            <category><![CDATA[blockchain-development]]></category>
            <category><![CDATA[technical-development]]></category>
            <category><![CDATA[identity-management]]></category>
            <dc:creator><![CDATA[Puneet Kumar]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 11:16:50 GMT</pubDate>
            <atom:updated>2019-04-19T11:21:31.395Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*N8xQN1bRETrCJF2TifENtQ.jpeg" /><figcaption>Hyperledger Indy</figcaption></figure><p>Hyperledger Indy provides tools, libraries, and reusable components for providing digital identities rooted on blockchains or other distributed ledgers so that they are interoperable across digital networks, administrative domains, applications.</p><p>Once an identity is created, the user can even assign a human-memorable name for their identity. On the ledger, the identity name is converted into a unique identity key called DID (decentralized identifiers). Different individual or organization can communicate with each other using these DIDs.</p><p><strong>Digital Identity</strong></p><p>A digital identity is the information of an entity used by computer systems to represent an external agent and get recognized in a network. Digital Identity provides authorization and authentication factors of a node when a node operates in a network.</p><p>The real-world example of digital identities are passports which identifies a person with authenticity.</p><p><strong>What is a Self-Sovereign Identity?</strong></p><p>Self-sovereign identity is the concept that people and businesses can control their own identity data on their own devices, and provide it efficiently to those who need to validate it, without relying on a central repository of identity data.</p><p>So, we can say that self-sovereign identity is a modified version of digital identity which is decentralized to maximize security. Previously, most of the digital identities were stored on centralized database which increased the chance of financial fraud and data breaches. But in case of self-sovereign identity, identities are issued by Hyperledger Indy and are controlled by a person or organization itself so that all the data become decentralized. The whole process is explained below -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*1Z6r4iTXWGA4_8pKIppUtw.jpeg" /></figure><p>Here, we have a Claim Issuer, Claim Holder and Claim Verifier. In this case, claim holder wants to get a claim which should be issued by the Department of Motor Vehicles(DMV) and must be verified by lawyers(Bar Association).</p><p>Firstly, DMV will sign the claim using its SSID and then claim will be issued to claim holder. Once the claim is issued then claim holder will sign the issued claim using his/her SSID and present the claim to bar association. Bar association will then verify the claim sung their SSID. All these transactions will be stored on blockchain so that they cannot be altered and can always be referred back.</p><p>In this way, Self-Sovereign Identity plays a huge role in authenticating and verifying an entity in a network.</p><p><strong>Key Features of Hyperledger Indy</strong>-</p><ol><li>Hyperledger Indy provides a distributed ledger to provide decentralised identities.</li><li>DIDs (Decentralized Identifiers) that are globally unique and resolvable (via a ledger) without requiring any centralized resolution authority.</li><li>Zero Knowledge Proofs which prove that some or all of the data in a set of Claims is true without revealing any additional information, including the identity of the prover</li><li>Provides identities which ensures -</li></ol><ul><li>Control — User can control their own identity.</li><li>Access — Access to their own data.</li><li>Transparency — Every entity is visible to every other entity.</li><li>Interoperability — Identities can be used by anyone on the network.</li><li>Consent — Agreement on using their own identity.</li><li>Existence — Provide user an independent existence.</li><li>Longevity — Exists as long as user wishes.</li><li>Portability — Transportable Identifiers.</li><li>Minimization — Disclosure of claims are minimized.</li><li>Protection — The rights of user’s are protected.</li></ul><p><strong>Hyperledger Indy Components</strong></p><p>a) Indy-Node</p><ul><li>Indy Node provides a <a href="https://sovrin.org/">self-sovereign identity ecosystem</a> on top of a distributed ledger.</li></ul><p>b) Indy-Agent</p><ul><li>Agents are a combination of functionality and storage that communicate via messages with other Agents. Agents are responsible for asking controlling identities and carrying them to other agents to create connection.</li></ul><p>c) Indy-Ledger</p><ul><li>Provides a simple, python-based, immutable, ordered log of transactions backed by a merkle tree.</li><li>This is an efficient way to generate verifiable proofs of presence and data consistency.</li></ul><p>You can read about how to set up Hyperledger blockchains here:</p><ul><li><a href="http://A Step by Step Guide for Setting-up Hyperledger Sawtooth">Hyperledger Sawtooth</a></li><li><a href="http://Step by Step Guide to Set up Hyperledger Fabric Network">Hyperledger Fabric Network</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54e0bfed9e90" width="1" height="1" alt=""><hr><p><a href="https://medium.com/akeo-tech/hyperledger-indy-blockchain-identity-project-54e0bfed9e90">Hyperledger Indy: Blockchain Identity Project</a> was originally published in <a href="https://medium.com/akeo-tech">Akeo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Step by Step Guide to Set up Hyperledger Fabric Network]]></title>
            <link>https://medium.com/akeo-tech/step-by-step-guide-to-set-up-hyperledger-fabric-network-b80977c29b8a?source=rss-4639c30568b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b80977c29b8a</guid>
            <category><![CDATA[blockchain-development]]></category>
            <category><![CDATA[hyperledger]]></category>
            <category><![CDATA[hyperledger-fabric]]></category>
            <category><![CDATA[technical-development]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Puneet Kumar]]></dc:creator>
            <pubDate>Fri, 12 Apr 2019 09:27:14 GMT</pubDate>
            <atom:updated>2019-10-03T09:28:01.377Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*5lyVGEbxxaaZzp4_t5cZHQ.jpeg" /><figcaption>Hyperledger Fabric Network</figcaption></figure><p><strong>Introduction:</strong></p><p>Hyperledger Fabric is a blockchain platform for distributed ledger solutions underpinned by a modular architecture delivering high degrees of confidentiality, resiliency, flexibility, and scalability. It is designed to support pluggable implementations of different components and accommodate the complexity and intricacies that exists across the economic ecosystem.</p><p><strong>Components of Hyperledger Fabric Network:</strong></p><ol><li><strong>Ledger :</strong> A ledger consists of two distinct, though related, parts — a “blockchain” and the “state database”, also known as “world state”. Unlike other ledgers, blockchains are immutable — that is, once a block has been added to the chain, it cannot be changed.</li><li><strong>Membership Service Provider : </strong>The Membership Service Provider (MSP) refers to an abstract component of the system that provides credentials to clients, and peers for them to participate in a Hyperledger Fabric network.</li><li><strong>Smart Contract : </strong>A smart contract is code — invoked by a client application external to the blockchain network — that manages access and modifications to a set of key-value pairs in the World State.</li><li><strong>Peers : </strong>A network entity that maintains a ledger and runs chaincode containers in order to perform read/write operations to the ledger. Peers are owned and maintained by members.</li><li><strong>Ordering Service : </strong>A defined collective of nodes that orders transactions into a block. The ordering service exists independent of the peer processes and orders transactions on a first-come-first-serve basis for all channel’s on the network.</li><li><strong>Channel :</strong> A channel is a private blockchain overlay which allows for data isolation and confidentiality. A channel-specific ledger is shared across the peers in the channel, and transacting parties must be properly authenticated to a channel in order to interact with it.</li><li><strong>Certificate Authority : </strong>Hyperledger Fabric CA is the default Certificate Authority component, which issues PKI-based certificates to network member organizations and their users.</li><li><strong>Organizations : </strong>Also known as “members”, organizations are invited to join the blockchain network by a blockchain service provider. An organization is joined to a network by adding its Membership Service Provider to the network.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2_u2NHV63BTJ89C4" /><figcaption>Source: Hyperledger Fabric Github</figcaption></figure><p><strong>The following are prerequisites for installing the required development tools:</strong></p><ul><li>Operating Systems: Ubuntu Linux 14.04 / 16.04 LTS (both 64-bit), or Mac OS 10.12</li><li>Docker Engine: Version 17.03 or higher</li><li>Docker-Compose: Version 1.8 or higher</li><li>Node: 8.9 or higher (Note: version 9 is not supported)</li><li>npm: v5.x</li><li>git: 2.9.x or higher</li><li>Python: 2.7.x</li><li>A code editor of your choice, we recommend VSCode.</li></ul><p><strong>**If installing Hyperledger Composer using Linux, the following points need to be kept in mind:</strong></p><ul><li>Login as a normal user, rather than root.</li><li>Do not use sudo su to root.</li><li>When installing prerequisites, use curl, then unzip using sudo.</li><li>Run prereqs-ubuntu.sh as a normal user. It may prompt for root password as some of its actions are required to be run as root.</li><li>Do not use npm with sudo or su to root to use it.</li><li>Avoid installing node globally as root.**</li></ul><h3><strong>Prerequisites</strong></h3><ul><li>To download prerequisites for Hyperledger Fabric development, run following command -</li></ul><blockquote>curl -O <a href="https://hyperledger.github.io/composer/latest/prereqs-ubuntu.sh">https://hyperledger.github.io/composer/latest/prereqs-ubuntu.sh</a></blockquote><p>This command will download and install -</p><blockquote>docker-compose , docker-engine, npm, git, python etc</blockquote><ul><li>Give permissions — chmod u+x prereqs-ubuntu.sh</li><li>Run Script — ./prereqs-ubuntu.sh (restart system after it)</li><li>Essential CLI tools — npm install -g composer-cli@0.20</li></ul><h3><strong>Steps</strong></h3><ol><li><strong>Create a directory — mkdir multichain_network</strong></li></ol><pre>cd multichain_network</pre><pre>curl <strong>-</strong>sSL <a href="http://bit.ly/2ysbOFE">http:<strong>//</strong>bit<strong>.</strong>ly<strong>/</strong>2ysbOFE</a> <strong>|</strong> bash <strong>-</strong>s 1.2<strong>.</strong>0</pre><pre>export PATH=&lt;path to download location&gt;/multichain_network/fabric-samples/first-network/bin:$PATH</pre><p><strong>2. Generate Certificates</strong></p><pre>cd first-network</pre><pre>export FABRIC_CFG_PATH=$PWD</pre><pre>cryptogen generate — config=./crypto-config.yaml</pre><p>This will create all certificates for orderers and peers in crypto-config folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*viS4keoNillGX0eI_E_NBQ.png" /></figure><p>Copy certificates for all peers and orderer to temporary folder.</p><pre><em>In first-network folder run this command — mkdir -p</em> <em>tmp/composer/org1</em></pre><pre>awk ‘NF {sub(/\r/, “”); printf “%s\\n”,$0;}’ ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt &gt; ./tmp/composer/org1/ca-org1.txt</pre><pre>awk ‘NF {sub(/\r/, “”); printf “%s\\n”,$0;}’ ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/ca.crt &gt; ./tmp/composer/ca-orderer.txt</pre><pre>export ORG1=./crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp</pre><pre>cp -p $ORG1/signcerts/A*.pem ./tmp/composer/org1</pre><pre>cp -p $ORG1/keystore/*_sk ./tmp/composer/org1</pre><p><strong>3. Create genesis block and channeltx</strong></p><pre>configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./composer-genesis.block</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*IeEipnvh9vT8UYebxIPC-w.png" /></figure><pre>configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./composer-channel.tx -channelID composerchannel</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*EG1cvHc4Th5Mn4QDaXP96w.png" /></figure><p><strong>4. Update CA keys in docker composer file</strong></p><p>Open project in code editor.</p><p><em>We have to change CA keys in “docker-compose-e2e-template.yaml” file, therefore navigate to this file in vscode.</em></p><p>Under services section we have two certificate authorities named “ca0” and “ca1”.</p><blockquote><strong>For</strong> <strong>ca0 </strong>— go to command section under ca0 and find CA1_PRIVATE_KEY and replace it with private key -</blockquote><pre><strong>C7d82435d76cb36bb1499edf1b9b256144753a458a8467ed1ff67607cef09179_sk</strong></pre><p>This key can be found in -</p><pre><em>“first-network/crypto-config/peerOrganizations/org1.example.com/ca/c7d82435d76cb36bb1499edf1b9b256144753a458a8467ed1ff67607cef09179_sk”</em></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NvQbefWsaGDP8_unMi9HKA.png" /></figure><blockquote><strong>For ca1 </strong>— goto command section under ca1 and find CA2_PRIVATE_KEY and replace it with private key -</blockquote><pre>B069c3b1761b013447f7da8f1c266b26146daa0eb43d04a531f73675403b4d61_sk</pre><p>This key can be found in -</p><pre><em>“first-network/crypto-config/peerOrganizations/org1.example.com/ca/b069c3b1761b013447f7da8f1c266b26146daa0eb43d04a531f73675403b4d61_sk</em></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iajnKRyhmnq-M2Z2-mLXaA.png" /></figure><h3><strong>Steps of Starting Hyperledger Fabric</strong></h3><ol><li>Open docker-compose-base.yaml file which is present in the bin folder and introduce following changes.</li></ol><pre><strong>Change orderer volume binding to </strong>-</pre><pre>../composer-genesis.block:/var/hyperledger/orderer/orderer.genesis.block</pre><p>As shown in the figure below -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m5jCspDiMxUkuvLGZQwEDw.png" /></figure><p>Change peer volume binding to (for all 4 peers)-</p><pre>- ../:/etc/configtx</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LOC7jnZ4HnX3hGCNNmszow.png" /></figure><p>2. To start fabric, run the following command -</p><pre>docker-compose -f docker-compose-cli.yaml -f docker-compose-couch.yaml up -d 2&gt;&amp;1</pre><p>The output of the above command is shown below -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LaeU4yzu9FoWJJSDnHSpHA.png" /></figure><p>3. After completing all these steps , you can run command -</p><pre>docker ps -a</pre><p>This will list all running containers regarding our network setup, in our case it will list 10 containers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6XKNl94CTSYSg2LXW0M7tA.png" /></figure><p>Proposed network setup is complete, our network have -</p><ul><li>One orderer</li><li>Two Organizations</li><li>Four peers (two peers on each organization)</li><li>Couchdb for all peers</li></ul><p>4. Creating channel</p><pre>docker exec peer0.org1.example.com peer channel create -o orderer.example.com:7050 -c composerchannel -f /etc/configtx/composer-channel.tx — tls true — cafile /etc/configtx/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem</pre><p>5. Joining first peer where channel is created —</p><pre>docker exec -e</pre><pre>“CORE_PEER_MSPCONFIGPATH=/etc/configtx/tmp/composer/org1/Admin@org1.example.com/msp” peer0.org1.example.com peer channel join -b composer-genesis.block</pre><p>6. For other peers, we have to first fetch the config of block from orderer</p><p>For Fetching<strong> -</strong></p><pre>docker exec -e</pre><pre>“CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin@org1.example.com/msp”</pre><pre>peer1.org1.example.com peer channel fetch config -o</pre><pre>orderer.example.com:7050 -c TwoOrgsChannel</pre><p>For joining channel<strong> –</strong></p><pre>docker exec -e</pre><pre>“CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin@org1.example.com/msp”</pre><pre>peer1.org1.example.com peer channel join -b composerchannel_config.block</pre><h3><strong>Install chainCode on every machine</strong></h3><pre>composer network install -a device-network.bna -c</pre><pre>PeerAdmin@multi_org1</pre><p><strong>Start chaincode on one machine</strong></p><pre>composer network start -n device-network -V 0.0.2-deploy.${bna_deployment_version} -A admin -S adminpw -c PeerAdmin@multi_org1</pre><h3><strong>Conclusion</strong></h3><p>We learnt about installing Hyperledger Fabric development tools and Hyperledger Composer using Linux. We also successfully deployed a Hyperledger Fabric network having one orderer, two organizations and two peers in each organization.</p><p><strong>NOTE</strong> — Hyperledger Composer is now officially deprecated, that means, they will mostly stop bringing new features to it. We can use other methods to write chaincode and interact with Hyperledger Fabric blockchain. Few of the popular ones are provided below:<br>1. Using JavaScript or Golang to write chaincode and Node.js SDK or Golang SDK to implement APIs to interact with Hyperledger Fabric.<br>2. Using Convector which is a JavaScript-based development framework built for enterprise blockchains.</p><p><em>Reach out to us at </em><a href="http://www.akeo.tech/"><em>www.akeo.tech</em></a><em> for blockchain related projects and queries</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b80977c29b8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/akeo-tech/step-by-step-guide-to-set-up-hyperledger-fabric-network-b80977c29b8a">Step by Step Guide to Set up Hyperledger Fabric Network</a> was originally published in <a href="https://medium.com/akeo-tech">Akeo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>