From b0fcfaf6067eff4bd2d41d18b4957ae649f45053 Mon Sep 17 00:00:00 2001 From: todd zhang Date: Wed, 21 Sep 2016 21:51:09 +0800 Subject: [PATCH 1/2] add wikipedia hyper link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index da4d4cd..a6a8a33 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ See [Performance and Crypto](#performance-and-crypto-new-april-2016) for full de Juno is a BFT Consensus-based Distributed Cryptoledger providing an alternative to current Blockchain-based Smart-Contract systems. -Blockchain-based approaches to Smart Contract systems are a mismatch for many enterprise applications, as they are purpose-built for *anonymous participation*, necessitating computationally-intensive solutions fault-tolerance and consensus (ie mining, proof-of-stake). Enterprise applications generally have no need to support anonymous actors, so the utility of using consensus algorithms like Paxos or Raft is clear. However no clear solution exists that can provide the Byzantine fault-tolerant (BFT) features of a blockchain on a consensus platform. +Blockchain-based approaches to Smart Contract systems are a mismatch for many enterprise applications, as they are purpose-built for *anonymous participation*, necessitating computationally-intensive solutions fault-tolerance and consensus (ie mining, proof-of-stake). Enterprise applications generally have no need to support anonymous actors, so the utility of using consensus algorithms like Paxos or Raft is clear. However no clear solution exists that can provide the Byzantine fault-tolerant ([BFT](https://en.wikipedia.org/wiki/Byzantine_fault_tolerance)) features of a blockchain on a consensus platform. Enter Juno, "hardening" the [Raft][Raft] consensus protocol with BFT features. Juno started as a fork of the [Tangaroa][Tangaroa Paper] project, which sought to enhance Raft with BFT features like crypto-signatures of all messages, incremental hashing, and independent commit-proof verification. From 5678a0c04f165e4f01e313d50ac860abb0b63ed1 Mon Sep 17 00:00:00 2001 From: todd zhang Date: Wed, 21 Sep 2016 21:54:19 +0800 Subject: [PATCH 2/2] add wikipedia hyper link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a6a8a33..acd1789 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,7 @@ See [Performance and Crypto](#performance-and-crypto-new-april-2016) for full de ## Introduction -Juno is a BFT Consensus-based Distributed Cryptoledger providing an alternative to current Blockchain-based Smart-Contract systems. +Juno is a [BFT](https://en.wikipedia.org/wiki/Byzantine_fault_tolerance) Consensus-based Distributed Cryptoledger providing an alternative to current Blockchain-based Smart-Contract systems. Blockchain-based approaches to Smart Contract systems are a mismatch for many enterprise applications, as they are purpose-built for *anonymous participation*, necessitating computationally-intensive solutions fault-tolerance and consensus (ie mining, proof-of-stake). Enterprise applications generally have no need to support anonymous actors, so the utility of using consensus algorithms like Paxos or Raft is clear. However no clear solution exists that can provide the Byzantine fault-tolerant ([BFT](https://en.wikipedia.org/wiki/Byzantine_fault_tolerance)) features of a blockchain on a consensus platform.