|
|
|
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.
|
"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.
|
Membership Service Provider - pluggable interface that supports customizable credential architectures and certificate authorities
Concrete identity format
User credential validation
User credential revocation
Signature generation and verification
For more information:
http://hyperledgerdocs.readthedocs.io/en/latest/security_model.html
|
|
|
|
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.
|
Consortium
Permissioned, private network.
To enable permissioned networks, Hyperledger Fabric provides a membership identity service that manages user IDs and authenticates all participants on the network. Access control lists can be used to provide additional layers of permission through authorization of specific network operations.
|
|
|
|
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.
|
Private Channels
A Private Channel is a subnet communication between two or more parties in the network that performs a private and confidential transaction.
|
|
|
|
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.
|
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.
|
Multiple options:
Pluggable Framework
No-op (no consensus)
PBFT
PBFT - Practical Byzantine Fault Tolerance
|
|
|
|
Efficiency |
|
|
|
|
Fast
Built for financial applications
|
No data
|
Varies
Depends on implementation
|
|
|
Block Confirmation Time
Details
|
TBD
|
Fast
Set during launch at 10 seconds, and will be iterated after use.
|
Varies
Depends on implementation
|
|
|
|
Development |
|
|
|
Proprietary Codebase
Details
|
Open Source
|
Open source with proprietary applications
https://github.com/vechain
|
Open Source
https://github.com/hyperledger/fabric
|
|
|
|
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
|
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
|
|
|
|
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.
|
Modular Architecture is a core focus of Platform
|
|
|
|
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.
|
1000 TPS capacity for now. Developed with scaling in mind. Provides flexibility in size and throughput depending on the implementation.
A Performance and Scalability Workgroup exists within the community to discuss, research, and identify key use cases and metrics for all blockchains.
Hyperledger Fabric is built on a modular architecture that separates transaction processing into three phases: distributed logic processing and agreement ('chaincode'), transaction ordering, and transaction validation and commitment. This separation confers several advantages: Fewer levels of trust and verification are required across node types, and network scalability and performance are optimized.
|
|
|
|
Varies
|
Depends on implementation
|
500 transactions per block
|
