|
|
|
Security |
|
|
|
|
Membership Service Provider - pluggable interface that supports customizable credential architectures and certificate authorities
Concrete identity format
User credential validation
User credential revocation
Signature generation and verification
For more information:
http://hyperledgerdocs.readthedocs.io/en/latest/security_model.html
|
Similar security models to Hyperledger Fabric, but also incorporates the IBM Cloud Services as an added security layer when using the platform.
For more information:
http://hyperledgerdocs.readthedocs.io/en/latest/security_model.html
|
Data is only shared between parties involved in the transaction, verifiers, and permissioned observers. This allows an extra layer of security from traditional DLT where the data is spread throughout the network.
|
|
|
|
Consortium
Permissioned, private network.
To enable permissioned networks, Hyperledger Fabric provides a membership identity service that manages user IDs and authenticates all participants on the network. Access control lists can be used to provide additional layers of permission through authorization of specific network operations.
|
Permissioned
|
Permissioned
|
|
|
|
Private Channels
A Private Channel is a subnet communication between two or more parties in the network that performs a private and confidential transaction.
|
Private channels
Fabric has a unique concept of channels that supports transaction privacy. Private channels are restricted messaging paths that can be used to provide transaction privacy and confidentiality for specific subsets of network members.
|
Privacy concerns are addressed through the pluggable uniqueness services, and restriction of viewing transactions.
|
|
|
|
Algorithms |
|
|
|
|
Multiple options:
Pluggable Framework
No-op (no consensus)
PBFT
PBFT - Practical Byzantine Fault Tolerance
|
Plugable consensus (PBFT)
Fabric’s notion of consensus is broad and encompasses the whole transaction flow, starting from proposing a transaction to the network to committing it to the ledger. It uses the plugable Byzantine fault tolerance (PBFT) algorythm
|
Notaries - Pluggable Framework, Validity consensus and Uniqueness consensus
transaction validity and transaction uniqueness.
https://docs.corda.net/key-concepts-consensus.html
Corda uses special Notary Nodes to reach consensus. Notaries are nodes that specifically address double spend attempts.
|
|
|
|
Efficiency |
|
|
|
|
Varies
Depends on implementation
|
Varies
Depends on implementation
|
Fast
Built for financial applications
|
|
|
Block Confirmation Time
Details
|
Varies
Depends on implementation
|
Varies
Depends on implementation
|
TBD
|
|
|
|
Development |
|
|
|
Proprietary Codebase
Details
|
Open Source
https://github.com/hyperledger/fabric
|
Hyperledger Fabric is open source. IBM Blockchain is a proprietary layer that sits on top of Hyperledger as a simple to use platform accessing the blockchain
|
Open Source
|
|
|
|
General |
|
|
|
Blockchain / DLT type
Details
|
Federated / Consortium, Permissioned Network
Federated Blockchains operate under the leadership of a group. As opposed to public Blockchains, they don’t allow any person with access to the Internet to participate in the process of verifying transactions. Federated Blockchains are faster (higher scalability) and provide more transaction privacy - important aspects for Enterprise focused deployments
|
Federated / Consortium, Permissioned Network
Federated Blockchains operate under the leadership of a group. As opposed to public Blockchains, they don’t allow any person with access to the Internet to participate in the process of verifying transactions. Federated Blockchains are faster (higher scalability) and provide more transaction privacy - important aspects for Enterprise focused deployments.
Based on the Hyperledger Fabric framework.
|
Not a blockchain. Uses DLT to create transaction efficiencies between permissioned parties rather than the same ledger for the entire network, which R3 Corda believes is inefficient.
https://vimeo.com/205410473
|
|
|
|
Modular Architecture is a core focus of Platform
|
Plug + Play Architecture
Easy to operate software platform to build out use case, test, and implement
https://www.ibm.com/blockchain/platform/
|
Less focus on modularity
Focus is on financial applications, but may support more use cases in the future.
|
|
|
|
1000 TPS capacity for now. Developed with scaling in mind. Provides flexibility in size and throughput depending on the implementation.
A Performance and Scalability Workgroup exists within the community to discuss, research, and identify key use cases and metrics for all blockchains.
Hyperledger Fabric is built on a modular architecture that separates transaction processing into three phases: distributed logic processing and agreement ('chaincode'), transaction ordering, and transaction validation and commitment. This separation confers several advantages: Fewer levels of trust and verification are required across node types, and network scalability and performance are optimized.
|
Supports 1000 TPS. Designed for high throughput business applications. Scales relative to Hyperledger Fabric new developments.
|
Corda focuses on scaling through reducing inefficiencies in consensus mechanisms. By limiting involvement to just the transacting parties, beneficiaries, and verifiers it aims to position itself as more scalable than PoW
performance considerations https://www.corda.net/2017/12/dlt-performance-considerations/
|
|
|
|
500 transactions per block
|
500 transactions per block
Same as Hyperledger Fabric
|
Varies
|
