Random misreadings of your post aside (maybe it's time to moderate this list a
bit more again), I think this is a reasonable model, and certainly more
terminology/understanding is useful, given I and many others have been making
arguments based on these differences.
One thing you may wish to fu
o:bitcoin-dev@lists.linuxfoundation.org>
Sent: 4/5/2017 6:28 AM
To: bitcoin-dev<mailto:bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] A different approach to define and understand softforks
and hardforks
Softforks and hardforks are usually defined in terms of block validity (BIP99)
Softforks and hardforks are usually defined in terms of block validity (BIP99):
making valid blocks invalid is a softfork, making invalid blocks valid is a
hardfork, and SFs are usually considered as less disruptive as it is considered
to be “opt-in”. However, as shown below this technical defin