đź“… Original date posted:2019-02-18
đź“ť Original message: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 list
> bitcoin-dev at lists.linuxfoundation.org
> https://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/971a925a/attachment-0001.html>;
Aymeric Vitte [ARCHIVE] /
npub15f…g5grz
2023-06-07 20:16:30
in reply to nevent1q…nqzk
Author Public Key
npub15fc36esk6dy2x4ptk2ner209rl9u0d736gr99edtu9knu9uny80s4g5grzPublished at
2023-06-07 20:16:30Event JSON
{
"id": "e7356f22bad060fdbd3a0771182cfe828ae125f291dcf4fe48b6f7f4f1d24dc6",
"pubkey": "a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df",
"created_at": 1686161790,
"kind": 1,
"tags": [
[
"e",
"90a0c763220b1b7816fac44840b029ebb7addf90dbc79e7c5fd8420c02e92ed9",
"",
"root"
],
[
"e",
"9e01bb5b19a7cbc23bbf9e3cabfec5be40ffa39c7a2de7cbd15f095026055a27",
"",
"reply"
],
[
"p",
"75f52ac24ef4f05f275587ff218a69c9bb9b3056ac1e2069f918970b6d7d430d"
]
],
"content": "📅 Original date posted:2019-02-18\n📝 Original message:Then, since you wrote this proposal, maybe you should add the very\nprecise description of the signing/verification process since it is\ndocumented nowhere\n\nI don't get the use of the speech regarding keys while it should focus\non signatures which are summarized in a vague sentence inspired by your\nref [2] with a not very logical link to the next paragraph stating that\nr,s should be 32B and the whole thing 65B with a header of 1B, you did\nnot invent it, that's probably the rule, not sure where it is specified\nagain and for what purpose, the header seems completely of no use\nespecially when you extend to segwit/bech32 since you just have to check\nthat related compressed key matches\n\nLe 17/02/2019 à 15:14, Christopher Gilliard via bitcoin-dev a écrit :\n\u003e I have written up a proposed BIP. It has to do with Signature formats\n\u003e when using Bitcoin Private keys. It is\n\u003e here: https://github.com/cgilliard/BIP/blob/master/README.md\n\u003e\n\u003e This BIP was written up as suggested in this github\n\u003e issue: 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\n\u003e are with regards to getting a BIP number assigned or any other process\n\u003e steps required.\n\u003e\n\u003e Regards,\n\u003e Chris\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\n-- \nMove your coins by yourself (browser version): https://peersm.com/wallet\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\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190218/971a925a/attachment-0001.html\u003e",
"sig": "94333b4eb929e7ddb2554c81a9c29a6c327bc65c8279554e50986ae6cb04642ac7074cc6a693232cdd1f36a530a69460e5ab1ff812eddd5df7e3a3b086eebcad"
}