📅 Original date posted:2019-02-18
📝 Original message:The proposal includes actual code that does verification, but I didn't
include code for signing. I thought it could be inferred, but I could at
least include a description of how to sign. I am not sure exactly what part
you are referring to by "keys speech", but the signatures are done by ECDSA
keys so it's hard to not include anything about keys even though that's not
the main topic. The "Background on ECDSA keys" section was mainly meant to
give background about what kind of keys Bitcoin uses, for people who
already know that they can easily skip this section so I would probably
think it's best just to leave in. Maybe it should be at the end as an
addendum though. Yes, I did not invent any of this, I'm just documenting
what people actually seem to do because I had to verify signatures as part
of a project I'm working on. I would have liked to have had this document
when I started the project so I thought it might be useful to others since
as far as I can tell this was not specified anywhere. The reason for
including this data in the header is the same that compressed/uncompressed
is included in the header so that you know which type of key the signature
is from and you don't have to try all options to see if any matches. This
is why Trezor did that way and why I documented it. I'm sure there are
other ways to do this, but since this is out there in the field being used
and is a reasonable solution, I thought I'd write it up.
On Mon, Feb 18, 2019 at 2:59 PM Aymeric Vitte <vitteaymeric at gmail.com>
wrote:
> Then, since you wrote this proposal, maybe you should add the very precise
> description of the signing/verification process since it is documented
> nowhere
>
> I don't get the use of the speech regarding keys while it should focus on
> signatures which are summarized in a vague sentence inspired by your ref
> [2] with a not very logical link to the next paragraph stating that r,s
> should be 32B and the whole thing 65B with a header of 1B, you did not
> invent it, that's probably the rule, not sure where it is specified again
> and for what purpose, the header seems completely of no use especially when
> you extend to segwit/bech32 since you just have to check that related
> compressed key matches
> Le 17/02/2019 à 15:14, Christopher Gilliard via bitcoin-dev a écrit :
>
> I have written up a proposed BIP. It has to do with Signature formats when
> using Bitcoin Private keys. It is here:
> https://github.com/cgilliard/BIP/blob/master/README.md
>
> This BIP was written up as suggested in this github issue:
> https://github.com/bitcoin/bitcoin/issues/10542
>
> Note that the proposal is inline with the implementation that Trezor
> implemented in the above issue.
>
> Any feedback would be appreciated. Please let me know what the steps are
> with regards to getting a BIP number assigned or any other process steps
> required.
>
> Regards,
> Chris
>
> _______________________________________________
> bitcoin-dev mailing listbitcoin-dev at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
> --
> Move your coins by yourself (browser version): https://peersm.com/wallet
> 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 part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190218/c16867ac/attachment-0001.html>;
Christopher Gilliard [ARCHIVE] /
npub1qm…0hwnt
2023-06-07 20:16:30
in reply to nevent1q…wu0z
Author Public Key
npub1qmsejphez6np2my9fu40kj9en68d5fa3s7ap4ul7eh9aeuljusgs50hwntPublished at
2023-06-07 20:16:30Event JSON
{
"id": "ec9743603996a2dc913bf8241a96f7efdcea497895480871eac8eea21b799ab3",
"pubkey": "06e19906f916a6156c854f2afb48b99e8eda27b187ba1af3fecdcbdcf3f2e411",
"created_at": 1686161790,
"kind": 1,
"tags": [
[
"e",
"90a0c763220b1b7816fac44840b029ebb7addf90dbc79e7c5fd8420c02e92ed9",
"",
"root"
],
[
"e",
"e7356f22bad060fdbd3a0771182cfe828ae125f291dcf4fe48b6f7f4f1d24dc6",
"",
"reply"
],
[
"p",
"a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df"
]
],
"content": "📅 Original date posted:2019-02-18\n📝 Original message:The proposal includes actual code that does verification, but I didn't\ninclude code for signing. I thought it could be inferred, but I could at\nleast include a description of how to sign. I am not sure exactly what part\nyou are referring to by \"keys speech\", but the signatures are done by ECDSA\nkeys so it's hard to not include anything about keys even though that's not\nthe main topic. The \"Background on ECDSA keys\" section was mainly meant to\ngive background about what kind of keys Bitcoin uses, for people who\nalready know that they can easily skip this section so I would probably\nthink it's best just to leave in. Maybe it should be at the end as an\naddendum though. Yes, I did not invent any of this, I'm just documenting\nwhat people actually seem to do because I had to verify signatures as part\nof a project I'm working on. I would have liked to have had this document\nwhen I started the project so I thought it might be useful to others since\nas far as I can tell this was not specified anywhere. The reason for\nincluding this data in the header is the same that compressed/uncompressed\nis included in the header so that you know which type of key the signature\nis from and you don't have to try all options to see if any matches. This\nis why Trezor did that way and why I documented it. I'm sure there are\nother ways to do this, but since this is out there in the field being used\nand is a reasonable solution, I thought I'd write it up.\n\nOn Mon, Feb 18, 2019 at 2:59 PM Aymeric Vitte \u003cvitteaymeric at gmail.com\u003e\nwrote:\n\n\u003e Then, since you wrote this proposal, maybe you should add the very precise\n\u003e description of the signing/verification process since it is documented\n\u003e nowhere\n\u003e\n\u003e I don't get the use of the speech regarding keys while it should focus on\n\u003e signatures which are summarized in a vague sentence inspired by your ref\n\u003e [2] with a not very logical link to the next paragraph stating that r,s\n\u003e should be 32B and the whole thing 65B with a header of 1B, you did not\n\u003e invent it, that's probably the rule, not sure where it is specified again\n\u003e and for what purpose, the header seems completely of no use especially when\n\u003e you extend to segwit/bech32 since you just have to check that related\n\u003e compressed key matches\n\u003e Le 17/02/2019 à 15:14, Christopher Gilliard via bitcoin-dev a écrit :\n\u003e\n\u003e I have written up a proposed BIP. It has to do with Signature formats when\n\u003e using Bitcoin Private keys. It is here:\n\u003e https://github.com/cgilliard/BIP/blob/master/README.md\n\u003e\n\u003e This BIP was written up as suggested in this github issue:\n\u003e https://github.com/bitcoin/bitcoin/issues/10542\n\u003e\n\u003e Note that the proposal is inline with the implementation that Trezor\n\u003e implemented in the above issue.\n\u003e\n\u003e Any feedback would be appreciated. Please let me know what the steps are\n\u003e with regards to getting a BIP number assigned or any other process steps\n\u003e required.\n\u003e\n\u003e Regards,\n\u003e Chris\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing listbitcoin-dev at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e --\n\u003e Move your coins by yourself (browser version): https://peersm.com/wallet\n\u003e Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions\n\u003e Zcash wallets made simple: https://github.com/Ayms/zcash-wallets\n\u003e Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets\n\u003e Get the torrent dynamic blocklist: http://peersm.com/getblocklist\n\u003e Check the 10 M passwords list: http://peersm.com/findmyass\n\u003e Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org\n\u003e Peersm : http://www.peersm.com\n\u003e torrent-live: https://github.com/Ayms/torrent-live\n\u003e node-Tor : https://www.github.com/Ayms/node-Tor\n\u003e GitHub : https://www.github.com/Ayms\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190218/c16867ac/attachment-0001.html\u003e",
"sig": "f154e510d040a65fe170cbbadcb85dfde1274d6e84879ee028940043abf5dd0149422126806c6aecdcd981f26dbf41219ed653daa9616c51350be2d30611a5ad"
}