From: Tom Harding <tomh@thinlink•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] New BIP: Dealing with dummy stack element malleability
Date: Fri, 2 Sep 2016 10:10:40 -0700 [thread overview]
Message-ID: <198f7a5e-7912-dfb2-1b61-388a4f81b7b5@thinlink.com> (raw)
In-Reply-To: <1317364559.64256.1472791258452@privateemail.com>
On 9/1/2016 9:40 PM, Johnson Lau via bitcoin-dev wrote:
> This BIP will be deployed by "version bits" BIP9 using the same parameters for BIP141 and BIP143, with the name "segwit" and using bit 1.
>
This fix has value outside of segwit. Why bundle the two together?
Shouldn't miners have to opportunity to vote on them independently?
next prev parent reply other threads:[~2016-09-02 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 4:40 Johnson Lau
2016-09-02 5:47 ` Peter Todd
2016-09-02 17:10 ` Tom Harding [this message]
2016-09-04 12:29 ` Johnson Lau
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=198f7a5e-7912-dfb2-1b61-388a4f81b7b5@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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