From: Aymeric Vitte <vitteaymeric@gmail.com>
To: Luke Dashjr <luke@dashjr.org>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	DKBryant@gmail.com
References: <CAAUFj100ULfTbEorSK2PF5nvW-R_TCMOiboBBEMj+eS5upgU8Q@mail.gmail.com>
	<201712212309.07243.luke@dashjr.org>
	<4789faec-c6fb-3d05-1b4b-95ce7aefb373@gmail.com>
Message-ID: <2b73d37b-812a-1653-a0be-e4b8c0fb6772@gmail.com>
Date: Sat, 23 Dec 2017 00:06:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101
	Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <4789faec-c6fb-3d05-1b4b-95ce7aefb373@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: fr
Subject: Re: [bitcoin-dev] BIP for Legacy Sign Verify functions
Precedence: list

Scriptsig not "sigscript" below

Now you must answer this question, because this is what we call a hard fork


Le 22/12/2017 à 11:29, Aymeric Vitte a écrit :
>
> 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