<?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[TheBlockchainHub - Medium]]></title>
        <description><![CDATA[The Global Hub for Blockchain Education , Research &amp; Commercialization - Medium]]></description>
        <link>https://medium.com/theblockchainhub?source=rss----602b22dcb36e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>TheBlockchainHub - Medium</title>
            <link>https://medium.com/theblockchainhub?source=rss----602b22dcb36e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:58:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/theblockchainhub" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ERC-20 Introduction — Part 3]]></title>
            <link>https://medium.com/theblockchainhub/erc-20-introduction-part-3-f2ef6e7af81?source=rss----602b22dcb36e---4</link>
            <guid isPermaLink="false">https://medium.com/p/f2ef6e7af81</guid>
            <category><![CDATA[erc20]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[tbh-stories]]></category>
            <dc:creator><![CDATA[Dejan Jovanovic]]></dc:creator>
            <pubDate>Wed, 20 Feb 2019 14:01:01 GMT</pubDate>
            <atom:updated>2019-02-20T14:01:01.309Z</atom:updated>
            <content:encoded><![CDATA[<h3>ERC-20 Introduction — Part 3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3juCmZRsI_s9bpI8sh-1aQ.png" /></figure><h3>Token Transfer</h3><p>There are two mechanisms for transferring tokens from one account to another. First case is simply using <em>transfer()</em> method. The <em>transfer()</em> method transfer the number of tokens from directly from message sender to specified another account. This method doesn’t make any checks on recipient address so all responsibility lays on sender to make sure that provided information is correct.</p><p>Let’s now explore the cases when interaction is between two smart contracts. Example will be based on service smart contract ServiceContract that is responsible for selling services to consumers. ServiceContract has method called provideService() that requires 10 SCT (ServiceContract Tokens) in order to operate.</p><p>The consumer has in his account 100 SCT. So, her is the two step process that needs to be executed. First step is that consumer provides approval for ServiceContract address to transfer required number of SCT tokens. The consume, in this case also a token holder call the method approve() to provide this information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*OZ-q_VWw3iv5QX0P2zc7IQ.png" /></figure><p>In our example consumers address is 0x2ff…….0004d21 and ServiceContract address is 0x98A…….98BBF8. From the allowance table above we can see that consumer has already sett allowance of 10 SCT for ServiceContract. Once this is done ServiceContract can transfer allocated tokens for the operation. So when consumer now calls method provideService(), provideService() will call transferFrom() method in order to transfer 10 SCT for the service. In the case that consumer do not have sufficient founds provideService() method will fail.</p><p><strong><em>Important Notes: </em></strong>it is important to notice that allowances are preliminary one, “soft”, as both individual and cumulative allowances can exceed and address balance. Any contract using allowance() must consider the balance of the consumer, holder when calculating the number of tokens available to it.</p><p>Smart Contract service payments with tokens</p><p>In this section we are going to go over case when tokens are used to pay for a service provided by another smart contract.</p><p>For paying for service function in Ether code looks like this:</p><pre>function processRequest(unit256 payload) public payable {<br>   require(msg.value == 2 ether);<br>   process(msg.sender, payload);<br>}</pre><p>Unfortunately, in the case that we have our own token, this is not possible as payable is always in Ethers and can not be in amount of tokens. Instead consumer and service provide must communicate with ServiceContract in order to move tokens from consumer to service provider.</p><p>There are three different ways how to achieve this transfer:</p><p><strong>1. approve() and transferFrom()</strong></p><p>Bothe functions are part of the ERC-20 standard and should be part of any compliant token implementation. The role of the approve() method is to authorize a third party to transfer tokens from the sender’s account. For detail sequence diagram please see below diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*qMDf6GTaoHaOmIFso4cL_A.png" /></figure><p>transferFrom() is called as a part of processRequest() implementation. Example implementation of the processRequest() method is:</p><pre>function processRequest(unit256 payload) public payable {<br>   require(tokenContract.transferFrom(msg.sender, address(this), <br>      10));<br>   process(msg.sender, payload);<br>}</pre><p><strong>2. approveAndCall()</strong></p><p>Previous case requires two separate requests from the sender. In the case of approveAndCall() implementation, it allows sender to carry out the same work with a single transaction. Detail sequence diagram is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*aCyDBk3BEPWSNg1Is2HL2g.png" /></figure><p>receiveApproval() method is called inside the implementation of approveAndCall() method implementation. This requires approveAndCall() methid to I be implemented as following:</p><pre>function approveAndCall(address _recipient, uint256 _value, bytes _extraData){<br>   approve(_recipient, _value);<br>   TokenRecipient(_recipient).receiveApproval(msg.sender, _value,<br>   address(this), _extraData);<br>}</pre><p>The receiveApproval() method in the ServiceContract is as follows:</p><pre>function receiveApproval(address _sender, uint256 _value,TokenContract _tokenContract, bytes _extraData){<br>   require(_tokenContract == tokenContract);<br>   require(tokenContract.transferFrom(_sender, address(this), 10));<br>   <br>   unit256 payloadSize;<br>   uint256 payload;<br> <br>   assembly{<br>       payloadSize := mload(_extraData)<br>       payload := mload(add(_extraData, 0x20))<br>   }<br>   payload = payload &gt;&gt; 8*(32 — payloadSize);<br>   process(msg.sender, payload);<br>}</pre><p>First line confirms that it is token contract that is calling this method. Second line of code obtains the required tokens. The rest of the code obtains the payload and calls the processing method.</p><p>There are few points that needs to be noticed with definition of approveAndCall() as it is not part of ERC-20 standard:</p><p>1. some token contracts do not support approveAndCall()</p><p>2. some token contracts only support a single hardcoded receiveApproval() method as the target of approveAndCall()</p><p>3. some token contracts support calling arbitrary service contract methods by adding the relevant method signature to the approveAndCall() transmitted by the sender</p><p><strong>3. transferAndCall()</strong></p><p>ERC-677 standard provides the alternative to approveAndCall() method called transferAndCall() method. transferAndCall() method carries out transfer() and then calls a function on the service contract. Following sequence diagram shows the detail of the interaction:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*lM3clc8hkogMqIo_TnqAcA.png" /></figure><p>The transferAndCall() method implementation should look following:</p><pre>function transferAndCall(address _recipient, uint256 _value, bytes _extraData){<br>   transfer(_recipient, _value);<br>   require(TokenRecipient(_recipient).tokenFallback(msg.sender, <br>    _value,_extraData));<br>}</pre><p>The tokenFallback() method implementation should look like this:</p><pre>function tokenFallback(address _sender, uint256 _value, bytes _extraData)return (bool){<br>   require(msg.sender == tokenContract);<br>   require(_value == 10);<br>   ……<br>   // implementation of the code what needs to be done<br>   return true;<br>}</pre><p>transferAndCall() method is a upgrade solution from approveAndCall() method. It provides similar functionality for less gas cost and lower complexity.</p><p>There are cases where this solution is not so good, for example when we have variable price of the transactions. In this case sender doesn’t know the cost of the price in advance as price can for example depend of the service demand.</p><p>Second case where this implementation presents the limitation is in the case of repeated transactions. An example of this as a gambling contract where multiple bets can be placed across different games. So instead of calling approve() method every time, sender could call it just once and save on gas.</p><p>Conclusion: each method presented here has benefits and drawbacks. When building a service contract that accepts tokens as payment it is important to clearly define requirements as this will allow proper selection of the method that best fits the contracts’s needs.</p><p><a href="http://theblockchainhub.com/aboutus/">The Blockchain Hub</a> is an inclusive education and innovation hub, with a strong network of diverse alumni from many industry verticals. Would you like to add your voice to ours, and have your articles featured in The Blockchain Hub? Just send us a note at <a href="/service/mailto:content@theblockchainhub.com">content@theblockchainhub.com</a></p><p>Disclaimer: The views and opinions expressed in this article are those of the author. They do not purport to reflect the policies, views, opinions or positions of The Blockchain Hub, any other agency, entity, organization, employer or company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2ef6e7af81" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theblockchainhub/erc-20-introduction-part-3-f2ef6e7af81">ERC-20 Introduction — Part 3</a> was originally published in <a href="https://medium.com/theblockchainhub">TheBlockchainHub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ERC 20 Introduction — Part 2]]></title>
            <link>https://medium.com/theblockchainhub/erc-20-introduction-part-2-f891464b7349?source=rss----602b22dcb36e---4</link>
            <guid isPermaLink="false">https://medium.com/p/f891464b7349</guid>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[erc20]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[nbh-stories]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Dejan Jovanovic]]></dc:creator>
            <pubDate>Tue, 22 Jan 2019 14:01:01 GMT</pubDate>
            <atom:updated>2019-01-22T14:01:01.004Z</atom:updated>
            <content:encoded><![CDATA[<h3>ERC 20 Introduction — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*qeZJNttUVr-BZOs6L5oPAg.png" /></figure><h3>So How It Works</h3><p>ERC-20 provides a formalized specification of the Token Smart Contract. Token Smart Contract is a smart contract that contains the map of account addresses and related balances. The balance represents a value that is defined by the contract creator. Here is the example of the smart contract balance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/293/1*MoDU__wEjL_gevh6DuCIsg.png" /></figure><p>When tokens are transferred from one account to another the token contract updates the balance of two accounts. For example, if from address 0x1F8…….02AA3h we transfer 10 tokens to address 0x2bb….9d8f11 it will result in balance being updated to following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*lsQ-CW6QtmJHrFwjx-5Auw.png" /></figure><p>If token contract allows there are two ways how to change the total supply of tokens. As we have mentioned ERC-621 provides the specification for two methods: increase supplies (minting) and decries supplies (burning). If token contract has implemented <em>increaseSupply(uint256 _value, address _to) </em>method then following calling <em>increaseSupply(100, </em>0x2ff….0004d21<em>)</em> will result in following balance update:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/292/1*wB-eZbWS6TL42qMqFLmicA.png" /></figure><p>By calling method <em>decreaseSupply(uint256 _value, address _to)</em> total supply can be decreased. This is also called burning. So for example if we call <em>decreaseSupply(70, </em>0xdff……aaf321<em>)</em> this will result in the following balance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/293/1*rPygZehzttD-T2gi3elINg.png" /></figure><p>So, as we understand how balance of tokens works let explore how is ERC-20 implementation work. There are few items that we need to define before we start with implementation.</p><p>There are few attributes that needs to be defined:</p><pre>string public constant name</pre><pre>string public constant symbol</pre><pre>uint8 public constant decimals</pre><pre>string public version</pre><p>First, we need to select token name. We need to understand that there is no central repository that will guaranty your token name uniqness. There is no restriction of how long the name can be but still keep it short as some wallets will truncate it anyways. For example, it can be “Hive Project Token”.</p><p>Token symbol is the symbol by which token contract will be known, for example “HVN”. It should be no longer than 3 to 4 characters.</p><p>Attribute decimals are common source of confusion. Depends on what is contract for value can ware. Let’s go through the cases:</p><p>1. If the smart contract is tracking number of software licenses that customers have then the decimal value is going to be 0 as the values that accounts have a re going to be round numbers. See the below example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*LPWmVJM2QPFjwHuLD_bvGA.png" /></figure><p>In this example total number of available licenses is 100. Owner of the contract holds the majority of licenses. As users purchases a license a single token will be transferred from the holding account (in our case 0x3h9..….87223A) to the purchaser.</p><p>2. Second example uses GoldToken, the token contract that represents ownership of physical gold. The token creator wants unit of to represent 1 kg of gold, but in the same time wants to allow users to hold and trade amounts of gold down to the gram level. In this case value of decimals is set to 3. Do not forget Ethereum doesn’t support decimal numbers so we deal with this on the code level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/293/1*K8apDXQACsq3k_LgTo_XEA.png" /></figure><p>So for total supply of 50 kg of gold represented (1 g per token * 50000 tokens). However, as decimals attribute is set to 3 the view to the users will be as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*73xtq2ubXWU-9AhJhJzf_g.png" /></figure><p>3. And at last if you are creating utility token it is recommended to use 18 decimals. In some cases contract owners are using 8 decimals, but I will recommend to stay away from it. The idea of divisibility is to allow for token contract to represent fine grained decimal value.</p><p>In summary when selecting a suitable value for decimals following rules should be followed:</p><p>· Does the token contract represent an invisible entity, then set decimals to 0</p><p>· Does the token contract represent an item with a fixed number of decimals, then set decimals to that number?</p><p>· If neither of the above apply set decimals to 18</p><p>It is important to understand impact of decimal point on the token creation. Following equation shows the calculation of total supply of tokens that token contract is going to have:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*ODxZzFSekc_oepneVJ9Xzg.png" /></figure><p>And finally string public version attribute is there to track the version of the contract and to ensure that test results provided with a contract are the one that are correspondent to the version of the token contract.</p><p><a href="http://theblockchainhub.com/aboutus/">The Blockchain Hub</a> is an inclusive education and innovation hub, with a strong network of diverse alumni from many industry verticals. Would you like to add your voice to ours, and have your articles featured in The Blockchain Hub? Just send us a note at <a href="/service/mailto:content@theblockchainhub.com">content@theblockchainhub.com</a></p><p>Disclaimer: The views and opinions expressed in this article are those of the author. They do not purport to reflect the policies, views, opinions or positions of The Blockchain Hub, any other agency, entity, organization, employer or company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f891464b7349" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theblockchainhub/erc-20-introduction-part-2-f891464b7349">ERC 20 Introduction — Part 2</a> was originally published in <a href="https://medium.com/theblockchainhub">TheBlockchainHub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Plasma in Action]]></title>
            <link>https://medium.com/theblockchainhub/plasma-in-action-8b7b483b3aa5?source=rss----602b22dcb36e---4</link>
            <guid isPermaLink="false">https://medium.com/p/8b7b483b3aa5</guid>
            <category><![CDATA[ethereum-blockchain]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[nbh-stories]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[plasma]]></category>
            <dc:creator><![CDATA[Dejan Jovanovic]]></dc:creator>
            <pubDate>Tue, 08 Jan 2019 14:01:01 GMT</pubDate>
            <atom:updated>2019-01-08T14:01:00.983Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95ZvkmV0L1BZjw5dsQtr0g.png" /></figure><p>Scalability has been a known problem of Ethereum network and there is huge effort to resolve this. Ethereum can currently only process 15 transactions per second, where Visa is processing around 45000 transactions per second. So far there has been few solutions in place that are tremendously increasing throughput of the network. The first set of efforts, “Layer 1” means that the solution is based on the blockchain directly. These two solutions that are trying to achieve better scalability on the blockchain are:</p><ol><li>Proof of Stake (PoS)</li><li>Sharding</li></ol><p>The second set of efforts, called “Layer 2” is a set of solutions that are based on off-chain solutions. Currently there are two main designs that are trying to improve scalability:</p><ol><li>State Channel</li><li>Plasma</li></ol><p>Plasma is a side-chain and the two main design implementations of Plasma are called Plasma MVP and Plasma Cash. In this article, as title is saying I will be talking about Plasma Cash as a solution for addressing scalability problem.</p><p>Plasma Cash is design pattern that is actually adding layer of smart contracts which can interact with the main blockchain and allows off-chain messages to dictate the transfer of on-chain assets. In principles Plasma is similar to Bitcoin Lightning Network, it makes off-chain transactions and using main blockchain only as a guarantee of correctness and security, but Plasma Cash is the one that is promising more long term solution in bringing Ethereum to enterprise level. Plasma Chain scales the main chain by offloading transaction throughput to site-chain. The two leading implementations of Plasma Cash are Loom Network and OmiseGo and in this article I will walk you through Loomis implementation.</p><p>Three main architectural components of Plasma Cash are:</p><ol><li>Client application</li><li>Root Chain</li><li>Plasma Chain</li></ol><p>Root Chain hosts two smart contracts: ERC721 token contract (or any other custom implementation) and Plasma Contract. Role of the Plasma contract is to provide following functionality: handle deposit events and handle exit events.</p><h3>Deposit</h3><p>In order to transact ERC721 token on Child Chain one must first deposit its tokens to the Plasma Contract and in return receives Plasma Coin. Role of the Plasma Contract is to do following: handle deposit events and handle exit events.</p><p>Plasma Chain is operated and hosted by Operator. Role of the Operator is to listen to deposit events on the main chain, register the tokens, making the consensus that forms in the side chain and posting its information on to the main chain. An Operator is the bridge between the main chain and Plasma Cash side chain.</p><p>Proof-of-authority (PoA) is an algorithm used with blockchains that delivers comparatively fast transactions through a consensus mechanism based on identity as a stake. In PoA based blockchains, transactions (blocks) are approved by authorized validator account — Operator.</p><p>Plasma Chain is an Operator hosted blockchain. Plasma Chain core characteristics are:</p><ul><li>It consists of block and each block can contain one or more transactions. Each block maintains its own Sparse Merkle Tree.</li><li>Users are free to spend or send to other users their Plasma Coins on the Plasma Chain.</li><li>Periodically Plasma Chain submits the Merkle root of the current block to Plasma Contract, showing any changes in ownership of Plasma Coins.</li></ul><p>Following diagram shows the interaction between user, smart contracts and Plasma Chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*eFk_ro9XQioaQHbOvDKk4Q.png" /></figure><p>First step is that user sends some ETH to ERC721 smart contract. This triggers the transaction informing Plasma Contract that Root Chain has received deposit. In return User receives Plasma Coin (or what ever Operator is providing through his smart contract implementation). Each token has associated tokenId. Following structure presents the set of information that are related to the received coin:</p><pre><strong>struct </strong>Coin {<br>    Mode mode;<br>    State state;<br>    <strong>address </strong>owner; <br>    <strong>address </strong>contractAddress;<br>    Exit exit;<br>    <strong>uint256 </strong>uid; <br>    <strong>uint256 </strong>denomination;<br>    <strong>uint256 </strong>depositBlock;<br>}</pre><p>When Plasma Contract is done with depositing users coins it emits Deposit event. For each deposited token user will receive back slot number and blockNumber. This information is cought by listening for Deposit emit.</p><pre>// create a utxo at `slot`<br><strong>emit </strong>Deposit(<br>    slot,<br>    currentBlock,<br>    denomination,<br>    from,<br>    msg.sender<br>);</pre><p>UTXO (Unspent Transaction Output) is a transaction output which can be spent as input in a new transaction.</p><p>On the other side Plasma Chain is listening for Deposit events and when it receives the event calls the side-chain and creates the new block for deposit.</p><p>There are two types of blocks on Plasma Chain:</p><ol><li>Deposit Block — includes only one transaction, DepositTransaction and it is always initial block</li><li>Plasma Block- may include many transactions</li></ol><p>Type of the blocks can be identified by following</p><p><strong>if (blockNumber % N != 0) then DepositBlock else PlasmaBlock</strong></p><p>For every block in Plasma Cash chain the Merkle root of the Sparse Merkle Tree is stored in the main chain. This Merkle root is then checkpointed by an operator into the main Ethereum chain.</p><h3>Spending Plasma Coin</h3><p>So now that User has obtained Plasma Coins he can spend it or send it to someone else. As we have seen each token has associated tokenId. In order to send token to another user transaction object needs to be constructed. Transaction object has following data:</p><ol><li><strong>uid:</strong> unique position in Sparse Merkle Tree</li><li><strong>previousBlock:</strong> pointing to previous transaction block. If this is a deposit, value is “0”. This creates a chain of history.</li><li><strong>denomination:</strong> This is how much the specific token holds.</li><li><strong>new_owner</strong></li><li><strong>signature:</strong> signature on the transaction’s hash</li><li><strong>hash: </strong>unsigned hash of transaction details</li><li><strong>merke_hash:</strong> signed hash of transaction’s details that is going to be included in the merkle tree</li><li><strong>sender</strong></li></ol><p>Transaction is signed with Users private key and encoded using Recursive Length Prefix (RLP) encoding Schema. Transaction is sent to HTTP end point /send_tx on Plasma Chain API. Plasma Chain decodes the transaction object and performs validation. If transaction is valid it gets added to current block in Plasma Chain.</p><p>In order for receiving party to claim the token, sending party also needs to send to receiving party the history of the sent token. The history of the token consist of inclusion proof and exclusion proof.</p><p>Merkle proofs are used in order to decide upon following questions:</p><ol><li>If the data belongs in the Merkle tree.</li><li>To prove validity of data being part of a dataset.</li><li>To ensure the validity of a certain dataset being inclusive in a larger dataset without revealing either the complete dataset or its subset.</li></ol><p>Inclusion proof validates that token has at least one transaction associated with it from block with deposit transaction onwards and exclusion proof that there is no transaction related to token in question for block number that is bigger then block with deposit transaction.</p><p>So receiving user needs to verify token history to insure that token is valid before spending it. Following picture shows interaction between participants:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cvzqrOU5nryFYyLdG6GpQA.png" /></figure><h3>Exit</h3><p>After sending and receiving tokens within the Plasma Chain, a user can exit to the main chain with the tokens they own at that current point in time. In order to exit, user has to submit a bond and proof that user currently owns the tokens.</p><p>In order to exit user needs to call startExit transaction and to provide following: slot number, blockNumber for the Plasma Coin in the previous block, Merkle proof for the Plasma Coin in the previous block, blockNumber for the Plasma Coin of the exiting block, Merkle proof for the Plasma Coin of the exiting block, and bond amount. Below is the function implementation:</p><pre><strong>function </strong>startExit(<br>    <strong>uint64 </strong>slot,<br>    <strong>bytes </strong>prevTxBytes, <strong>bytes </strong>exitingTxBytes,<br>    <strong>bytes </strong>prevTxInclusionProof, <strong>bytes </strong>exitingTxInclusionProof,<br>    <strong>bytes </strong>signature,<br>    <strong>uint256</strong>[2] blocks)<br>    <strong>external<br>    payable </strong>isBonded<br>    isState(slot, State.DEPOSITED)<br>{<br>    require(msg.sender == exitingTxBytes.getOwner());<br>    doInclusionChecks(<br>        prevTxBytes, exitingTxBytes,<br>        prevTxInclusionProof, exitingTxInclusionProof,<br>        signature,<br>        blocks<br>    );<br>    pushExit(slot, prevTxBytes.getOwner(), blocks);<br>}</pre><p>By listening to the event StartedExit that is emitted from Root Chain, the user has a chance to protect themself from fraudulent transaction. This listening task can be automated by user application. If fraudulent exit has been detected user or user application can challenge it.</p><p>There are three types of exit challenges:</p><ol><li>Exit Spent Coin Challenge — In this attack User 1 has sent coin to a User 2, after both parties verify its inclusion User 1 immediately attempt to exit the spent coin. User 2 must login before the end of the challenge period and provide proof of a direct spent of the coin. This challenge is implemented via challengeAfter function.</li><li>Exit Double Spent Challenge — in this case it is required that Operator allows inclusion of double spend transaction. The attacker, User 1 sends a coin to the victim User 2. After transaction has confirmed inclusion User 1 sends another transaction to User 3. From mainchain point of view both of users, User 2 and User 3 are valid owners of the coin. This challenge is implemented via challengeBetween function.</li><li>Exit With Invalid History Challenge — Consider that case that victim User 2 has coin that he does not intend to spend. Attacker, User 1 in collaboration with Operator creates the transaction that references invalid transaction from User 2 to User 1, effectively giving User 1 ownership of the coin and sends the transaction to User 3. After transaction gets included, transaction to User 3 can be used as a valid ancestor transaction. Taking advantage of the situation User 3 can use this coin to spend or sent to another user. This is exactly the reason why it is required for receiving party to validate the coin history. This challenge is implemented via challengeBefore and respondChallengeBefore function.</li></ol><p>In summary challenge cases are modeled as following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/1*i8ycX1ii65RN8wTY7N_IjQ.png" /></figure><h3>Conclusion</h3><p>Plasma Cash is just one construction of Plasma that is helping to improve performance and scalability of Ethereum. Plasma Cash can be used to offload computational need from mainchain and provide high availability solution from app perspective, also enables cost effective and secure solution. For my analysis and research I used Loom implementation of Plasma Cash.</p><h3>References</h3><p>[1] <a href="https://medium.com/crypto-economics/what-is-plasma-plasma-cash-6fbbef784a">https://medium.com/crypto-economics/what-is-plasma-plasma-cash-6fbbef784a</a></p><p>[2] <a href="https://medium.com/novamining/plasma-cash-new-scalability-solution-for-the-ethereum-network-f7c0b889db7d">https://medium.com/novamining/plasma-cash-new-scalability-solution-for-the-ethereum-network-f7c0b889db7d</a></p><p>[3] <a href="https://medium.com/finc-engineering/a-view-of-plasma-cash-for-ethereum-b608b934ec67">https://medium.com/finc-engineering/a-view-of-plasma-cash-for-ethereum-b608b934ec67</a></p><p>[4] <a href="https://ethresear.ch/t/plasma-cash-plasma-with-much-less-per-user-data-checking/1298">https://ethresear.ch/t/plasma-cash-plasma-with-much-less-per-user-data-checking/1298</a></p><p>[5] <a href="https://medium.com/loom-network/plasma-cash-initial-release-plasma-backed-nfts-now-available-on-loom-network-sidechains-37976d0cfccd">https://medium.com/loom-network/plasma-cash-initial-release-plasma-backed-nfts-now-available-on-loom-network-sidechains-37976d0cfccd</a></p><p>[6] <a href="https://github.com/loomnetwork/plasma-cash">https://github.com/loomnetwork/plasma-cash</a></p><p>[7] <a href="https://github.com/loomnetwork/plasma-cash/blob/master/FullSpec.md">https://github.com/loomnetwork/plasma-cash/blob/master/FullSpec.md</a></p><p>[8] <a href="https://karl.tech/plasma-cash-simple-spec/">https://karl.tech/plasma-cash-simple-spec/</a></p><p>[9] <a href="https://ethresear.ch/t/loom-network-plasma-cash-for-erc721-tokens/2385">https://ethresear.ch/t/loom-network-plasma-cash-for-erc721-tokens/2385</a></p><p><a href="http://theblockchainhub.com/aboutus/">The Blockchain Hub</a> is an inclusive education and innovation hub, with a strong network of diverse alumni from many industry verticals. Would you like to add your voice to ours, and have your articles featured in The Blockchain Hub? Just send us a note at <a href="/service/mailto:content@theblockchainhub.com">content@theblockchainhub.com</a></p><p>Disclaimer: The views and opinions expressed in this article are those of the author. They do not purport to reflect the policies, views, opinions or positions of The Blockchain Hub, any other agency, entity, organization, employer or company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b7b483b3aa5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theblockchainhub/plasma-in-action-8b7b483b3aa5">Plasma in Action</a> was originally published in <a href="https://medium.com/theblockchainhub">TheBlockchainHub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ERC20 Introduction — Part 1]]></title>
            <link>https://medium.com/theblockchainhub/erc20-introduction-part-1-e8c2062aed0f?source=rss----602b22dcb36e---4</link>
            <guid isPermaLink="false">https://medium.com/p/e8c2062aed0f</guid>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[erc20]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[tbh-stories]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Dejan Jovanovic]]></dc:creator>
            <pubDate>Tue, 18 Dec 2018 14:01:01 GMT</pubDate>
            <atom:updated>2019-01-15T16:24:56.981Z</atom:updated>
            <content:encoded><![CDATA[<h3>ERC20 Introduction — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bgDBFm7zuOwKl_knYM2lZA.png" /></figure><h3>Introduction</h3><p><strong>What is ERC20 token and why do we need this?</strong> ERC stands for “Ethereum Request for Comment”. This is the Ethereum version of Request for Comments (RFC), a concept created by the Internet Engineering Task Force. It is used for capturing technical and organizational notes. In the case of ERC, this includes technical guidelines for the buildout of the Ethereum network.</p><p>So how does it works? Developers submit an Ethereum Improvement Proposal (EIP), this includes protocol specifications and contract standards. Once the Ethereum Committee finalizes and approves an EIP, it becomes and ERC.</p><p>Released and finalized EIPs are providing the Ethereum developers with a set of implementable standards. ERC-20 is one of the most well-known of all standards and most tokens issued on top of the Ethereum platform complies to it.</p><p><strong>What is the ERC-20 Standard?</strong></p><p>Originally ERC-20 was proposed back in 2015 and officially formalized in September 2017. It is a great starting point in token standardization. The ERC-20 token standard includes the following functions:</p><pre><em>totalSupply() </em>: returns total token supply</pre><pre><em>balanceOf(address _owner)</em> : returns account balance of _owner’s account</pre><pre><em>transfer(address _to, uint256 _value)</em> : takes in number _value and transfers that amount of tokens to provided address _toand triggers transfer event</pre><pre><em>transferFrom(address _from, address _to, unit256 _value)</em> : transfer _value amount of tokens from the address _from to the address _to, and triggers the transfer event</pre><pre><em>approve(address _spender, uint256 _value) </em>: allows _spender to any number of tokens up to _value amount</pre><pre><em>allowance(address _owner, address _spender)</em> : returns amount which the _spender is allowed to withdraw from the _owner</pre><p>The following events are triggered based on the listed ERC-20 functions:</p><pre><em>transfer(address indexed _from, address indexed _to, uint256 _value)</em> : this is triggered whenever tokens are transferred</pre><pre><em>approval(address indexed _owner, address indexed _spender, uint256 _value)</em> : this is triggered on any call to approve() function</pre><p>There are cases when additional functionality or improvements are needed, thus additionally to ERC-20 the following ERC standards are proposed:</p><p><strong>ERC-223</strong></p><p>ERC-223 proposal addresses the case when tokens are transferred to a smart contract. ERC-223 is backwards compatible with ERC-20 token. Status of this ERC is open and proposed on March 5, 2017.</p><p>There are two different ways to transfer ERC-20 tokens, depending on whether you intend to send the tokens directly to an account or delegate the transfer to another smart contract:</p><blockquote>1. Invoking <em>transfer()</em> function</blockquote><blockquote>2. Or by invoking <em>approve()</em> function and then calling <em>transferFrom()</em> function</blockquote><p>What happens when you transfer your tokens by mistake to a contract address that is unaware or doesn’t expect these tokens? The problem with invoking transfer() function is that a smart contract will not notify the recipient of the transfer of the transaction; therefore, he/she will not be able to recognize the incoming transaction. If you send for example 100 ERC20 tokens to a contract that is not intended to work with ERC20 tokens, the smart contract will not reject the transaction because it can’t recognize an incoming transaction request. As a result, your tokens will get stuck at the contracts balance.</p><blockquote>When the recipient is a smart contract, users must transfer their tokens using the second option (<em>approve() + transferFrom()</em>). In the case that the recipient is a externally owned account address, the user must transfer their tokens using <em>transfer()</em> function. If user makes a mistake and chooses the wrong function, the token will be lost inside the smart contract.</blockquote><p>There are already a number of tokens held by token contracts that did not expect any token transfer. These tokens are not accessible as there is no withdraw function available. Here are some examples:</p><blockquote>310.067 GNT Stuck in Golem contract</blockquote><blockquote>242 REP Stuck in Augur contract</blockquote><blockquote>814 DGD Stuck in Digix DAO contract</blockquote><blockquote>14.506 1ST Stuck in FirstBlood contract</blockquote><blockquote>30 MLN Stuck in Melonport contract</blockquote><p>The proposed solution, covered under ERC-223 is to use following for transfers of tokens to smart contract:</p><pre><em>transfer(address _to, uint _value, bytes _data) returns (bool success)</em></pre><p>This method is responsible for transferring tokens and invoking method:</p><pre><em>tokenFallback(address _from, uint256 _value, bytes data)</em></pre><p>This function will allow receiving contract to decline the token or trigger further actions. This can be used in place of the <em>approve()</em> function. Please see example:</p><pre>contract ERC223ReceivingContract {</pre><pre>/*** @dev Standard ERC223 function that will handle incoming token   <br> * transfers.<br> *<br> * @param _from  Token sender address.<br> * @param _value Amount of tokens.<br> * @param _data  Transaction metadata.<br>*/</pre><pre>function tokenFallback(address _from, uint _value, bytes _data);</pre><pre>}<br>contract ERC223Token is ERC223Interface {<br>   using SafeMath for uint;<br>   mapping(address =&gt; uint) balances; // List of user balances.<br>   /*** @dev Transfer the specified amount of tokens to the  <br>    * specified address.<br>    * Invokes the `tokenFallback` function if the recipient is a <br>    * contract.<br>    * The token transfer fails if the recipient is a contract<br>    * but does not implement the `tokenFallback` function<br>    * or the fallback function to receive funds.<br>    *<br>    * @param _to Receiver address. <br>    * @param _value Amount of tokens that will be transferred.<br>    * @param _data Transaction metadata.<br>   */<br>function transfer(address _to, uint _value, bytes _data) {<br>    // Standard function transfer similar to ERC20 transfer with no <br>    // _data .<br>    // Added due to backwards compatibility reasons .<br>    <br>    uint codeLength;<br>    assembly {<br>       // Retrieve the size of the code on target address, this <br>       // needs assembly .<br>       codeLength := extcodesize(_to)<br>    }<br>    balances[msg.sender] = balances[msg.sender].sub(_value);<br>    balances[_to] = balances[_to].add(_value); <br>    <br>    if(codeLength&gt;0) {<br>        ERC223ReceivingContract receiver = <br>                              ERC223ReceivingContract(_to);<br>    receiver.tokenFallback(msg.sender, _value, _data);<br>    }<br>    Transfer(msg.sender, _to, _value, _data);<br>}<br>…<br>}</pre><p>Reference implementation available at: <a href="https://github.com/Dexaran/ERC223-token-standard/tree/master/token/ERC223"><em>https://github.com/Dexaran/ERC223-token-standard/tree/master/token/ERC223</em></a></p><p><strong>ERC-621</strong></p><p>ERC-621 proposal addresses the case when tokens supply needs to be changed. Status of this ERC is open and proposed on May 1, 2017.</p><p>In order to address this need the proposition is to add the following functions to ERC-20 token:</p><pre><em>increaseSupply(uint256 _value, address _to)</em> : allows at any time to increase existing supply for specified address</pre><pre><em>decreaseSupply(uint256 _value, address _from) </em>: supply can be decreased at any time by specified _value for the owner _from</pre><p>This proposal is mostly relevant to digitized assets management.</p><p><strong>ERC-721</strong></p><p>ERC-721 addresses totally different needs from what ERC-20 and ERC-223 are addressing. It describes a non-fungible token. Fungible is being something such as money or commodity of such nature that one part or quantity in paying a debt or settling an account according to the Merriam Webster dictionary. Fungibility is a characteristic of an asset or token. But if you are tracking collectables such as Pokemon cards where each card has it own characteristics (attributes) and potentially are different from each other from any perspective including price, then we are looking at a non-fungible token.</p><p>This means that each token is totally different and each one can have totally different values to different users. Each one is its own separate commodity whose values are based on its own rarity and desirability by users.</p><p>The standard definition of functions is:</p><pre><em>name() constant returns (string name)</em> : this function returns the name. Interfaces and other smart contracts must not depend on existence of this function.</pre><pre><em>symbol() constant returns (string symbol)</em> : this method returns the symbol referencing the entire collection of non fungible tokens</pre><pre><em>totalSupply() constant return (uint256 totalSupply)</em> : returns the number of non fungible tokens currently tracked by the contract</pre><pre><em>balanceOf(address _owner) constant returns (uint256 balance)</em> : returns the number of non fungible tokens assigned to address _owner</pre><pre><em>ownerOf(uint256 _tokenId) constant returns (address owner)</em> : this method returns the owner of _tokenId</pre><pre><em>approve(address _to, uint256 _tokenId)</em> : this method grants the approval of the address _to to take possession of the non fungible token _tokenId. Only one address can have approval at any given time, calling method <em>approveTransfer</em> with a new address revokes approval for the previous address. Successful completion of this method creates the <em>Approve</em> event.</pre><pre><em>takeOwnership(uint256 _tokenId)</em> : this function is responsible for assigning the ownership of the non fungible token to the message sender or it throws exception if message sender does not have approval for _tokenId, or _tokenId does not represent non fungible token currently tracked by the smart contract, or message sender already has ownership of the _tokenId.</pre><pre><em>transfer(address _to, uint256 _tokenId)</em> : this method assignees the ownership of the non fungible token with id that is _tokenId to _to if and only as message sender is also a owner of the token (msg.sender == ownerOf(tokenId)). A successful transfer must fire the Transfer event. In the case that transfer is not successful it will throw the exception. Exception is thrown in following cases: message sender is not a owner of _tokenId, or _tokenId does not represent currently tracked non fungible token, or _to is 0.</pre><pre><em>tokenOfOwnerByIndex(address _owner, uint256 _index) constant return (uint tokenId)</em> : this method is optional and it is recommended to be implemented in order to enhance usability with wallets and exchanges. It returns non fungible token that is assigned to the address of the _owner, with value of the _index argument. This method throws exception in the case that _index &gt;= balanceOf(owner).</pre><pre><em>tokenMetadata(uint256 _tokenId) constant returns (string infoUrl)</em> : this method is optional but it is recommended to be implemented for enhanced usability with wallets and exchanges. This method returns multi address string referencing an external resource bundle that contains metadata about non fungible token associated with _tokenId. The string must be an IPFS of HTTP/HTTPS base path.</pre><p>Following events are supported:</p><pre><em>Transfer(address indexed _from, address indexed _to, uint256 _tokenId)</em> — this event must be triggered when non fungible tokens ownership is transferred. Additionally in the case of creation of new non fungible token this event is triggered with _from address of 0 and a _to address matching the owner of new non fungible token, and also in the case of deletion event is triggered with _to address of 0 and a _from address of the owner.</pre><pre><em>Approval(address indexed _owner, address indexed _approved, uint256 _tokenId)</em> — this event is triggered on any successful call to approve(address _spender, uint256 _value)</pre><pre><em>ApprovalForAll(address indexed _owner, address indexed _operator, bool _approved)</em> - this event is emit when operator is disabler or enabled for an owner</pre><p>Following table presents the cases when Approve event is triggered:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*__fut_4fdOrJ4unfek7j8Q.png" /></figure><p><strong>ERC-827</strong></p><p>ERC-827 presents another extension to ERC-20, and it allows for the transfer of tokens and also allows tokens to be approved by the holder in order to be spent by a third party. It can be used to solve the same problem that ERC-223 is resolving, preventing ERC-20 tokens to be stuck. Moreover, it offers flexibility to transfer data along with tokens to smart contract and execute them. ERC-827 has been included in Zeppelin open source contract. On Ethereum blockchain tokens can be reused by other applications from wallets to decentralized exchanges.</p><p>To understand ERC-827 token let’s go through a shopping cart example.</p><p>Let say that a shopping cart has items waiting to be bought. In order to complete the transaction the user has to transfer tokens to the shopping cart with some data passed with the cart which will call another smart contract that is responsible for checking whether the cart owner has enough tokens to cover the balance and proceed to checkout for the items saved in the shopping cart.</p><p>Here is OpenZeppelin implementation</p><pre>contract ERC827 is ERC20 {<br>   function approve( address _spender, uint256 _value, bytes _data ) <br>       public returns (bool);</pre><pre>function transfer( address _to, uint256 _value, bytes _data ) <br>       public returns (bool);</pre><pre>function transferFrom( address _from, address _to, uint256 <br>       _value, bytes _data )</pre><pre>public returns (bool);<br>}</pre><p>The standard definition of specified ERC-827 methods is:</p><pre><em>approve(address _from, uint256 _value, byte _data) public returns (bool)</em> : this method allows to approve the transfer of values and execute a call with the data sent during the approve function call. Potential risk is that allowance can be changed within this method and and the old one. One possible solution to mitigate the risk is to first reduce the spenders allowance to 0 and set the desire value afterwards. Here is example implementation:</pre><pre>/** @dev Addition to ERC20 token methods. It allows to approve the transfer of value and execute a call with the sent data. Beware that changing an allowance with this method brings the risk that someone may use both the old and the new allowance by unfortunate transaction ordering. One possible solution to mitigate this race condition is to first reduce the spender&#39;s allowance to 0 and set the desired value afterwards:</pre><pre><a href="https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729">https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729</a></pre><pre>@param _spender The address that will spend the funds.<br>@param _value The amount of tokens to be spent.<br>@param _data ABI-encoded contract call to call `_to` address.<br>@return true if the call function was executed successfully</pre><pre>*/</pre><pre>function approve(address _spender, uint256 _value, bytes _data)  <br>   public returns (bool) {</pre><pre>require(_spender != address(this));<br>   require(super.approve(_spender, _value));<br>   require(_spender.call(_data));</pre><pre>return true;<br>}</pre><pre><em>transfer(address _to, uint256 _value, bytes _data) public returns (bool)</em> : this method transfers tokens from specified address and executes a call with the sent data on the same transaction.</pre><pre>Method will return true if the called function is executed successfully. Example implementation:</pre><pre>/**<br>@dev Addition to ERC20 token methods. Transfer tokens to a <br>specified address and execute a call with the sent data on the <br>same transaction</pre><pre>@param _to address The address which you want to transfer to<br>@param _value uint256 the amount of tokens to be transferred<br>@param _data ABI-encoded contract call to call `_to` address.<br>@return true if the call function was executed successfully</pre><pre>*/</pre><pre>function transfer(address _to, uint256 _value, bytes _data) public <br>   returns (bool) {</pre><pre>require(_to != address(this));<br>   require(super.transfer(_to, _value));<br>   require(_to.call(_data));</pre><pre>return true;<br>}</pre><pre><em>transferFrom(address _from, address _to, uint256 _value, bytes _data) public returns (bool)</em> : this method like <em>transfer()</em> it also transfers tokens from one address to another and makes a contract call on the same transaction. The only difference is that this method can be used in coordination with <em>approve()</em> method and execute different logic while approving and transferring tokens. Example implementation:</pre><pre>/**<br>@dev Addition to ERC20 token methods. Transfer tokens from one address to another and make a contract call on the same transaction</pre><pre>@param _from The address which you want to send tokens from<br>@param _to The address which you want to transfer to<br>@param _value The amount of tokens to be transferred<br>@param _data ABI-encoded contract call to call `_to` address.<br>@return true if the call function was executed successfully</pre><pre>*/</pre><pre>function transferFrom(address _from, address _to, uint256 _value, <br>bytes _data) public returns (bool) {</pre><pre>require(_to != address(this));<br>   super.transferFrom(_from, _to, _value);<br>   require(_to.call(_data));</pre><pre>return true;<br>}</pre><p><a href="http://theblockchainhub.com/aboutus/">The Blockchain Hub</a> is an inclusive education and innovation hub, with a strong network of diverse alumni from many industry verticals. Would you like to add your voice to ours, and have your articles featured in The Blockchain Hub? Just send us a note at <a href="/service/mailto:content@theblockchainhub.com">content@theblockchainhub.com</a></p><p>Disclaimer: The views and opinions expressed in this article are those of the author. They do not purport to reflect the policies, views, opinions or positions of The Blockchain Hub, any other agency, entity, organization, employer or company.</p><p>Part 1 Part 2 Part 3</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8c2062aed0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theblockchainhub/erc20-introduction-part-1-e8c2062aed0f">ERC20 Introduction — Part 1</a> was originally published in <a href="https://medium.com/theblockchainhub">TheBlockchainHub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Blockchain adoption]]></title>
            <link>https://medium.com/theblockchainhub/blockchain-adoption-1d09b3688245?source=rss----602b22dcb36e---4</link>
            <guid isPermaLink="false">https://medium.com/p/1d09b3688245</guid>
            <category><![CDATA[tbh-stories]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[adoption]]></category>
            <category><![CDATA[the-chasm]]></category>
            <dc:creator><![CDATA[Lassonde Professional Development Centre]]></dc:creator>
            <pubDate>Tue, 11 Dec 2018 19:53:01 GMT</pubDate>
            <atom:updated>2018-11-18T16:50:33.716Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog post was written by Carlos Dominguez <a href="http://www.theblockchainhub.com/academy">CBPro</a>, <a href="http://www.theblockchainhub.com/academy">CMDes</a>. Carlos is a professional in Enterprise Architecture and Information Security. He is also alumni and volunteer with The Blockchain Hub. To learn more about our program offerings, please check <a href="https://theblockchainhub.com/academy">www.theblockchainhub.com/academy</a></p><h3>On Blockchain Adoption</h3><p>At the recent Fields Institute Blockchain Event (September 2018), one of the stand-out presentations covered leading academic research on Blockchain Technology adoption, presented by Associated Professor Theophanis C. Stratopoulos of Waterloo University.</p><p>In reviewing the papers, one of the fascinating topics was the framework for measuring adoption (see the links included at the bottom of this post), which are based on the Diffusion of Innovation work done by Everett Rogers . The papers draw from the must-read book for entrepreneurs: “Crossing the Chasm” by Geoffrey A. Moore, which also refers to the work of Everett Rogers. Below is a summary of the works to peak your interest.</p><p>Please note, this article will refer to Blockchain with an upper case, which is simply preference of the author but is not intended to spark the “Blockchain” vs “blockchain” debate — let’s save that for a future post!</p><h3>Innovation Diffusion</h3><p>Diffusion of Innovation seeks to explain how, why, and at what rate new ideas and technologies spread. It makes use of a chart to depict the adoption, which looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*UZBFY1z4EmIXSV5rXJF1lA.png" /><figcaption>Based on Rogers, E. (1962) Diffusion of innovations. Free Press, London, NY, USA. Wikimedia Commons</figcaption></figure><p>The adoption lifecycle includes different types of adopters, which could extend from individuals to countries. For more details please read the Wikipedia entry included at the end. Geoffrey Moore added a gap in the adoption lifecycle (see next figure), between the early adopters of the product (the technology enthusiasts and visionaries) and the early majority (the pragmatists).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFLbepHJDRpGoGzE5MCd2Q.png" /><figcaption>Technology (or solution) adoption process, as described in Geoffrey Moore’s book Crossing the Chasm. Wikimedia Commons.</figcaption></figure><p>This gap is ominously called “The Chasm”.</p><h3>What about Blockchain?</h3><p>Well… that is the key question of the presentation and work of Professor Theophanis C. Stratopoulos: where is Blockchain adoption right now? Or to put in another way: is it before or after “The Chasm”?</p><p>Very good question! So where is Blockchain?</p><p>It turns out this is not easy to answer. The papers draw from several sources such as Google Trends (analytics on what people search), and from statistics on publications. The results seem to indicate (at least to me) that Blockchain adoption is somewhere around “The Chasm”. In the vicinity of it.</p><p>Here is an example of what Google Trends have to say on search results, going by what I believe people search when looking for Blockchain:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/1*wW6ZC-8_zMGMsexdNnUUbw.png" /><figcaption>Google Trends. 5 years of searches. Roughly.</figcaption></figure><p>So, what do people care about (according to that chart above)? …Bitcoin! Do mind the chart needs to be read in particular way: 100 represents the top result and everything else is scaled after it.</p><p>That chart is not surprising, or should not be surprising at all. Somehow that chart looks familiar, and I think this is the one that is triggering my memory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*WJxUbvZqmu3wmntVmeDQtw.jpeg" /><figcaption>Bitcoin Price over 5 years. CoinMarketCap</figcaption></figure><p>The “spike” in both charts is centered around December 2017 when Bitcoin hit top dollar ($19k). Funny enough, it seems Ripple did too (or I am reading too much into this? Let me know your thoughts!). So, Google Trends and CoinMarketCap align (roughly).</p><h3>Trying to get to the point</h3><p>One point is that Google Trends don’t seem to mean anything, besides rampant speculation on Bitcoin (and Ripple). I don’t think Google Trends show anything chasm related.</p><p>Why is that? Well, I have some theories:</p><ul><li>Google Trends relies on public data (search engines)</li><li>The trends don’t seem to account for Consortium Blockchains</li><li>There is a lot of work that is being done quietly, mostly by Consortia</li><li>Many disagree with the term “Enterprise Blockchain” and prefer to use DLT</li></ul><p>There is something else: The Innovation Diffusion theory does not include a recent phenomenon (or so I believe) which I would call “adoption compression”, where the cycle is shortened considerably due to feedback loops (positive and negative) built by social media. Remember 3D TV? It came and went before we even knew it was here.</p><p>We usually refer to that compression as a “fad”. Here is a list of things that worked on compressed adoption cycles ( just like 3D TV)</p><ul><li>Netbooks (The laptop that tried to be a tablet)</li><li>QR Codes. Still around, but way down in usage. Possibly revived by Bitcoin</li><li>Pokemon Go. This was more a fever than a fad</li><li>Google Glass. Do I need to say more?</li><li>GPS navigation devices. I still have one, but it will be hard to replace</li><li>Blu-Ray discs. I have some, and I don’t know where to get more</li><li>MP3 players. The iPhone is responsible for killing a lot of single use gadgets</li></ul><p>There could be an argument that some of the technologies in the list above were replaced. True, but I remember them being all over and then nowhere.</p><p>As Google Trends did not show what I wanted, I am going to refer to another way of looking at adoption, and that is by using the Gartner Hype Cycle, shown here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_vEhZAbTZOzEOjJch-rVSw.png" /><figcaption>Gartner Hype Cycle. Gartner 2018</figcaption></figure><p>That rollercoaster adoption cycle I mentioned for 3D TV is closer to what Gartner describes. The bottom of the rollercoaster is what Gartner calls “The Trough of Disillusionment”. Ouch!</p><p>The question would be: where is Blockchain on this particular rollercoaster?</p><h3>Blockchain is Everywhere and Nowhere</h3><p>This is my pet theory: I think we are past “The Chasm” (in diffusion terms) and entering the “Trough of Disillusionment” in Gartner Rollercoaster terms. There is also a trap on the way for the unwary, when trying to figure out where Blockchain is in the Gartner diagram: it depends who you ask!</p><p>My own search on Blockchain news tells me that:</p><ul><li>A lot of the news are self-serving (either by sources that like Blockchain, or sources that hate Blockchain)</li><li>The news are contradictory, in the style of nutrition news: Blockchain is good for you! No, wait, Blockchain is bad for you!</li><li>It is questionable to mix DLT and Blockchain in the same sentence. People get silly trying to figure that one out</li><li>There is a lot of hidden DLT out there, out of sight and mind and in Consortia Land (or is it Blockchain?)</li></ul><p>Blockchain technology is like an “iceberg” (to call it something), which has a hidden mass. A reason for that mass to be hidden is on the connotations the word “Blockchain” brings up. I think we are going to be surprised, soon enough, on how far some industries are in the adoption curve.</p><p>Those under-the-radar adopters are just working at it quietly, to avoid the bad effects of the hype (board of directors worry about Bitcoin bad reputation). One of the presenters in the Fields event referred to that out-of-sight work as building “quiet competence”.</p><p>Blockchain technology is also evolving very fast, so whatever is discussed today will be obsolete in six months. This is one of the factors which could be delaying adoption, as many could be waiting for the brave to cross “The Chasm”. A lot could be written on Blockchain technology maturity, but that is a matter for another day.</p><p>One way to detect the “hidden mass” is to look for the killer apps of Blockchain in these use cases:</p><ul><li>Digital Identity (of the decentralized kind)</li><li>Supply Chain (of all sorts of things)</li></ul><h3>Some reading material and contradictory news</h3><p>This is where I provide some useful links for anybody who got this far.</p><p>Papers by Theophanis C. Stratopoulos</p><ul><li><a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2695858">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2695858</a></li><li><a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3188470">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3188470</a></li></ul><p>A TL;DR link for anybody who does not want to read the book “Crossing the Chasm”, which I recommend reading:</p><ul><li><a href="https://ewthoff.home.xs4all.nl/Weppage%20documents/Summary%20Crossing%20the%20Chasm.pdf">https://ewthoff.home.xs4all.nl/Weppage%20documents/Summary%20Crossing%20the%20Chasm.pdf</a></li></ul><p>Mandatory Wikipedia entries:</p><ul><li><a href="https://en.wikipedia.org/wiki/Diffusion_of_innovations">https://en.wikipedia.org/wiki/Diffusion_of_innovations</a></li><li><a href="https://en.wikipedia.org/wiki/Crossing_the_Chasm">https://en.wikipedia.org/wiki/Crossing_the_Chasm</a></li></ul><p>And a questionable nutrition of Blockchain adoption news, on both sides of the spectrum. You be the judge of what is going on.</p><ul><li><a href="https://www.coindesk.com/blockchain-enters-trough-of-disillusionment-on-gartners-hype-scale/">https://www.coindesk.com/blockchain-enters-trough-of-disillusionment-on-gartners-hype-scale/</a></li><li><a href="https://techcrunch.com/2018/09/24/walmart-is-betting-on-the-blockchain-to-improve-food-safety/">https://techcrunch.com/2018/09/24/walmart-is-betting-on-the-blockchain-to-improve-food-safety/</a></li><li><a href="https://www.forbes.com/sites/michaeldelcastillo/2018/08/09/ibm-maersk-blockchain-platform-adds-92-clients-as-part-of-global-launch-1/">https://www.forbes.com/sites/michaeldelcastillo/2018/08/09/ibm-maersk-blockchain-platform-adds-92-clients-as-part-of-global-launch-1/</a></li><li><a href="https://cointelegraph.com/news/deloitte-outlines-five-major-obstacles-to-blockchains-mainstream-adoption">https://cointelegraph.com/news/deloitte-outlines-five-major-obstacles-to-blockchains-mainstream-adoption</a></li><li><a href="https://www.prnewswire.com/news-releases/are-we-close-to-crossing-the-chasm-of-mass-adoption-of-blockchain-tech-find-the-answer-in-zurich-at-crypto-summit-300721520.html">https://www.prnewswire.com/news-releases/are-we-close-to-crossing-the-chasm-of-mass-adoption-of-blockchain-tech-find-the-answer-in-zurich-at-crypto-summit-300721520.html</a></li><li><a href="https://www.mro-network.com/emerging-technology/hype-factor-behind-emerging-technologies-and-blockchain">https://www.mro-network.com/emerging-technology/hype-factor-behind-emerging-technologies-and-blockchain</a></li><li><a href="https://www.barrons.com/articles/blockchain-separating-hope-from-hype-1537912060">https://www.barrons.com/articles/blockchain-separating-hope-from-hype-1537912060</a></li><li><a href="https://www.cnbc.com/2018/06/04/for-all-the-hype-blockchain-applications-are-still-years-even-decades-away.html">https://www.cnbc.com/2018/06/04/for-all-the-hype-blockchain-applications-are-still-years-even-decades-away.html</a></li><li><a href="https://www.cnbc.com/2018/06/06/blockchain-is-so-hyped-right-now-and-many-companies-will-get-burned.html">https://www.cnbc.com/2018/06/06/blockchain-is-so-hyped-right-now-and-many-companies-will-get-burned.html</a></li><li><a href="https://www.prnewswire.com/news-releases/business-blockchain-technology-adoption-happening-faster-than-projected-675982983.html">https://www.prnewswire.com/news-releases/business-blockchain-technology-adoption-happening-faster-than-projected-675982983.html</a></li></ul><p><a href="http://theblockchainhub.com/aboutus/">The Blockchain Hub</a> is an inclusive education and innovation hub, with a strong network of diverse alumni from many industry verticals. Would you like to add your voice to ours, and have your articles featured in The Blockchain Hub? Just send us a note at <a href="/service/mailto:content@theblockchainhub.com">content@theblockchainhub.com</a></p><p>Disclaimer: The views and opinions expressed in this article are those of the author. They do not purport to reflect the policies, views, opinions or positions of The Blockchain Hub, any other agency, entity, organization, employer or company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d09b3688245" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theblockchainhub/blockchain-adoption-1d09b3688245">On Blockchain adoption</a> was originally published in <a href="https://medium.com/theblockchainhub">TheBlockchainHub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blockchain and The Enterprise, Part 1]]></title>
            <link>https://medium.com/theblockchainhub/blockchain-and-the-enterprise-part-1-463f2c299e99?source=rss----602b22dcb36e---4</link>
            <guid isPermaLink="false">https://medium.com/p/463f2c299e99</guid>
            <category><![CDATA[use-cases]]></category>
            <category><![CDATA[tbh-stories]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Lassonde Professional Development Centre]]></dc:creator>
            <pubDate>Tue, 11 Dec 2018 19:52:10 GMT</pubDate>
            <atom:updated>2018-11-18T16:50:07.128Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>This blog post was written by Carlos Dominguez, <a href="http://theblockchainhub.com/mcbb">MCBB</a>. Carlos is a professional in Enterprise Architecture and Information Security. He is also alumni and volunteer with The Blockchain Hub. To learn more about our program offerings, please check <a href="https://theblockchainhub.com/academy">www.theblockchainhub.com/academy</a></p><p>To address Blockchain Enterprise adoption and use cases I will use a process similar to a <a href="https://en.wikipedia.org/wiki/Value_proposition">value proposition analysis</a>, simplified to three steps:</p><ul><li>Step 1: Describe the solution (the blockchain).</li><li>Step 2: Describe the problem (pains and gains).</li><li>Step 3: Describe how the solution (blockchain again!) addresses those pains and results on gains. This is known as “the fit”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCAbOOme8vF6u56BGxjWXw.png" /></figure><h3>But first, which blockchain is it?</h3><p>As we all know (I am including you, my readers) everytime blockchain is mentioned there is controversy. Which is fine, but it can make intelligible discourse difficult. For the sake of being able to continue with this blog entry, let’s state what “blockchain” will mean in the context of Enterprise adoption.</p><p>There are many ways to sort out blockchains into categories and every attempt at doing so still misses something. Eventually, when ISO <a href="https://www.iso.org/committee/6266604.html">finishes their work</a>, we will all agree on the types, but for now let’s keep it simple.</p><p>A practical way to differentiate which “type” of blockchain is being discussed is by looking at:</p><ul><li>Participants’ access to the network: Permissioned or Permissionless?</li><li>Participants’ access to transactions: Public/Private, Read or Write?</li><li>Type of consensus. This is where we get into those many Proof-of-whatever, including many variations of Byzantine failure tolerances.</li><li>What sort of asset it includes: some have cryptocurrencies, or tokens, or none of that.</li><li>What sort of governance: total chaos (beloved by libertarians), governance via computed rules (like a DAO), or governance by committee (people get together and vote).</li><li>Incentives: full blown tokenization (hello Tokenomics!), or token-less (like current Enterprise ones). For now (wait for part 3 of this blog).</li><li>Type of peer-to-peer networking: Gossip, Channels, Direct… many options here.</li><li>Network topology: from the mildly decentralized to the absolute decentralization.</li></ul><p>The type of blockchain suitable for the Enterprise is usually referred to as “Permissioned”, which refers to specific design choices for the parameters I mentioned above.</p><p>I have also seen references to “Private” as in a single-party implementation, which does not make any sense as by their nature blockchains are not meant to be used as a private database. There are also Hybrid blockchains, but I will skip these for now.</p><p>Hybrid blockchain, sometimes is called “Distributed Ledger Technology” or DLT, usually lacks a native cryptocurrency. If you know what <a href="https://www.hyperledger.org/">Hyperledger</a> , <a href="https://www.r3.com/corda-platform/">Corda</a> or <a href="https://www.jpmorgan.com/global/Quorum">Quorum</a> are, these are the ones!</p><h3>Brief detour into decentralization</h3><p>Now that all pertinent clarifications have been made, I have one final addition: when I referred to The Enterprise I hid something from you. This is what I hid: The Enterprise can actually refer to all manner of businesses.</p><p>I will sort those out along a decentralization axis, and into four quadrants as per a second axis of profitability. This does not follow any economic model, but it will help me explain some notions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9xKEjzvQzL5Tmygdkopolw.png" /><figcaption>I doodled this while discussing adoption. Feel free to disagree</figcaption></figure><p>From that diagram above, the “Enterprise” we are about to discuss is located in the left side of the diagram. They could be existing or new.</p><p>Why do I exclude the right side? Because I want to cover businesses that are moving from left-to-right along the axis of decentralization.</p><p>That movement is the result of adopting DLT (aka Blockchain) technology for their current or new business models. We can refer to the migration as a “transformation”. The world of crypto-assets and tokens for the Enterprise will come later in another blog post (part 3).</p><p>Let me explain what a “centralized product” is:, it relies on a value chain where the Enterprise is the only player, or the dominant one. From a Technology and Infrastructure standpoint, all of the value chain participants are owners and operators, and inter-business collaboration or cooperation is done along the demarcation lines of that ownership and control.</p><p>For the sake of argument, let’s also make these assumptions about the Enterprise:</p><ul><li>It already has some form of Information Technology to support its products or services.</li><li>It operates on an industry vertical where there are competitors (let’s exclude monopolies).</li><li>It depends on other entities such as business partners, suppliers, vendors and regulators.</li><li>It offers a centralized product (or service) as discussed above.</li></ul><p>Now that we have set the stage let’s move to the next topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*V181RcKIbt4wc-cXjkEedQ.jpeg" /><figcaption>If your business is mostly dealing with these we are going to have some challenges</figcaption></figure><h3>Step 1: Blockchain inherent attributes</h3><p>So what is it about Blockchain (or DLT) that generates so much hype? Besides its obvious use to get people investing in ICO schemes, most blockchains do the following things to some degree for a distributed network of transacting nodes (participants), where nobody is really in control of the whole thing:</p><ul><li>Record transactions in an immutable ledger .</li><li>The ledger is used to create trust amongst the parties.</li><li>The transaction entries are digitally signed providing <a href="https://en.wikipedia.org/wiki/Non-repudiation">non-repudiation</a>.</li><li>Each transaction block represents the state of the network.</li><li>Each transaction is final.</li><li>Transaction blocks are ordered and timestamped.</li><li>Each block is created as per consensus from the network.</li><li>It creates a level of automation for settling accounts across the network.</li></ul><p>What all of the above means is, a ledger (a book of records):</p><ul><li>Which is shared by a multiple parties and of which nobody is really in control. We can call that “decentralized” and it is assumed to be a good thing (notice I said “assumed”),</li><li>Represents the collective agreement of what-is-what for all those parties (the so called network state),</li><li>And, which is almost impossible to alter without anybody noticing.</li></ul><p>Ask yourself this question: what can you do with a thing like that? If nothing comes to mind I will add one more thing: the transactions (of the immutable type) can also include code, and that code is subjected to the same rules as everything else (consensus). That code is also another overly hyped thing: <a href="https://en.wikipedia.org/wiki/Smart_contract">Smart Contract</a>. If still nothing comes to mind, read on.</p><h3>Step 2: Stating the Problem</h3><p>Now that we have described the “solution” (Blockchain), and its attributes, I will proceed to describe some of the challenges Enterprises face, and which I think are worth addressing.</p><p>So what afflicts the modern Enterprise? To answer this I will refer to the assumptions I made somewhere earlier in the blog about business environment, which I will repeat here:</p><ul><li>It already has some form of IT, to support its products or services.</li><li>It operates on an industry vertical where there are competitors.</li><li>It depends on other entities such as business partners, suppliers, vendors and regulators.</li><li>It offers centralized product or services.</li></ul><p>An Enterprise operating in that setting will find itself dealing with the following:</p><ul><li>Having to coordinate transactions across many parties (all those suppliers, business partners, vendors, etc). Sometimes re-initiating the transaction as something was missed.</li><li>Using a multiplicity of integration technologies and data formats for transactions, as each party has their own technology and data preferences (their Mac to your PC).</li><li>Spending time onboarding new parties and off-boarding old ones, while keeping the legal and compliance teams busy with contracts, and IT busy with adding and removing integrations.</li><li>Having to reconcile those transactions multiple times, as each party has its own set of “books” (ledgers), where nobody can see the whole thing and errors happen.</li><li>Not knowing whether to trust the party and the data behind those integrations. The other party may be up to no good.</li><li>Not knowing about the third-party’s third-party, and what they have to do with the transactions.</li><li>Doing painful audits to ensure all transactions are compliant with a multitude of compliance rules, and sometimes finding something is amiss and needs fixing (and paying accounting firms for the privilege).</li><li>Generally spending a great deal of effort on inter-business coordination. Also, repeating the same procedures everybody else is doing, because there is no-reusing somebody’s else process that you don’t control or trust (this is an important point).</li></ul><p>I would summarize all of the above with this picture</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*KA5vkC5oBvciG8CCzGhYIQ.jpeg" /><figcaption>Inter-business integration and coordination of processes across many parties</figcaption></figure><p>A bit of history: that mess above used to be the state of affairs for intra-business integration, the one that takes place inside the corporate environment. Two technologies came along and helped deal with it:</p><ul><li>The <a href="https://en.wikipedia.org/wiki/Database">Database</a>, to hold all that corporate data in an organized form. Hard to believe it only came about in 1970. Before that Enterprises relied on the spaghetti data! (I am exaggerating for effect).</li><li>The <a href="https://en.wikipedia.org/wiki/Enterprise_service_bus">Enterprise Service Bus</a> (aka ESB ), to sort out all those pesky integrations plaguing the IT environment, and move all that data in an efficient, organized and re-usable manner.</li></ul><p>Those two technologies are still not enough to make sense of transactions at the business level. They just fix IT messes, but something else is needed to hold the ledger so the business knows the state of its own books: The Enterprise Resource Planning systems (aka ERP).</p><p>There is an obvious question: why can’t Databases, ESBs, and ERPs systems be used to coordinate external parties? Answer: if it ever was that easy! There are some things getting in the way with the industry wide implementations: Ownership, Control, and Trust. Remember, we are talking about centralized business where those three things are the name of the game!</p><p>I am not saying the solutions don’t exist. They do, but are limited by the reliance on the centralized systems. Just think about it: someone has to own and operate the thing, and whoever does, they have a great deal of power over everyone else. They are also the greatest risk and source of failures for everybody. Like the saying goes: the bigger they are, the harder they fall.</p><p>If that strikes you as a cynical view, please revisit that link I have somewhere up there (<a href="https://fraudsurveys.ey.com/media/1627/global_fraud_survey_2018.pdf">EY’s 15th Global Fraud Survey</a>). The paper points out something very interesting which will come up next: Digitization of Compliance.</p><h3>Part 3: How the solution fits the problem</h3><p>Now that I have you convinced (hopefully) of the difficulties the Enterprise faces when doing transactions in a network where there is no trust, let’s figure out how the solution (Blockchain) addresses them.</p><p>I will start with a better model of the spaghetti wiring I showed above. Something more business-like, such as this diagram that I totally made up to explain this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*beGtEvhn2PMhJPz4CLGk0g.png" /><figcaption>Business Network 1.0 with spaghetti like integration and transaction coordination</figcaption></figure><p>So what do we have here? Let’s list:</p><ul><li>There are some interdependent businesses.</li><li>Each business totally controls and commands their own environment.</li><li>Each business has its own processes which have nothing to do with others’ processes.</li><li>There are a number of integrations. A few spaghetti bowls of them. Probably all different flavours.</li><li>There is no overarching business process to support integration and transaction coordination.</li><li>Each business has its own version of “the truth” (the ledger), which nobody else knows about.</li><li>Despite being similar, there is a lot of duplication, as each business is responsible for their own stuff and has no control over the quality of what others do.</li><li>There is plenty of material for auditors and regulators to work on. Who knows what they will find when reconciling!</li><li>Some of those businesses may not be providing actual value, or could be adding inefficiencies. Those are the types of mediators that automation would do eventually remove, but for now you need them to cook all that spaghetti.</li><li>Adding or removing someone from the spaghetti party does not look pleasant.</li></ul><p>The obvious question is: what can Blockchain do about the spaghetti? It turns out it can do a whole lot. I will illustrate that with a another diagram, just as made-up as the previous one, but with permissioned blockchain sauce added.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WZW9aNOPPXVVjNXH8VLlbg.png" /><figcaption>Business Network 2.0 and Blockchain as the decentralized ERP in the sky</figcaption></figure><p>Notice, nothing changed about the intra-business coordination, we just changed how the businesses integrated with each other to support the overarching business process. That’s the transformation I mentioned above. Let’s describe that Business Network 2.0 (no spaghetti) by pointing what changed from v 1.0.</p><ul><li>There is a new source of truth, in the form of the distributed ledger.</li><li>Nobody owns the network (or better said: they all do, but nobody “holds” it).</li><li>There is a standard for integration, courtesy of a standardized blockchain node.</li><li>There is a standard for transaction data, to support the network transactions.</li><li>Adding and removing participants is easier (courtesy of standardization of access).</li><li>Transactions are final (no back and forth to get something done).</li><li>There is a new type of application that works at the blockchain level (hello, smart contracts!).</li><li>There is transparency and accountability (everything signed, validated, and consented).</li><li>No need for manual meddlesome reconciliation/facilitators (disintermediated!).</li><li>Very resilient over-arching business process, supported by a distributed network with no single point of failure.</li></ul><p>At this point I hope it is obvious what blockchain did. No? Ok, here it is: The blockchain (or DLT) is working as Service Bus, Database and/or ERP system but for the whole business network! The same type of solutions put in place to sort out the messy innards of Enterprise IT is now available at a meta-level. Enterprise Blockchain is a Meta-ERP/Meta-ESB system for business networks, but decentralized to solve trust issues created by centralization.</p><p>Here are some good follow up questions: why didn&#39;t any of the current software power houses create this type of technology? Those business network challenges have been around for some time, so why not build something to solve them?</p><p>These are my answers:</p><ul><li>Software houses sell to specific clients, usually enterprises. They don&#39;t sell to unspecified networks of enterprises.</li><li>Enterprises tend to prefer and buy software that is deployed and owned by centralized entities, which is in their nature to do.</li><li>The type of problem solved by Bitcoin, and the expanded blockchain technology is better suited for Open Source development without a defined business model (investments, sales, etc.), and rely instead on the effort of a dedicated community of technical experts.</li><li>Software houses have taken notice of Blockchain and have adjusted already. Some are even launching products that will enable integration between enterprise blockchains, ERP and other enterprise systems (see links below).</li></ul><p>You are probably wondering about the catch. Yes, there is a catch. Actually, there is a whole slew of them. I will cover some of these furter down.</p><p>Next question: when and where to use Blockchain? I think you are ready for the next part.</p><h3>Enterprise use cases conclusion</h3><p>Let’s get something clear: as far as I have understood the value of Blockchain technology, all the uses cases involve business networks not private deployments. A Database/ERP/ESB system can do a much better work for a single Enterprise.</p><p>There is an exception to this rule: if the Enterprise is so large that it behaves like a collection of independent business units, maybe and just maybe blockchain would work. We are talking about organizations with tens of thousands of people and hundreds of business units.</p><p>Generally the type of use cases worth considering involve a bit of <a href="https://en.wikipedia.org/wiki/Coopetition">“coopetition</a>”, to solve industry wide problems and revenue drains. The use cases best suited for the technology resemble supply chain in one way or another, and do not have to be about physical items but digital ones as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XqyFopJ5osVFdTssiYXLgg.png" /><figcaption>This is the transformation for an ecosystem (team effort is needed for Coopetition)</figcaption></figure><p>These are the types of challenges impacting whole industry verticals, resulting on inefficiencies and constraints for all parties. It is mostly created by lack of trust, standardization, and automation. The symptoms are:</p><ul><li>Long running transactions which are hard to settle and require manual intervention.</li><li>Identical processes repeated by many parties, and which are not a <a href="https://en.wikipedia.org/wiki/Competitive_advantage">competitive advantage</a> but just Enterprise level non-core functions.</li><li>A thriving body of mediators with low value adds.</li><li>Supply chain issues which makes it hard to locate something in space and time.</li><li>Troublesome dispute resolution with third parties lacking accountability or transparency.</li></ul><p>When Blockchain gets added to the network you get the following Gains as per new and improved business models, and as a result of participation in Business Network 2.0:</p><ul><li>Automated settlements via parametric transactions</li><li>Automated provenance and authenticity tracking</li><li>Very lean value chains, without troublesome mediators</li><li>Pinpoint accuracy for supply chain and logistics (e.g. surgical precision recalls).</li><li>Automated compliance for all: transparency and accountability as a business model.</li><li>Product stacking: automation and standardization with products as reusable building blocks.</li></ul><p>In summary: the use cases are those with a win-win outcome for whole industry groups, and for challenges afflicting all. And, I repeat, are not for use cases involving competitive advantages. Blockchain is a team sport! The best use case is the one that works better with larger teams.</p><p>At the extreme end of those gains is the “Decentralized Ecosystem” (remember that chart way up in the blog?). I will discuss this in part 3, as it requires some additional considerations.</p><p>Now we ready to discuss the catch (i.e. adoption challenges).</p><h3>Proceed with caution!</h3><p>First and foremost: Coopetition will require creating a business entity to manage the adoption and on-going operations. Enter The Consortium, and a myriad of challenges which comes with it. The Consortium also plays a role in defining the business cases that will pay for all those nice use cases, so let’s stay with the use cases for now.</p><p>Here is the SWOT analysis done by Gartner more than a year ago, and which is still relevant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*_3xhHSPmV5T-ehKjr5mSNA.png" /><figcaption>Practical Blockchain: A Gartner Trend Insight Report</figcaption></figure><p>We discussed a lot of the Strengths and Opportunities in the Fit analysis, so is time to open the book on Weaknesses and Threats. You would think that by now some of them would have been resolved. No, they have not and this is where the use cases can fall apart. Granted, some of these challenges don’t apply to Enterprise Blockchain but many do.</p><p>I am going to add some challenges of my own, categorized for convenience:</p><p><strong>Security challenges</strong>:</p><ul><li>Key management is a core functionality supporting the Permissioned access model. It will be as good or as bad as current practices.</li><li>Need to consider transaction privacy carefully, as per specific platform features.</li><li>Tight integration with competitors could lead do disclosures of sensitive business plans.</li><li>There could be impacts to Audit and Compliance practices. You may not be able to afford disrupting those.</li></ul><p><strong>Business challenges</strong></p><ul><li>There may not be a clear business case for the use cases.</li><li>Use cases may require to adopt a common data and transaction model. Easier said than done.</li><li>Collaboration with competitors (Coopetition) requires some alignment in product and service design, as well as market approach.</li><li>Creating or participating in a consortium requires an agreement to a constitution, and abiding by it.</li><li>May need to re-imagine business models. Also challenging.</li></ul><p><strong>Technology Challenges</strong></p><ul><li>Underestimating the complexity of integrating a node with backend systems. Redundant nodes will add complexity.</li><li>Internal reconciliation will not go away. You still have your own ledger.</li><li>Investing in early technology that may be exposed to rapid changes and fast obsolescence.</li><li>Finding qualified personnel will be difficult (and expensive).</li></ul><p><strong>Data Governance Challenges</strong></p><ul><li>You need to be “Digital”. Starting with paper records to in one jump will mess up the use case, inflate budgets, and result in massive scope creep. Digitize first, and do blockchain later.</li><li>Need clear line of sight for ownership of data in the shared ledger (Consortium again).</li><li>Immutability: recorded erroneous information is not easily corrected.</li><li>Blockchain Technology does not consider data life cycle. Transactions are hard to delete or archive, without special arrangements.</li></ul><h3>Conclusion</h3><p>So what are we to do when evaluating a business case? I will leave you with some general advice:</p><ul><li>Understand your place and value in others’ value chain. It is possible you could be the one to be disintermediated.</li><li>Validate use cases carefully, and consider the impacts to your business network. You may end up upsetting some parties.</li><li>For now, think strategically and act tactically, until more use cases are validated and implemented.</li><li>Undertake proofs-of-concepts to understand technology and decentralization.</li><li>Understand the difference between a proof-of-concept (simulated network) and the actual implementation (real coopetition network).</li><li>Limit the scope of the use cases to quick wins (the easier ones to do, go first).</li><li>Learn from the early attempts to reimagine business models, processes, markets, and products for the era of programmable economy (smart contracts).</li><li>Assume technology obsolescence will happen. Fast.</li><li>Validate legal and regulatory impact for the chosen use cases.</li><li>Start to digitize paper records. This will come in handy.</li><li>Be part of the ecosystem by participating in the industry (blockchain industry), to track developments and learn from others’ attempts. Build some competence.</li><li>Start taking inventory of your business network, the participants, and their roles. Do value chain analysis with an eye on disintermediation. That may come handy too.</li><li>Initiate some of that “coopetition”, as it is possible that businesses in your vertical are already looking at industry wide challenges.</li></ul><p>Bad reasons for using blockchain:</p><ul><li>Fear of missing out.</li><li>Following the herd mentality.</li><li>Trying to increase brand value by “doing blockchain”.</li><li>Because some management consultant told you so.</li><li>Thinking that “decentralized” is inherently better than “centralized”, without considering what this actually means for your business model.</li></ul><p>Here are some links to help the thinking on Enterprise Use Cases</p><ul><li><a href="https://www.mckinsey.com/business-functions/digital-mckinsey/our-insights/blockchain-beyond-the-hype-what-is-the-strategic-business-value">McKinsey: Blockchain beyond the hype: What is the business strategic business value?</a></li><li><a href="https://medium.com/singulardtv/why-coopetition-must-become-the-principle-of-blockchain-culture-f50e6a3da446">Why ‘Coopetition’ Must Become the Principle of Blockchain Culture</a></li><li><a href="https://www.forbes.com/sites/omribarzilay/2018/02/08/why-blockchains-future-demands-more-coopetition">Why Blockchain’s Future Demands More Coopetition</a></li><li><a href="https://www.econotimes.com/Coopetition-The-Biggest-Obstacle-Hindering-Blockchain-Growth-Consulting-Firm-Says-1386181">‘Coopetition’ the Biggest Obstacle to Blockchain Growth, Consulting Firm Says</a></li><li><a href="https://www.gartner.com/smarterwithgartner/the-cios-guide-to-blockchain/">Gartner: The CIO’s Guide to Blockchain</a></li><li><a href="https://www.gartner.com/newsroom/id/3873790">Gartner Survey Reveals the Scarcity of Current Blockchain Deployments</a></li><li><a href="https://techcrunch.com/2018/07/22/the-blockchain-begins-finding-its-way-in-the-enterprise/">The blockchain begins finding its way in the enterprise</a></li><li><a href="https://www.forbes.com/sites/forbestechcouncil/2018/05/14/blockchain-in-enterprises/">Forbes: Blockchain In Enterprises</a></li><li><a href="https://www.forbes.com/sites/forbestechcouncil/2018/06/21/enterprise-blockchain-technologies-part-two">Forbes: Blockchain in Enterprises Part 2</a></li><li>S<a href="https://www.sap.com/canada/products/leonardo/blockchain.html">AP: Blockchain Applications and Services</a></li><li><a href="https://www.ledgerinsights.com/sap-blockchain-strategy/">How SAP’s blockchain strategy is fundamentally different</a></li><li><a href="https://azure.microsoft.com/en-ca/solutions/blockchain/">Microsoft Azure: Blockchain Technology and Applications</a></li><li><a href="https://www.oracle.com/cloud/blockchain/">Oracle: Transforming the Enterprise with Oracle Blockchain Platform</a></li><li><a href="https://aws.amazon.com/blockchain/">Amazon: Blockchain on AWS</a></li><li><a href="https://it.toolbox.com/blogs/erpdesk/how-erp-is-incorporating-blockchain-technology-082917">How ERP is incorporating Blockchain</a></li><li><a href="https://it.toolbox.com/blogs/erpdesk/how-erp-is-incorporating-blockchain-technology-082917">Infosys: Integrating Blockchain with ERP for a transparent supply chain</a> (PDF)</li></ul><p><a href="http://theblockchainhub.com/aboutus/">The Blockchain Hub</a> is an inclusive education and innovation hub, with a strong network of diverse alumni from many industry verticals. Would you like to add your voice to ours, and have your articles featured in The Blockchain Hub? Just send us a note at <a href="/service/mailto:content@theblockchainhub.com">content@theblockchainhub.com</a></p><p>Disclaimer: The views and opinions expressed in this article are those of the author. They do not purport to reflect the policies, views, opinions or positions of The Blockchain Hub, any other agency, entity, organization, employer or company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=463f2c299e99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theblockchainhub/blockchain-and-the-enterprise-part-1-463f2c299e99">Blockchain and The Enterprise, Part 1</a> was originally published in <a href="https://medium.com/theblockchainhub">TheBlockchainHub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>