Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor fixes #25

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion sections/01_Introduction.md
Original file line number Diff line number Diff line change
@@ -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.
4 changes: 2 additions & 2 deletions sections/02_Network.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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:

Expand Down
2 changes: 1 addition & 1 deletion sections/08_dBFT.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down