|
|
|
Security |
|
|
|
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.
|
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/
|
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
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.
|
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.
|
Permissionless
|
|
|
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.
|
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
|
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 |
|
|
|
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
|
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).
|
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 |
|
|
|
Fast
3-4 seconds : set to improve with future updates. See future planned work.
|
Fast
Depends on implementation. Processes transactions in parallel to accelerate block creation and validation
|
Moderate
|
|
Block Confirmation Time
Details
|
TBD
|
Varies
Depends on implementation. Processes transactions in parallel to accelerate block creation and validation
|
Fast
|
|
|
|
Development |
|
|
Proprietary Codebase
Details
|
Open source with proprietary applications
The Ripple protocol is open source: https://github.com/ripple . Proprietary work is xCurrent, xRapid, xVia
|
Open Source
|
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
|
Permissioned Network, Public Architecture
Ripple uses a decentralized network, but has trusted validator nodes who confirm transactions through the 'last closed ledger'.
|
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.
|
|
|
Yes
3 different plug and play offers on top of the protocol layer for specific needs: xCurrent, xRapid, xVia
|
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.
|
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
|
|
|
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.
|
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.
|
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.
|
|
|
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.
|
Varies
Depends on implementation
|
Varies
https://tronscan.org/#/blockchain/stats
|