From: Aymeric Vitte <vitteaymeric@gmail.com>
To: Luke Dashjr <luke@dashjr.org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>,
DKBryant@gmail.com
Subject: Re: [bitcoin-dev] BIP for Legacy Sign Verify functions
Date: Fri, 22 Dec 2017 11:29:13 +0100 [thread overview]
Message-ID: <4789faec-c6fb-3d05-1b4b-95ce7aefb373@gmail.com> (raw)
In-Reply-To: <201712212309.07243.luke@dashjr.org>
Le 22/12/2017 à 00:09, Luke Dashjr via bitcoin-dev a écrit :
> 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.
I already posted about this, then what is doing the pubkey in sigscript
for standard p2pkh transactions? (this was not the case some time ago)
--
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
next prev parent reply other threads:[~2017-12-22 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:26 [bitcoin-dev] BIP for Legacy Sign Verify functions Dan Bryant
2017-12-21 23:09 ` Luke Dashjr
2017-12-21 23:21 ` Dan Bryant
2017-12-22 10:29 ` Aymeric Vitte [this message]
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=4789faec-c6fb-3d05-1b4b-95ce7aefb373@gmail.com \
--to=vitteaymeric@gmail.com \
--cc=DKBryant@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.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