From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Barry Silbert segwit agreement
Date: Sun, 28 May 2017 22:51:46 +0200 [thread overview]
Message-ID: <1729851.ePRgbNd32q@strawberry> (raw)
In-Reply-To: <CADvTj4qdr2yGYFEWA7oVmL-KkrchYb5aQBRY9w0OK4ZVopSTSA@mail.gmail.com>
On Saturday, 27 May 2017 01:09:10 CEST James Hilliard wrote:
> > why?
>
> the main
> issue is due to 0.13.1+ having many segwit related features active
> already, including all the P2P components, the new network service
> flag, the witness-tx and block messages, compact blocks v2 and
> preferential peering.
Hmm, the flags are identical in 0.13 and 0.14 clients.
Either way, this is rather trivial to solve. If bugs in older clients mean
they can’t operate properly when SW is activated (via bit 4) but they don’t
know its activated (since they only look at bit1), then just ban them when
they misbehave.
And tell people to upgrade to a version where SegWit is less buggy.
> You would have to then have multiple activation
> codepaths to test for such as BIP141(active)->HF BIP141(inactive)->HF
> etc. By doing BIP141 first you then only have the BIP141(active)->HF
> activation codepath to test for, and you also can't be sure you can
> rely on BIP141(inactive)->HF activation codepath being the only one
> until segwit activation expires.
Heh, well, this is rather simple to solve by not having all those activation
codepaths and just picking **one**.
You can safely replace the bit1 activation code with a bit4 activation
logic, which is based on 80% and has no end-date.
We both know that the bip9 (bit1) based activation will not trigger before
the expiration date anyway.
These worries are rather trivial to solve if you do a little bit of proper
architecture of the solution. This honestly can’t be a reason for saying NO
to the majority of the mining hash power giving you a break and offering a
better SegWit activation.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2017-05-28 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 17:47 [bitcoin-dev] Barry Silbert segwit agreement Jacob Eliosoff
2017-05-26 18:48 ` Tom Zander
2017-05-26 20:02 ` Matt Corallo
2017-05-26 20:10 ` Jacob Eliosoff
2017-05-26 21:30 ` James Hilliard
2017-05-26 22:12 ` Tom Zander
[not found] ` <CADvTj4qdr2yGYFEWA7oVmL-KkrchYb5aQBRY9w0OK4ZVopSTSA@mail.gmail.com>
2017-05-28 20:51 ` Tom Zander [this message]
2017-05-28 23:28 ` James Hilliard
2017-05-26 22:44 ` Matt Corallo
-- strict thread matches above, loose matches on Subject: below --
2017-05-22 12:29 Daniele Pinna
2017-05-22 6:12 shaolinfry
2017-05-22 6:27 ` Peter Todd
2017-05-22 9:23 ` Hampus Sjöberg
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=1729851.ePRgbNd32q@strawberry \
--to=tomz@freedommail.ch \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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