Key Points

Enterprise blockchains include: Fabric, Ethereum, Corda, Quorum, Sawtooth

References

Session Overview

• Content - Different Blockchain Technologies like Hyperledger,Ethereum,R3 Corda,Multichain etc

• Summary - Key message to be delivered at the end of the session

• Enterprise Blockchain solutions are a strategic investment for an organization. Different Enterprise Blockchain platforms implement unique features and provide some support for common concepts and features as well.
  
  

• The session defines a set of criteria for comparison ( development, runtime environments and application use case fit ) and then compares some of the more popular Enterprise Blockchain frameworks against the criteria ( Hyperledger Fabric, Enterprise Ethereum, Corda, Quorum, Hyperledger Sawtooth ).
  
  

• For each platform, a common application use case is referenced and evaluated for fit.
  
  

• Finally, a set of questions to ask on selection of an Enterprise Blockchain for candidate use cases is reviewed.

• Summary - Key message to be delivered at the end of the session

• Key Takeaway 1

• Identify criteria for blockchain criteria that may be relevant for your use case
  
  

• Key Takeaway 2

• Learn some of the key features and differences between the major Enterprise Blockchain platforms
  
  

• Key Takeaway 3

• Get a set of questions that can help select an Enterprise Blockchain platform for your use case

Enterprise Blockchains key features

Enterprise Blockchains reviewed

Comparison criteria

Ethereum

Corda

Hyperledger Sawtooth

Hyperledger Fabric

Quorum

Review options for your use case

Some have made significant penetration of specific industries

Your use case drives selection criteria

Internal solution vs Consortium solution

Existing organization skill sets

Production environment – single target or multi-platform capable

Integration requirements

Next steps -

industry blockchain strategies and solutions

relevant standards and regulations

opportunity assessment

Key Concepts

Compare Hyperledger Fabric, Ethereum, Corda, Quorum -2020 ratings

https://blockchainsimplified.com/blog/hyperledger-vs-quorum-vs-corda-which-is-correct-for-your-business/

Fabric v Corda - 2018

fabric-v-corda-2018-features-medium.com-Hyperledger Fabric vs R3 Corda.pdf

corda v fabric feature compare

tokens c??? fabtoken delayed

privacy b

scale f???

finality b

batch proc ????

admin ????

languages f

interoperability b

open platform b

identity tools b???

pluggable f???

wide use cases f???

did support ????

multi cloud ????

consensus ????

default net b hyperchain, aws, ibm, azure

Enterprise Blockchain Protocols: A Technical Analysis of Ethereum vs Fabric vs Corda

https://kaleido.io/a-technical-analysis-of-ethereum-vs-fabric-vs-corda/

kaleido.io-Enterprise Blockchain Protocols A Technical Analysis of Ethereum vs Fabric vs Corda.pdf

Ethereum Enterprise Blockchain implementations

Consensus Models Compared

All blockchain systems need a consensus mechanism to ensure all nodes have the same view of the transactions input and order. Almost all existing protocols utilize consensus algorithms designed around the “order-and-execute” architecture. First all nodes agree on the transactions order inside a block, then the transactions are independently executed by each node to calculate the resulting state.

Fabric consensus model is different - order > execute > commit

Fabric achieves transaction finality differently.

It has a faster consensus model:   execute > order > commit

option to listen for transaction commit completion event ensures finality

At a high level, a configurable number of organizations must come to consensus on the execution results, where the “endorsement policy” is defined at the chaincode level, private data collection level (starting in v2.0), or key level.

Corda consensus design is very similar to Fabric. First the nodes involved in the transaction coordinate among them to process the transaction by executing the target contract and signing the execution result. Once the required signatures are collected, the initiator node is responsible for sending the transaction to the notary service for consensus signature. The notary service maintains a full history of all the transactions that have been submitted and is able to determine if a double spending situation is happening. Once the notary service approves the transaction and signs of on the proposed result, the transaction is finalized and committed by all the parties. This makes it effectively the same execute-order-validate design that Fabric follows.

Multiversion Concurrency Control for execute > order > commit flows

