From: Peter Todd <pete@petertodd•org>
To: Chris Stewart <chris@suredbits•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Disallow insecure use of SIGHASH_SINGLE
Date: Tue, 5 Jun 2018 20:43:26 -0400 [thread overview]
Message-ID: <20180606004326.hpd3tmkjhdzclf2g@petertodd.org> (raw)
In-Reply-To: <CAGL6+mH3ah_e-+e0=ce0-HmkaqU1YzoGNS5JXCXDbojxpVvX8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Tue, Jun 05, 2018 at 07:17:52PM -0500, Chris Stewart via bitcoin-dev wrote:
> Do you have any thoughts on expanding this to SIGHASH_NONE? Perhaps someone
> else on the dev list can enlighten me, but is there a current use case for
> SIGHASH_NONE that would suffer from it being non standard?
SIGHASH_NONE is important as it's the only way that a multisig signers can
relinquish the need for them to sign without giving up the private key.
FWIW the SIGHASH_SINGLE bug can be used in similar ways too.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-06-06 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 18:53 Johnson Lau
2018-06-06 0:17 ` Chris Stewart
2018-06-06 0:43 ` Peter Todd [this message]
2018-06-06 0:49 ` Peter Todd
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=20180606004326.hpd3tmkjhdzclf2g@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=chris@suredbits$(echo .)com \
/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