From: praxeology_guy <praxeology_guy@protonmail•com>
To: shaolinfry <shaolinfry@protonmail•ch>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Draft BIP: Version bits extension with guaranteed lock-in
Date: Fri, 07 Apr 2017 04:38:03 -0400 [thread overview]
Message-ID: <G5La89Lv4mv4xT4iey5PieUSZAwELWfUFrNQV--7SvAV8-ps7W6id6Xoj-9pkq5wTJmL8WXTDKhFWWNmJecyG27BdZr9bNe51Z-PtRrAPWY=@protonmail.com> (raw)
In-Reply-To: <oO9hdZXHMpEDF84P5wXwMd0JsIeRqcDGVDHjgdNWxq81WpkqCIqrdMgEHmWAmM4a6i1cxDrUkgTPp_kx7N5CZxqwWP_5MtZ5DTAF2VorCp4=@protonmail.ch>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1242 bytes --]
next prev parent reply other threads:[~2017-04-07 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 21:25 shaolinfry
2017-04-07 8:38 ` praxeology_guy [this message]
2017-04-07 13:55 ` Ryan Grant
2017-04-07 17:56 ` praxeology_guy
2017-04-08 4:48 ` Ryan Grant
2017-04-18 12:37 Kekcoin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='G5La89Lv4mv4xT4iey5PieUSZAwELWfUFrNQV--7SvAV8-ps7W6id6Xoj-9pkq5wTJmL8WXTDKhFWWNmJecyG27BdZr9bNe51Z-PtRrAPWY=@protonmail.com' \
--to=praxeology_guy@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=shaolinfry@protonmail$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox