Clarify terminology

This commit is contained in:
str4d 2018-01-29 01:27:48 +00:00
parent 68cbeafdc6
commit f6664895d5
No known key found for this signature in database
GPG Key ID: 665DBCD284F7DAFF
1 changed files with 18 additions and 5 deletions

View File

@ -12,8 +12,21 @@
Terminology
===========
The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in
RFC 2119.
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as
described in RFC 2119.
The following terms are interpreted as follows:
Branch
A chain of blocks with common consensus rules, where the first block in the chain is not the genesis block,
but the child of a parent block created under an older set of consensus rules.
Hard fork
The creation of a new branch by a change in the consensus rules of the network. Nodes that do not recognize
the new rules will continue to follow the old branch.
Network Upgrade
An intentional hard fork undertaken by the community in order to improve the network.
Abstract
@ -27,9 +40,9 @@ software, and minimize the risks to both the upgrading network and those users o
Motivation
==========
Zcash is a *consensual currency*: nobody is ever going to force someone to use a specific version or a
specific branch of Zcash. [#consensual-currency]_ As such, different sub-communities will always have the
freedom to choose different variants or branches which offer different design trade-offs.
Zcash is a *consensual currency*: nobody is ever going to force someone to use a specific software
implementation or a specific branch of Zcash. [#consensual-currency]_ As such, different sub-communities will
always have the freedom to choose different variants or branches which offer different design trade-offs.
The current Zcash software includes an *auto-senescence* feature, causing nodes running a particular version
to automatically shut down 16 weeks after that version was released. This was implemented for several reasons