“execute first and order next” design implies that some kind of concurrency version control is necessary, otherwise when multiple transactions are trying to modify the same state value in parallel, the later one will overwrite the earlier one and wipe out the state transfer from the earlier transaction, instead of building on the result of the earlier transaction. Fabric employs a multiversion concurrency control (MVCC) technique borrowed from database design. Under the cover, the chaincode engine keeps track of what state values are being viewed (in readset) and updated (in writeset) when the smart contract is executed. During the validation phase, where each transaction contained inside a block is validated and state transfer is applied, if a transaction’s state value versions in its readset do not match the current versions, typically because they have been updated by an earlier transaction in the block, then the transaction is marked as invalid.

implication is that if a series of transactions need to modify the same state value, they must be regulated such that no more than one transaction lands inside a single block. Otherwise the application will observe a lot of invalid transactions due to concurrent modifications.

Techniques exist to program around this limitation, such as utilizing the composite key capability to assemble unique keys for each transaction while having the ability to group together keys targeting the same underlying state variable. The high-throughput sample application demonstrates how this can be done. Note, though, that not all scenarios can take advantage of this technique.

Compare Fabric vs Corda XinFin for token networks

https://vinn9686.medium.com/hyperledger-vs-xinfin-which-blockchain-platform-will-benefit-your-business-f1e43db4a455

Hyperledger Fabric vs Corda XinFin compared 2019

Hyperledger vs XinFin which Blockchain Platform will Benefit your Business?

XinFin - public and private network access

• Instant payment at the lowest cost by enabling stable coin and peer to peer transfer between trusted parties.
• Hybrid blockchain with both private and public capability, both of which can be leveraged as per requirement.
• XDC token have high liquidity and are usable across the ecosystem
• Low transaction time and the newly launched mainnet technology has opened new avenues

XDC protocol works on the framework of hybrid blockchain technology and carries the features of private and public blockchain which doesn’t just support cryptocurrency but is currently being used across the XinFin ecosystem

Spread on a distributed network of individual private sub-networks, the XDC provides capabilities of a distributed public ledger along with transparency and the individual private sub-networks can be used for specific enterprise-level blockchain which has all amenities and security of private blockchain with master nodes holding membership stakes on the public network.

Every node carries both public and private state at the same time as each network that they are a part of, this mechanism furnishes the availability and synchronization of the data.

The XinFin network is a fork of Ethereum, therefore is fully compatible with Solidity and have also incorporated smart contracts in the protocol system.

The validity of the smart contract is approved by only master nodes.

DPOS consensus

consensus mechanism of Proof of Stake with the added PBFT layer i.e. the transactions are approved by a consortium of members who hold a stake in the network based on their wealth.

Fabric Token System Support

project Burrow is working on an improvised version of smart contracts and the Hyperledger Quilt is working on the payment end of the business transactions.

Fabric features:

• Decentralized trust in a network of known participants using permissioned channels
• Selective exposing of data as per the type of data and parties involved
• Smart contracts programmable in all languages and no custom languages and architectures required
• FabToken SDK for custom tokens with options for ZKP ( mint, transfer, burn )
• Consensus is RAFT or PBFT
• Explicit and Implicit private transactions
• Can run Solidity contracts on Fabric using Burrow EVM
• Can run an Ethereum mainnet node and a Fabric node on the same host if needed
• Can work with many Token, Crypto APIs using SDKs

Private transactions possible on Fabric

All ledgers are updated for each transaction on a public blockchain but for hyperledger, the peers directly affiliated with the deal are connected, and only their ledgers get updated about the deal. Other third parties can only access a limited amount of information as per the permissions granted on the network

use cases for token networks include:

payments, remittances, physical and digital asset management, STO - token offerings, NFTs, use as certificates, incentives, rewards

Potential Value Opportunities

Potential Challenges

Candidate Solutions

Quorum 

Quorum adds permissionless POS consensus

Quorum Control and presented by Quorum Control's Founder and CEO, Topper Bowers. 

The title of their presentation is "Topper Talks Tupelo: Introducing the Future of DLT". In the presentation, Topper will give an overview of Tupelo. Tupelo is a permissionless proof of stake DLT platform purpose-built to model individual asset ownership and provenance as the base layer (rather than token exchange). Tupelo introduces a completely unique infrastructure to better support scalable adoption outside of currency-oriented blockchain circles and deliver concrete benefits to users, from enhanced data security to more accurate and transparent record-keeping.

Step-by-step guide for Example

sample code block

Recommended Next Steps

Related articles