|
|
|
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.
|
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.
|
"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
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
|
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.
|
|
|
|
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.
|
Privacy concerns are addressed through the pluggable uniqueness services, and restriction of viewing transactions.
|
Yes
Transaction Data Privacy Protocol (TxDP): Ensures privacy of transaction data.
|
|
|
|
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
|
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.
|
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
3-4 seconds : set to improve with future updates. See future planned work.
|
Fast
Built for financial applications
|
No data
|
|
|
Block Confirmation Time
Details
|
TBD
|
TBD
|
Fast
Set during launch at 10 seconds, and will be iterated after use.
|
|
|
|
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 with proprietary applications
https://github.com/vechain
|
|
|
|
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'.
|
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
|
|
|
|
Yes
3 different plug and play offers on top of the protocol layer for specific needs: xCurrent, xRapid, xVia
|
Less focus on modularity
Focus is on financial applications, but may support more use cases in the future.
|
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.
|
|
|
|
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.
|
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/
|
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.
|
|
|
|
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
|
