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

Adjust indices for epoch range to be more intuitive 

The epoch range is now clearly for the upgrade activated at ACTIVATION_HEIGHT_N.
This commit is contained in:
str4d 2018-02-05 01:24:05 +00:00
parent 7e3439ebb4
commit 621229a657
No known key found for this signature in database
GPG Key ID: 665DBCD284F7DAFF
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
drafts/str4d-overwinter-activation/draft1.rst
View File

@ -112,8 +112,8 @@ require ``ACTIVATION_HEIGHT`` to be globally unique, or even locally unique; mul
occur in parallel, as long as they are non-overlapping (only one will activate on any given chain).
Concretely, this means that the Zcash blockchain is broken into "epochs" of block height intervals
``[ACTIVATION_HEIGHT_{N-1}, ACTIVATION_HEIGHT_N)`` (ie. including ``ACTIVATION_HEIGHT_{N-1}`` and excluding
``ACTIVATION_HEIGHT_N``), on which consensus rule sets are defined.
``[ACTIVATION_HEIGHT_N, ACTIVATION_HEIGHT_{N+1})`` (ie. including ``ACTIVATION_HEIGHT_N`` and excluding
``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
by block height checks. For example: