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 _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev