TrueCloudLab/neo-go
8
0
Fork 0
mirror of https://github.com/nspcc-dev/neo-go.git synced 2024-12-12 21:10:36 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs: update neox.md with the latest protocol changes

Browse source
This commit is contained in:
Roman Khimov 2020-08-10 15:14:34 +03:00
parent 8850ecd4ca
commit 47ed2eda43
1 changed files with 12 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
docs/neox.md
View file

@ -6,8 +6,9 @@ with two configuration options.
## What is neox ## What is neox
Neox is an extension of original Neo 2 node implemented in neox-2.x branch of Neox is an extension of original Neo 2 node originally implemented in neox-2.x
C# implementation. It includes the following main changes: branch of C# implementation (and then presented in the 2.11.0 official
release). It includes the following main changes:
* local state root generation for contract storages based on MPT * local state root generation for contract storages based on MPT
* consensus updates for state root exchange between CNs and generation of * consensus updates for state root exchange between CNs and generation of
verified (signed by CNs) state root verified (signed by CNs) state root
@ -43,22 +44,16 @@ entities which are consensus nodes.
### How and why consensus process was changed in neox ### How and why consensus process was changed in neox
Consensus nodes now exchange state root information with PrepareRequest Consensus nodes now exchange state root signatures for height N-1 during
messages, so the Primary node tells everyone its current state root hash consensus process for block N with PrepareRequest and PrepareResponse
(along with the block index that state root corresponds to) and the hash of messages.
the previous state root message. This data might also be versioned in case of
future updates, so there is a special field reserved for that too, but at the
moment it's always 0. Backups either confirm this data (if it matches their
local state) by proceeding with PrepareResponse or request a ChangeView if
there is some mismatch detected.
If all goes well CNs generate a signature for this state root data and If all goes well CNs collect enough signatures for this state root data and
exchange it with their Commit messages (along with new block generate (and broadcast) a `stateroot` message along with regular Commit
signatures). Effectively this creates another signed chain on the network that consensus messages. Effectively this creates another signed chain on the
is always one block behind from the main chain because the process of block `N` network that is always one block behind from the main chain because the
creation confirms the state resulting from processing of block `N - 1`. A process of block `N` creation confirms the state resulting from processing of
separate `stateroot` message is generated and sent along with the new block block `N - 1`.
broadcast.
### How P2P protocol was changed ### How P2P protocol was changed