From: Johnson Lau <jl2012@xbt.hk>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] New BIP: Low S values signatures
Date: Wed, 17 Aug 2016 08:43:47 -0400 (EDT) [thread overview]
Message-ID: <212784600.96759.1471437827809@privateemail.com> (raw)
In-Reply-To: <835406850.86951.1471342201363@privateemail.com>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
The BIP146 has been updated to include NULLDUMMY* as part of the softfork:
https://github.com/bitcoin/bips/pull/435
NULLDUMMY is a trivial softfork to fix malleability related to the extra stack element consumed by CHECKMULTISIG(VERIFY). It is probably more important than LOW_S since without that an attacker may replace the stack element with any value.
[-- Attachment #2: Type: text/html, Size: 519 bytes --]
next prev parent reply other threads:[~2016-08-17 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 10:10 [bitcoin-dev] New BIP: Low S values signatures Johnson Lau
2016-08-16 10:20 ` Luke Dashjr
2016-08-16 17:46 ` Johnson Lau
2016-08-17 12:43 ` Johnson Lau [this message]
2016-09-02 8:28 ` 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=212784600.96759.1471437827809@privateemail.com \
--to=jl2012@xbt.hk \
--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