BIP for Legacy Sign Verify functions

BIP for Legacy Sign Verify functions
2017-12-21 23:09 ` Luke Dashjr
  
From: Dan Bryant @ 2017-12-21 22:26 UTC (permalink / raw)
  To: Bitcoin Protocol Discussion

[-- Attachment #1: Type: text/plain, Size: 366 bytes --]

https://github.com/brianddk/bips/blob/legacysignverify/bip-0xyz.mediawiki

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.

Original reference thread [Sign / Verify message against SegWit P2SH
addresses]

[-- Attachment #2: Type: text/html, Size: 580 bytes --]

 permalink raw reply	[|nested]
2017-12-21 22:26 [bitcoin-dev] BIP for Legacy Sign Verify functions Dan Bryant

  2017-12-21 23:21   ` Dan Bryant
  2017-12-22 10:29   ` Aymeric Vitte
  
From: Luke Dashjr @ 2017-12-21 23:09 UTC (permalink / raw)
  To: bitcoin-dev, DKBryant

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


 permalink raw reply	[|nested]
2017-12-21 23:09 ` Luke Dashjr

  2017-12-22 10:29   ` Aymeric Vitte
  
From: Dan Bryant @ 2017-12-21 23:21 UTC (permalink / raw)
  To: Luke Dashjr;  Bitcoin Protocol Discussion

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

Thank you... I've updated.

> New schemes should probably NOT be based on the current one.

Fair enough... I still think there are those who would still like an
existing sign/verify BIP to reference.

On Thu, Dec 21, 2017 at 5:09 PM, Luke Dashjr <luke@dashjr•org> wrote:

> 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
>

[-- Attachment #2: Type: text/html, Size: 1801 bytes --]

 permalink raw reply	[|nested]
2017-12-21 23:09 ` Luke Dashjr
  2017-12-21 23:21   ` Dan Bryant

  2017-12-22 23:06     ` Aymeric Vitte
  
From: Aymeric Vitte @ 2017-12-22 10:29 UTC (permalink / raw)
  To: Luke Dashjr, Bitcoin Protocol Discussion, DKBryant



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



 permalink raw reply	[|nested]
2017-12-22 10:29   ` Aymeric Vitte

  
From: Aymeric Vitte @ 2017-12-22 23:06 UTC ( / )
  To: Luke Dashjr, Bitcoin Protocol Discussion, DKBryant

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