📅 Original date posted:2017-12-22 📝 Original message:Scriptsig not "sigscript" ...

Aymeric Vitte [ARCHIVE] /

npub15fc…5grz

2023-06-07 18:09:01

in reply to nevent1q…eavl

📅 Original date posted:2017-12-22
📝 Original message: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

Author Public Key

npub15fc36esk6dy2x4ptk2ner209rl9u0d736gr99edtu9knu9uny80s4g5grz

Show more details

Published at

2023-06-07 18:09:01

Kind type

1 Short Text Note

Event JSON

{ "id": "07c7fea80c2a3831f9b649c12619ae849314eb15e13494015a3f851d8290871a", "pubkey": "a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df", "created_at": 1686161341, "kind": 1, "tags": [ [ "e", "a95dc4624423bc647bfe926615c717637c1b537dc203c75309dfccd8f9b44c49", "", "root" ], [ "e", "5afbbb2419fe1d410b9579058365b231dd68dbc35021fe85bac0fedd5dac99f9", "", "reply" ], [ "p", "a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df" ] ], "content": "📅 Original date posted:2017-12-22\n📝 Original message:Scriptsig not \"sigscript\" below\n\nNow you must answer this question, because this is what we call a hard fork\n\n\nLe 22/12/2017 à 11:29, Aymeric Vitte a écrit :\n\u003e\n\u003e Le 22/12/2017 à 00:09, Luke Dashjr via bitcoin-dev a écrit :\n\u003e\u003e What is actually done, is using the signature + message to perform key \n\u003e\u003e recovery, to extract the public key of the signer, and then hashing that and \n\u003e\u003e comparing it to the address provided.\n\u003e I already posted about this, then what is doing the pubkey in sigscript\n\u003e for standard p2pkh transactions? (this was not the case some time ago)\n\u003e\n\n-- \nBitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions\nZcash wallets made simple: https://github.com/Ayms/zcash-wallets\nBitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets\nGet the torrent dynamic blocklist: http://peersm.com/getblocklist\nCheck the 10 M passwords list: http://peersm.com/findmyass\nAnti-spies and private torrents, dynamic blocklist: http://torrent-live.org\nPeersm : http://www.peersm.com\ntorrent-live: https://github.com/Ayms/torrent-live\nnode-Tor : https://www.github.com/Ayms/node-Tor\nGitHub : https://www.github.com/Ayms", "sig": "99ef2c6dd4b47ac5cd6cf609d2b0867984f3ce2dd2de51e389039c882405a7712c151154e284f59e342ad4c8aee3744d8b9ec0e769d484e5762d37d4de0e9e8e" }