shaolinfry,
Not sure if you noticed my comments on your earlier orphaning proposal... but
if you did you should already know that I really like this proposal...
particularly since orphaning valid old blocks is completely unnecessary.
I really like how you pulled out the "lockinontimeout" variable so that this
same method could be used in future softfork proposals... instead of hardcoding
a special case hack for SegWit.
- it would be nice if the user could set this variable in a configuration file.
- it would be nice if the user could set the "nTimeout" in
"src/chainparams.cpp" in a configuratoin file too. This could be used allow a
user to expedite when a softfork would become active on his node when combined
with ."lockinontimeout".
Developers such as the Core team could put more conservative values in the
program, and then community members such as miners and nodes who feel more
strongly about SegWit could either compile their own settings or maybe copy a
popular configuration file if such was made possible.
Cheers,
Praxeology Guy
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
