From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Johnson Lau <jl2012@xbt•hk>
Subject: Re: [bitcoin-dev] New BIP: Low S values signatures
Date: Tue, 16 Aug 2016 10:20:27 +0000 [thread overview]
Message-ID: <201608161020.28467.luke@dashjr.org> (raw)
In-Reply-To: <835406850.86951.1471342201363@privateemail.com>
On Tuesday, August 16, 2016 10:10:01 AM Johnson Lau via bitcoin-dev wrote:
> Specification
>
> Every signature passed to OP_CHECKSIG, OP_CHECKSIGVERIFY, OP_CHECKMULTISIG,
> or OP_CHECKMULTISIGVERIFY, to which ECDSA verification is applied,
Not 20-byte witness v0 programs?
> These operators all perform ECDSA verifications on pubkey/signature pairs,
> iterating from the top of the stack backwards. For each such verification,
> if the signature does not pass the IsLowDERSignature check,
"the IsLowDERSignature check" is not well-defined. Probably intend to
reference the previous paragraph?
Luke
next prev parent reply other threads:[~2016-08-16 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 10:10 Johnson Lau
2016-08-16 10:20 ` Luke Dashjr [this message]
2016-08-16 17:46 ` Johnson Lau
2016-08-17 12:43 ` Johnson Lau
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=201608161020.28467.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jl2012@xbt$(echo .)hk \
/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