1
0
mirror of https://github.com/bitcoin/bips.git synced 2025-01-18 21:35:13 +01:00

Bip-99/Add details to definitions

This commit is contained in:
Andy Chase 2015-09-04 15:15:08 -07:00 committed by Jorge Timón
parent d954832e30
commit 1da1397d54

View File

@ -25,19 +25,17 @@ deployment of changes.
==Definitions==
- Software fork: in free software, an existing project can be copied
and extended/maintained without permission from the original
project's maintainers.
- Consensus fork: a divergence in the implementation of the
verification rules can impede the expected eventual convergence of
the network in a single chain that has the most proof of work and
also satisfies the rules. This can be intentional or be caused by a
bug in consensus validation reimplementations.
- Softfork: an intentional consensus fork where everything that
was previously invalid remains invalid, but some things that were
valid also become invalid. A majority of miners can impose
these kind of changes and they also have some deployment advantages.
- Hardfork: an intentional consensus fork that is not a softfork.
;Software fork
: A copy of an existing project where management is separate from the existing project.
;Consensus fork
: A divergence in the implementation of the verification rules can impede the expected eventual convergence of the network in a single chain that has the most proof of work and also satisfies the rules. This can be intentional or be caused by a bug in consensus validation reimplementations.
;Softfork
: A change to the Bitcoin protocol wherein previously valid blocks and transactions become invalid. A hashrate majority miners can enforce the new rules so that the change enforced across all clients. Softforks are backward compatible.
;Hardfork
: A change to the Bitcoin protocol that makes previously invalid blocks valid. Hardforks require all users to upgrade.
==Taxonomy of consensus forks==