From: Johnson Lau <jl2012@xbt•hk>
To: bitcoin-dev@lists•linuxfoundation.org, Luke Dashjr <luke@dashjr•org>
Subject: Re: [bitcoin-dev] New BIP: Low S values signatures
Date: Tue, 16 Aug 2016 13:46:11 -0400 (EDT) [thread overview]
Message-ID: <1210216648.90169.1471369571065@privateemail.com> (raw)
In-Reply-To: <201608161020.28467.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
> On August 16, 2016 at 6:20 AM Luke Dashjr <luke@dashjr•org> wrote:
>
>
> 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?
That's an implicit CHECKSIG. Will clarify.
>
> > 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?
IsLowDERSignature is the function in Bitcoin Core. That's a bit complicated as the real checking function is not directly called. I'll clarify.
>
> Luke
[-- Attachment #2: Type: text/html, Size: 1224 bytes --]
next prev parent reply other threads:[~2016-08-16 17:46 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
2016-08-16 17:46 ` Johnson Lau [this message]
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=1210216648.90169.1471369571065@privateemail.com \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)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