|
|
|
@ -1714,7 +1714,7 @@ signatures. Finally, the consensus rules may differ in unanticipated
|
|
|
|
|
ways because of implicit consensus constraints imposed by system
|
|
|
|
|
limitations or implementation details. An example of the latter was seen
|
|
|
|
|
in the unanticipated hard fork during the upgrade of Bitcoin Core 0.7 to
|
|
|
|
|
0.8, which was caused by a limitation in the Berkley DB implementation
|
|
|
|
|
0.8, which was caused by a limitation in the Berkeley DB implementation
|
|
|
|
|
used to store blocks.
|
|
|
|
|
|
|
|
|
|
Conceptually, we can think of a hard fork as developing in four stages:
|
|
|
|
|