|
|
|
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.
|
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.
|
SGX / PoET
All transactions are signed by known identities.
PoET implementation will depend on that of SGX. SGX is a set of instructions which allows application to run in sectioned-off areas of memory called enclaves. This aims to protect sensitive data and code from disclosure or tampering, both when stored and at runtime. Unfortunately, since Intel first introduced SGX in 2013, several weaknesses have been found in its design.
https://www.theregister.co.uk/2016/02/01/sgx_secure_until_you_look_at_the_detail/
|
|
|
|
Permissioned
|
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, Permissionless depending on application
Hyperledger Sawtooth supports both permissioned and permissionless blockchain networks. This provides flexibility but lacks the prescriptive level of security hyperledger fabric has.
|
|
|
|
Privacy concerns are addressed through the pluggable uniqueness services, and restriction of viewing transactions.
|
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.
|
Configrable permissions for any node cluster within the network
Sawtooth is built to solve the challenges of permissioned (private) networks. Clusters of Sawtooth nodes can be easily deployed with separate permissioning. There is no centralized service that could potentially leak transaction patterns or other confidential information. There is no concept of private channels as seen with Hyperledger fabric
contributors are investigating both trusted execution and zero-knowledge cryptographic approaches
|
|
|
|
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.
|
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
|
PoET
Dynamic, Pluggable Consensus Algorithms
Sawtooth supports pluggable consensus algorithms but offers their own method —Proof of Elapsed Time (PoET). The PoET consensus has each validating participant wait a random amount of time. The first person to finish waiting becomes the leader of the new block. This provides a secure authority mechanism without the computational race and energy draw of Proof of Work (PoW).
|
|
|
|
Efficiency |
|
|
|
|
Fast
Built for financial applications
|
Fast
3-4 seconds : set to improve with future updates. See future planned work.
|
Fast
Depends on implementation. Processes transactions in parallel to accelerate block creation and validation
|
|
|
Block Confirmation Time
Details
|
TBD
|
TBD
|
Varies
Depends on implementation. Processes transactions in parallel to accelerate block creation and validation
|
|
|
|
Development |
|
|
|
Proprietary Codebase
Details
|
Open Source
|
Open source with proprietary applications
The Ripple protocol is open source: https://github.com/ripple . Proprietary work is xCurrent, xRapid, xVia
|
Open Source
|
|
|
|
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
|
Permissioned Network, Public Architecture
Ripple uses a decentralized network, but has trusted validator nodes who confirm transactions through the 'last closed ledger'.
|
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
3 different plug and play offers on top of the protocol layer for specific needs: xCurrent, xRapid, xVia
|
Modular Architecture. Incorporates IoT Sensors that can broaden the use case.
Location, Temperature, Humidity, Shock, Tilt, Motion, Shock - all examples of data that can be captured.
|
|
|
|
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/
|
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.
|
1000 TPS. Built to be scalable in the way that consensus algorithms can be changed, applications are separate from the core system, and transactions can occur in parallel.
The different consensus mechanism features were designed to cater to networks of different sizes and with different requirements. Sawtooth targets large distributed validator populations that do not require much computational power.
|
|
|
|
Varies
|
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
|
