|
|
Security |
|
|
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
|
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.
|
No data encryption or channel partition and is public.
Merkle Patricia Trie Data structure
|
|
|
Consortium
Permissioned, private network.
|
|
|
|
|
|
Privacy concerns are addressed through the pluggable uniqueness services, and restriction of viewing transactions.
|
Limited (zk-SNARKs, Ring signatures)
|
|
|
Algorithms |
|
|
Multiple options:
Pluggable Framework
No-op (no consensus)
PBFT
|
Notaries - Pluggable Framework, Validity consensus and Uniqueness consensus
|
|
|
|
Efficiency |
|
|
|
|
|
|
|
|
|
|
|
|
Development |
|
|
|
|
|
|
|
General |
|
|
Federated / Consortium, Permissioned Network
|
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.
|
Public with Private Forks
|
|
|
Modular Architecture is a core focus of Platform
|
|
Generic, with DApp and Smart Contract support for wider applications
|
|
|
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.
|
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
|
limited by PoW
currently supports a maximum of 15 TPS
|
|
|
500 transactions per block
|
|
|
