From ae02cc65967ef12050a9902d840d383e9bd4ae01 Mon Sep 17 00:00:00 2001 From: Albert Date: Mon, 1 Jul 2019 10:39:25 +0800 Subject: [PATCH 1/2] Fix links --- sections/02_Network.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sections/02_Network.md b/sections/02_Network.md index 5787b9b..80c4057 100644 --- a/sections/02_Network.md +++ b/sections/02_Network.md @@ -27,7 +27,7 @@ Peer-to-peer (P2P) communication between nodes is the core on fully distributed ### P2P Protocol Specification -P2P commands can be found on [Neo Project](https://https://github.com/neo-project/neo) repository^[Developers can look directly on _neo/Network/P2P_ folder, while this section is a work on progress]. +P2P commands can be found on [Neo Project](https://github.com/neo-project/neo) repository^[Developers can look directly on _neo/Network/P2P_ folder, while this section is a work on progress]. ### Message compression @@ -42,7 +42,7 @@ A trivial way for interacting with external world can be done by RPC's calls, wh ### RPC Protocol Specification -RPC commands can be found on [Neo Project](https://https://github.com/neo-project/neo) repository and also [Neo Plugins](https://https://github.com/neo-project/neo-plugins). +RPC commands can be found on [Neo Project](https://github.com/neo-project/neo) repository and also [Neo Plugins](https://github.com/neo-project/neo-plugins). A summary of RPC commands on Neo network: From 3f0effaf792c00ff409a9528984eb57c486f8802 Mon Sep 17 00:00:00 2001 From: Albert Date: Wed, 3 Jul 2019 16:45:45 +0800 Subject: [PATCH 2/2] Minor fixes --- sections/01_Introduction.md | 2 +- sections/08_dBFT.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sections/01_Introduction.md b/sections/01_Introduction.md index 3baa8e1..80ba236 100644 --- a/sections/01_Introduction.md +++ b/sections/01_Introduction.md @@ -1,6 +1,6 @@ # Introduction -The Green Paper is a community-driven initiative to provide a technical specification for Neo blockchain. +The Yellow Paper is a community-driven initiative to provide a technical specification for Neo blockchain. It is organized in sections, describing diverse details of the protocol, from consensus mechanisms, cryptography and smart contracts. Every part of the protocol may be covered here, although it is recommended to keep the scope as limited as possible to fundamental pieces of the technology. These topics are suggested by Neo community and may be changed in the future, so feel free to contribute. diff --git a/sections/08_dBFT.md b/sections/08_dBFT.md index c57f0e9..e3f795a 100644 --- a/sections/08_dBFT.md +++ b/sections/08_dBFT.md @@ -32,7 +32,7 @@ Given $n=3f+1$ replicas of a State Machine, organized as Primary and Backup node * Safety property ensures that all processes will execute as atomic, either executing on all nodes, or reverting as a whole. This is possible due to the deterministic nature of the process (executed on every node), which is also valid for the NEO network and blockchain protocols in general. -* Liveness guarantees that the network won't be stopped (unless more than $f$ byzantine nodes exist), by using a mechanism called "change view", which allows Backup nodes to switch Primary node when it seems Byzantine, as well as when quorum of the majority is not achieved. +* Liveness guarantees that the network won't be stopped (unless more than $f$ byzantine nodes exist), by using a mechanism called "change view", which allows Backup nodes to switch a Primary node when it seems Byzantine, as well as when quorum of the majority is not achieved. A timeout mechanism is used, and by doubling delays exponentially at every view, pBFT can prevent attacks from malicious network delays that cannot grow indefinitely. In the current formula, timeout happens following a left-shift operator according to the current view number, for example: