From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, DKBryant@gmail•com
Subject: Re: [bitcoin-dev] BIP for Legacy Sign Verify functions
Date: Thu, 21 Dec 2017 23:09:05 +0000 [thread overview]
Message-ID: <201712212309.07243.luke@dashjr.org> (raw)
In-Reply-To: <CAAUFj100ULfTbEorSK2PF5nvW-R_TCMOiboBBEMj+eS5upgU8Q@mail.gmail.com>
On Thursday 21 December 2017 10:26:25 PM Dan Bryant via bitcoin-dev wrote:
> https://github.com/brianddk/bips/blob/legacysignverify/bip-0xyz.mediawiki
It's not even correct... Your first "verify message" step is not possible; you
can't get a public key from an address.
What is actually done, is using the signature + message to perform key
recovery, to extract the public key of the signer, and then hashing that and
comparing it to the address provided.
> Although this is a well established functionality, it has never been
> published in a BIP. My proposal is simply to provide a reference point for
> future expansion of these capabilities into new address schemes.
New schemes should probably NOT be based on the current one.
Luke
next prev parent reply other threads:[~2017-12-21 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:26 Dan Bryant
2017-12-21 23:09 ` Luke Dashjr [this message]
2017-12-21 23:21 ` Dan Bryant
2017-12-22 10:29 ` Aymeric Vitte
2017-12-22 23:06 ` Aymeric Vitte
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=201712212309.07243.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=DKBryant@gmail$(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