|Consensus||Single Notary, Raft, BFT-SMaRt|
|Public / Private / Permissioned||Public, Permissioned; Private, Permissioned|
|Smart contract language(s) supported||Java, Kotlin|
|Transaction visibility||Private transactions between participants are hidden from all other participants.|
|Transaction ordering||Ordering provided by notary service as per consensus mechanism. In the BFT-SMaRt distributed notary, signatures from validating notaries can be specified in a customized manner.|
A single-node notary service that persists notarization requests in the network.
When using Raft deployed on n nodes, a Corda notary tolerates crashes of any t < n/2 of these nodes. Hence, at least 50% of the nodes must be running for the network to function.
For BFT-SMaRt to execute correctly, less than a third of all replicas of the service can be faulty at any moment. Hence, the total number of replicas n must be n >= 3f + 1, where f is the maximum number of faulty replicas.
Single Notary can be used for test networks and networks that do not have strict availability requirements.
Raft is not recommended for production.
BFT-SMaRt is a high-performance Byzantine Fault Tolerant State Machine Replication that relies on a leader to solve the classic Byzantine consensus problem that predates blockchains.
Single Notary can be used for networks that do not have strict availability requirements.
Raft on Corda has known limitations and is not recommended for production use.
BFT-SMaRt requires Java serialization which is disabled by default in Corda due to security risks, and it will only work in dev mode where this can be customized. There is no single shared ledger, only different shared vaults of facts between counterparties to a deal.
Capital markets, digital assets, digital identity, energy, global trade, government, healthcare, insurance, telecommunications.
Learn more about the free usage period to get started right away.
Complete the form below, and our experts will get in touch with you.