mirror of https://github.com/zcash/zips.git
ZIP-252: Add a Zebra section
This commit is contained in:
parent
143dc209a8
commit
2834b6d2ae
32
zip-0252.rst
32
zip-0252.rst
|
@ -138,6 +138,38 @@ The implementation is similar to that for Overwinter which was described in
|
|||
However, NU5 nodes will have a preference for connecting to other NU5 nodes, so
|
||||
pre-NU5 nodes will gradually be disconnected in the run up to activation.
|
||||
|
||||
Support in Zebra
|
||||
================
|
||||
|
||||
**TODO: Update as needed**
|
||||
|
||||
Support for NU5 on testnet will be implemented in Zebra version 1.0.0, which
|
||||
will advertise protocol version 170012. Support for NU5 on mainnet will be implemented
|
||||
in Zebra version 2.0.0, which will advertise protocol version 170013.
|
||||
|
||||
|
||||
Backward compatibility in zcashd
|
||||
--------------------------------
|
||||
|
||||
The minimum peer protocol version that NU5-compatible Zebra nodes will connect to
|
||||
is 170002. However, Zebra will immediately disconnect from nodes with a protocol
|
||||
version less than:
|
||||
|
||||
- 170012 on testnet, or
|
||||
- 170013 on mainnet.
|
||||
|
||||
NU5 deployment for Zebra
|
||||
--------------------------------
|
||||
|
||||
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
|
||||
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
|
||||
==========
|
||||
|
|
Loading…
Reference in New Issue