|
|
|
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
For more information:
http://hyperledgerdocs.readthedocs.io/en/latest/security_model.html
|
No data encryption or channel partition and is public.
Merkle Patricia Trie Data structure
Data and contracts in Ethereum are encoded but not encrypted and all data is public - therefore all sensitive data should be encrypted locally and hash stored to prove authenticity.
|
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.
|
|
|
|
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.
|
Permissionless
Anyone can download the protocol and validate transactions making it less secure
|
Permissioned
|
|
|
|
Private Channels
A Private Channel is a subnet communication between two or more parties in the network that performs a private and confidential transaction.
|
Limited (zk-SNARKs, Ring signatures)
Privacy in this public permissionless network has been limited. Since the Metropolis hard fork, it became possible to integrate more cryptographic operations in smart contracts - two kinds of technologies are implemented: zk-SNARKs and Ring Signatures.
‘Zero-knowledge’ proofs allow one party (the prover) to prove to another (the verifier) that a statement is true, without revealing any information beyond the validity of the statement itself.
Ring Signatures are a cryptographic technology first introduced in 2001. It enables any member of a group of users to perform a digital signature, that can be proven to be made by a member of this group, while it is impossible to determine by which member of the group.
https://btcmanager.com/good-news-privacy-bitcoin-ethereum/
|
Privacy concerns are addressed through the pluggable uniqueness services, and restriction of viewing transactions.
|
|
|
|
Algorithms |
|
|
|
|
Multiple options:
Pluggable Framework
No-op (no consensus)
PBFT
PBFT - Practical Byzantine Fault Tolerance
|
PoW & PoS
Proof of work (PoW) + PoS-based public blockchains in Ethereums upcoming Casper implementation. Opposed to the PoW consensus protocol, the PoS protocol achieves consensus through stakers, sometimes referred to as minters who “stake” their coins by locking them down in specialized wallets. With stakers at work, mining will become redundant, meaning the Ethereum network post-Casper will rely on stakers and staking pools instead of miners for its operability.
|
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.
|
|
|
|
Efficiency |
|
|
|
|
Varies
Depends on implementation
|
Moderate
|
Fast
Built for financial applications
|
|
|
Block Confirmation Time
Details
|
Varies
Depends on implementation
|
~12 blocks
|
TBD
|
|
|
|
Development |
|
|
|
Proprietary Codebase
Details
|
Open Source
https://github.com/hyperledger/fabric
|
Open Source
https://github.com/ethereum/
|
Open Source
|
|
|
|
General |
|
|
|
Blockchain / DLT type
Details
|
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 with Private Forks
Ethereum can be a public or private blockchain. The Ethereum Main network is obviously a public blockchain, but with increasing enterprise-focus a number of projects and consortiums (Ethereum Aliiance) have been launched that develop private blockchains (e.g. Quorum)
|
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
|
|
|
|
Modular Architecture is a core focus of Platform
|
Generic, with DApp and Smart Contract support for wider applications
For Ethereum it is not modularity that stands out but the provision of a generic platform suitable for various types of transactions and applications
|
Less focus on modularity
Focus is on financial applications, but may support more use cases in the future.
|
|
|
|
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.
|
limited by PoW
currently supports a maximum of 15 TPS
designed for public networks, limited by Proof of Work (PoW) consensus
|
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/
|
|
|
|
500 transactions per block
|
Varies
https://bitinfocharts.com/comparison/size-eth.html#3m
|
Varies
|
