Terminology: "consensus rule change"

This commit is contained in:
str4d 2018-02-26 21:34:22 +00:00
parent c4bf8a86da
commit 1a5ab78f25
No known key found for this signature in database
GPG Key ID: 665DBCD284F7DAFF
1 changed files with 6 additions and 5 deletions

View File

@ -21,12 +21,12 @@ Branch
block, or the child of a parent block created under an older set of consensus rules (i.e. the parent block
is a member of a different branch). By definition, every block belongs to at most one branch.
Hard fork
Consensus rule change
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.
An intentional consensus rule change undertaken by the community in order to improve the network.
Abstract
@ -206,9 +206,10 @@ This proposal will be deployed with the Overwinter network upgrade.
Backward compatibility
======================
This proposal intentionally creates what is known as a "bilateral hard fork". Use of this mechanism requires
that all network participants upgrade their software to a compatible version within the upgrade window. Older
software will treat post-upgrade blocks as invalid, and will follow any pre-upgrade branch that persists.
This proposal intentionally creates what is known as a "bilateral consensus rule change". Use of this
mechanism requires that all network participants upgrade their software to a compatible version within the
upgrade window. Older software will treat post-upgrade blocks as invalid, and will follow any pre-upgrade
branch that persists.
Reference Implementation