|
|
|
Security |
|
|
|
|
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.
|
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.
|
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.
|
|
|
|
Permissionless
|
Permissioned
|
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.
|
|
|
|
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.
|
Privacy concerns are addressed through the pluggable uniqueness services, and restriction of viewing transactions.
|
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 |
|
|
|
|
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.
|
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.
|
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 |
|
|
|
|
Moderate
|
Fast
Built for financial applications
|
Fast
3-4 seconds : set to improve with future updates. See future planned work.
|
|
|
Block Confirmation Time
Details
|
Fast
|
TBD
|
TBD
|
|
|
|
Development |
|
|
|
Proprietary Codebase
Details
|
Open source but goverened by the TRON organization
Built on Ethereum, but planning to move to own main net in June 2018
|
Open Source
|
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
|
Public
Open source public blockchain fuelled by cryptocurrency.
|
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
|
Permissioned Network, Public Architecture
Ripple uses a decentralized network, but has trusted validator nodes who confirm transactions through the 'last closed ledger'.
|
|
|
|
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
|
Less focus on modularity
Focus is on financial applications, but may support more use cases in the future.
|
Yes
3 different plug and play offers on top of the protocol layer for specific needs: xCurrent, xRapid, xVia
|
|
|
|
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.
|
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/
|
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.
|
|
|
|
Varies
https://tronscan.org/#/blockchain/stats
|
Varies
|
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.
|
