|
|
|
Security |
|
|
|
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.
|
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.
|
"Block Security Protocol" (BSP)
Employs a BSP to implement the signature function on each data bock during PoA cosnensus. Only the blocks with authorized signatures can be mined and accepted.
|
|
|
Permissioned
|
Permissionless
|
Permissioned Aspects
Only permissioned parties can view the raw transactional data stored in the public blockchain. To all others, it will be hashed and secured.
Anyone can become a node, but there is a hard cap of 101 Authority Nodes. It requires a great deal of transparency and public capital to become a node.
|
|
|
Privacy concerns are addressed through the pluggable uniqueness services, and restriction of viewing transactions.
|
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.
|
Yes
Transaction Data Privacy Protocol (TxDP): Ensures privacy of transaction data.
|
|
|
|
Algorithms |
|
|
|
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.
|
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.
|
Proof of Authority
Consists of 101 Authority Nodes that are controlled by separate, self-interested entities. Due to the variety of companies, this will secure the network and ensure a trustless environment. PoA allows for a higher number of TPS than PoW and PoS, meaning VeChain can support up to 10,000 TPS.
|
|
|
|
Efficiency |
|
|
|
Fast
Built for financial applications
|
Moderate
|
No data
|
|
Block Confirmation Time
Details
|
TBD
|
Fast
|
Fast
Set during launch at 10 seconds, and will be iterated after use.
|
|
|
|
Development |
|
|
Proprietary Codebase
Details
|
Open Source
|
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
https://github.com/vechain
|
|
|
|
General |
|
|
Blockchain / DLT type
Details
|
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
|
Public
Open source public blockchain fuelled by cryptocurrency.
|
Public
|
|
|
Less focus on modularity
Focus is on financial applications, but may support more use cases in the future.
|
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
VeChain exists as a platform to be developed on. Meaning the core features and services can be applied in a number of industries. Some utilizing IoT, some just using the consensus mechanism.
|
|
|
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/
|
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.
|
50 - 10,000 TPS
50 TPS is currently the maximum. Once VeChain moves to thier mainnet, they plan to scale their TPS to 10,000. This will enable Enterprise level support for financial and sensor data.
|
|
|
Varies
|
Varies
https://tronscan.org/#/blockchain/stats
|
Depends on implementation
|