Clarifications

This commit is contained in:
str4d 2018-02-26 22:19:15 +00:00
parent f1b89467f4
commit c48da32f5f
No known key found for this signature in database
GPG Key ID: 665DBCD284F7DAFF
1 changed files with 3 additions and 3 deletions

View File

@ -114,8 +114,8 @@ Concretely, this means that the Zcash blockchain is broken into "epochs" of bloc
``[ACTIVATION_HEIGHT_N, ACTIVATION_HEIGHT_{N+1})`` (i.e. including ``ACTIVATION_HEIGHT_N`` and excluding ``[ACTIVATION_HEIGHT_N, ACTIVATION_HEIGHT_{N+1})`` (i.e. including ``ACTIVATION_HEIGHT_N`` and excluding
``ACTIVATION_HEIGHT_{N+1}``), on which consensus rule sets are defined. ``ACTIVATION_HEIGHT_{N+1}``), on which consensus rule sets are defined.
Consensus rules themselves (and any network behavior or surrounding code that depends on them) MUST be gated When a consensus rule depends on activation of a particular upgrade, its implementation (and that of any
by block height checks. For example: network behavior or surrounding code that depends on it) MUST be gated by a block height check. For example:
.. code:: cpp .. code:: cpp
@ -140,7 +140,7 @@ Incoming blocks known to have a particular height (due to their parent chain bei
validated under the consensus rules corresponding to the expected branch ID for that height. validated under the consensus rules corresponding to the expected branch ID for that height.
Incoming blocks with unknown heights (because at least one block header in their parent chain is unknown) Incoming blocks with unknown heights (because at least one block header in their parent chain is unknown)
MAY be cached for future consideration after all their parents have been received. MAY be cached, so that they can be reconsidered in the future after all their parents have been received.
Chain reorganization Chain reorganization
```````````````````` ````````````````````