|
|
|
Security |
|
|
|
|
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.
|
SGX / PoET
All transactions are signed by known identities.
PoET implementation will depend on that of SGX. SGX is a set of instructions which allows application to run in sectioned-off areas of memory called enclaves. This aims to protect sensitive data and code from disclosure or tampering, both when stored and at runtime. Unfortunately, since Intel first introduced SGX in 2013, several weaknesses have been found in its design.
https://www.theregister.co.uk/2016/02/01/sgx_secure_until_you_look_at_the_detail/
|
|
|
|
Permissioned
|
Permissioned
|
Permissioned, Permissionless depending on application
Hyperledger Sawtooth supports both permissioned and permissionless blockchain networks. This provides flexibility but lacks the prescriptive level of security hyperledger fabric has.
|
|
|
|
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.
|
Configrable permissions for any node cluster within the network
Sawtooth is built to solve the challenges of permissioned (private) networks. Clusters of Sawtooth nodes can be easily deployed with separate permissioning. There is no centralized service that could potentially leak transaction patterns or other confidential information. There is no concept of private channels as seen with Hyperledger fabric
contributors are investigating both trusted execution and zero-knowledge cryptographic approaches
|
|
|
|
Algorithms |
|
|
|
|
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.
|
PoET
Dynamic, Pluggable Consensus Algorithms
Sawtooth supports pluggable consensus algorithms but offers their own method —Proof of Elapsed Time (PoET). The PoET consensus has each validating participant wait a random amount of time. The first person to finish waiting becomes the leader of the new block. This provides a secure authority mechanism without the computational race and energy draw of Proof of Work (PoW).
|
|
|
|
Efficiency |
|
|
|
|
Varies
Depends on implementation
|
Fast
Built for financial applications
|
Fast
Depends on implementation. Processes transactions in parallel to accelerate block creation and validation
|
|
|
Block Confirmation Time
Details
|
Varies
Depends on implementation
|
TBD
|
Varies
Depends on implementation. Processes transactions in parallel to accelerate block creation and validation
|
|
|
|
Development |
|
|
|
Proprietary Codebase
Details
|
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
|
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.
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
|
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
|
|
|
|
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.
|
Modular Architecture. Incorporates IoT Sensors that can broaden the use case.
Location, Temperature, Humidity, Shock, Tilt, Motion, Shock - all examples of data that can be captured.
|
|
|
|
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/
|
1000 TPS. Built to be scalable in the way that consensus algorithms can be changed, applications are separate from the core system, and transactions can occur in parallel.
The different consensus mechanism features were designed to cater to networks of different sizes and with different requirements. Sawtooth targets large distributed validator populations that do not require much computational power.
|
|
|
|
500 transactions per block
Same as Hyperledger Fabric
|
Varies
|
Varies
Depends on implementation
|
