|
|
|
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
|
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.
|
Transactions are confirmed and validated through validator nodes.
The more trusted validators in the network, the harder it will be to control and change the ledger as an outside attack.
|
|
|
Permissioned
|
Permissionless
|
Permissioned
Anyone can become a validator, but will only be relevant if trusted.This provides public support for infrastructure, but keeps the transaction nature private when needed.
|
|
|
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.
|
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.
|
Transaction information on the ledger is public, but payment information is not.
This means that in the event of a security breach, no personal financial information can be compromised through this network.
|
|
|
|
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
|
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.
|
Ripple Protocol Consensus Algorithm
70+ validators
Applied every few seconds by all nodes. Once consensus is reached, the current ledger is closed. Most recently closed ledger is known as the last closed ledger and is the basis of the distributed ledger.
For more information: https://vimeo.com/64405422
|
|
|
|
Efficiency |
|
|
|
Varies
Depends on implementation
|
Moderate
|
Fast
3-4 seconds : set to improve with future updates. See future planned work.
|
|
Block Confirmation Time
Details
|
Varies
Depends on implementation
|
Fast
|
TBD
|
|
|
|
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 but goverened by the TRON organization
Built on Ethereum, but planning to move to own main net in June 2018
|
Open source with proprietary applications
The Ripple protocol is open source: https://github.com/ripple . Proprietary work is xCurrent, xRapid, xVia
|
|
|
|
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.
|
Public
Open source public blockchain fuelled by cryptocurrency.
|
Permissioned Network, Public Architecture
Ripple uses a decentralized network, but has trusted validator nodes who confirm transactions through the 'last closed ledger'.
|
|
|
Plug + Play Architecture
Easy to operate software platform to build out use case, test, and implement
https://www.ibm.com/blockchain/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
|
Yes
3 different plug and play offers on top of the protocol layer for specific needs: xCurrent, xRapid, xVia
|
|
|
Supports 1000 TPS. Designed for high throughput business applications. Scales relative to Hyperledger Fabric new developments.
|
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.
|
1500 TPS with potential of tens of thousands through Ripple Payment Channels
While it does not compare to the tps of a Visa transaction (~150,000), Ripple offers a stable solution for the size it it currently at.
|
|
|
500 transactions per block
Same as Hyperledger Fabric
|
Varies
https://tronscan.org/#/blockchain/stats
|
Large
The ledger is constantly refreshed as soon as there is a new input in the network. The last closed ledger model is different from the blockchain, in that there are no history of blocks for the distributed ledger.
|