zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update Zebra release and connection behaviour

This commit is contained in:
teor 2022-04-06 06:55:49 +10:00 committed by Deirdre Connolly
parent 12ff90a307
commit bc9427282a
1 changed files with 4 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
zip-0252.rst
View File

@ -191,9 +191,9 @@ rules on Testnet:
validating a strict subset of the NU5 consensus rules. This version had an validating a strict subset of the NU5 consensus rules. This version had an
activation height of 1599200, as described in section `NU5 deployment`_ activation height of 1599200, as described in section `NU5 deployment`_
above. above.
- `zebrad` v1.0.0-beta.7 will fully validate what is expected to be the final - `zebrad` v1.0.0-beta.8 will fully validate what is expected to be the final
revision of the NU5 consensus rules. As part of these consensus rule changes, revision of the NU5 consensus rules. As part of these consensus rule changes,
`zebrad` v1.0.0-beta.7 will automatically re-download the entire chain from `zebrad` v1.0.0-beta.8 will automatically re-download the entire chain from
genesis, then follow an alternate chain starting at height 1599200. It will genesis, then follow an alternate chain starting at height 1599200. It will
advertise protocol version 170050. advertise protocol version 170050.
@ -214,13 +214,8 @@ NU5 deployment for Zebra
------------------------ ------------------------
For each network, at the corresponding NU5 activation height, nodes compatible For each network, at the corresponding NU5 activation height, nodes compatible
with NU5 activation on that network will close any new connections with pre-NU5 with NU5 activation on that network will close existing connections with pre-NU5
peers. peers, and reject new connections from pre-NU5 peers.
Since Zebra maintains a reasonably strict internal request-response protocol,
pre-NU5 nodes will gradually be disconnected after activation. (Nodes are
temporarily disconnected if they send gossip or chain sync hints outside the
strict request-response sequence that Zebra expects.)
References References