📅 Original date posted:2017-09-07 📝 Original message:Thanks for the proposal. ...

Jonas Schnelli [ARCHIVE] /

npub1nfr…dtxs

2023-06-07 18:05:33

in reply to nevent1q…faz6

📅 Original date posted:2017-09-07
📝 Original message:Thanks for the proposal.

Three points it could see as possible improvements:

1.
From what I know, the exact birthday in seconds doesn’t matter that much therefore it may be possible to just use 13 or 16bits to create a representation in week from 2009-01-09 00:00 UTC. 13bits would give you 157 years.
Always round down to the beginning of the week when the key was created.
But not sure if it’s worth to save ~two bytes for that.
Also not sure if the key-birthday in seconds could have a security or privacy implication (week maybe better).

2.
Would it make sense to have special depth bytes that directly implies it’s a BIP44 master key (and therefore avoid the bip32 path serialisation)? I know some „centralised“ table need to be available for that which may be not a good idea. But maybe the BIP could reserve a couple of depth-bytes (maybe 0xF0 to 0xFF) for predefined paths.

3.
Would adding a version bit make sense to allow future extensions?

/jonas

> Am 06.09.2017 um 15:29 schrieb Pavol Rusnak via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org>:
>
> The discussion about changing bip32 version bytes for SegWit got me
> thinking and I ended up with what I think is the best proposal:
>
> https://github.com/satoshilabs/slips/blob/master/slip-0032.md
>
> (It is hosted in SL repo for now, but if there is will, I would love to
> have this added to BIP repo as an extension to BIP32)
>
> Feel free to comment.
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170907/01c4fef5/attachment.sig>;

Author Public Key

npub1nfrrurat393mqymf3s26pujyn5vujlem3pzcukr5p9d4qpklngxq43dtxs

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 18:05:33

Kind type

1 Short Text Note

Event JSON

{ "id": "cbff85680ac742fcdd6f25d9e506f236e332a3f242fc2c3c0e895b9b25b70cc3", "pubkey": "9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c", "created_at": 1686161133, "kind": 1, "tags": [ [ "e", "8b6c82e376bdda93cb2f70dd4782d9cc9d7453907841b893f7135515b4f67b4c", "", "root" ], [ "e", "b6cc2965c6377753d32761cb2b2e199ba81abe681ae38185d72f579b422b54e4", "", "reply" ], [ "p", "7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05" ] ], "content": "📅 Original date posted:2017-09-07\n📝 Original message:Thanks for the proposal.\n\nThree points it could see as possible improvements:\n\n1.\nFrom what I know, the exact birthday in seconds doesn’t matter that much therefore it may be possible to just use 13 or 16bits to create a representation in week from 2009-01-09 00:00 UTC. 13bits would give you 157 years.\nAlways round down to the beginning of the week when the key was created.\nBut not sure if it’s worth to save ~two bytes for that.\nAlso not sure if the key-birthday in seconds could have a security or privacy implication (week maybe better).\n\n2.\nWould it make sense to have special depth bytes that directly implies it’s a BIP44 master key (and therefore avoid the bip32 path serialisation)? I know some „centralised“ table need to be available for that which may be not a good idea. But maybe the BIP could reserve a couple of depth-bytes (maybe 0xF0 to 0xFF) for predefined paths.\n\n3.\nWould adding a version bit make sense to allow future extensions?\n\n\n/jonas\n\n\n\u003e Am 06.09.2017 um 15:29 schrieb Pavol Rusnak via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e:\n\u003e \n\u003e The discussion about changing bip32 version bytes for SegWit got me\n\u003e thinking and I ended up with what I think is the best proposal:\n\u003e \n\u003e https://github.com/satoshilabs/slips/blob/master/slip-0032.md\n\u003e \n\u003e (It is hosted in SL repo for now, but if there is will, I would love to\n\u003e have this added to BIP repo as an extension to BIP32)\n\u003e \n\u003e Feel free to comment.\n\u003e \n\u003e --\n\u003e Best Regards / S pozdravom,\n\u003e \n\u003e Pavol \"stick\" Rusnak\n\u003e CTO, SatoshiLabs\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-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: Message signed with OpenPGP\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170907/01c4fef5/attachment.sig\u003e", "sig": "ddc20682719e0df9b5c964ad87778c47a9ad7bc492d517acdb86265beb639239d18dbae6cf0222b450cd63a99264a4a213175a62380901d39b49d133d1cb8f97" }