|
|
|
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
|
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
|
Public Blockchain with security features built in.
Lamport digital signature algorithm. Claims to be resistant to quantum computer attacks.
Customized P2P network with data storage encryption, location transparency, source nontraceability
Merkle Patricia Trie data structure
Although the hash algorithm built into Bitcoin and Ethereum is secure with todays technology from brute force attacks, quantum computing may support enough computational power to compromise these algorithm.
|
|
|
Permissioned
|
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.
|
Permissionless
|
|
|
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.
|
Private Channels
A Private Channel is a subnet communication between two or more parties in the network that performs a private and confidential transaction.
|
Based on zero knowledge proof. Hides the send, receipt address and transfer amount.
Similar in function to the zk-SNARK feature Ethereum added during their Metropolis release.
|
|
|
|
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
|
Multiple options:
Pluggable Framework
No-op (no consensus)
PBFT
PBFT - Practical Byzantine Fault Tolerance
|
Fast Paxos PoS variant.
The consensus of TRON adopts a three-step strategy.
1. Kafka-based technology system: implement a centralized consensus algorithm.
2. Raft-based distributed consensus mechanism: realize the centralized and distributed leapfrogging. Improves network function/distribution and lays the foundation for distribution with no logical center.
3. Consensus mechanism of Proof of Stake and realize the Byzantine Fault Tolerant Consensus.
|
|
|
|
Efficiency |
|
|
|
Varies
Depends on implementation
|
Varies
Depends on implementation
|
Moderate
|
|
Block Confirmation Time
Details
|
Varies
Depends on implementation
|
Varies
Depends on implementation
|
Fast
|
|
|
|
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
https://github.com/hyperledger/fabric
|
Open source but goverened by the TRON organization
Built on Ethereum, but planning to move to own main net in June 2018
|
|
|
|
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.
|
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
|
Public
Open source public blockchain fuelled by cryptocurrency.
|
|
|
Plug + Play Architecture
Easy to operate software platform to build out use case, test, and implement
https://www.ibm.com/blockchain/platform/
|
Modular Architecture is a core focus of Platform
|
Similar to Ethereum:
Generic, with DApp and Smart Contract support for wider applications
It is not modularity that stands out but the provision of a generic platform suitable for various types of transactions and applications
|
|
|
Supports 1000 TPS. Designed for high throughput business applications. Scales relative to Hyperledger Fabric new developments.
|
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.
|
Currently supports 15 TPS as it is on the Ethereum platform. Will be able to support up to 1000 TPS once main net launches
Scalability is a core feature for TRON. They want to be able to support large commercial projects, while minimizing transactions fees and time.
|
|
|
500 transactions per block
Same as Hyperledger Fabric
|
500 transactions per block
|
Varies
https://tronscan.org/#/blockchain/stats
|