📅 Original date posted:2021-03-22 📝 Original message:yes that would be fine. ...

Erik Aronesty [ARCHIVE] /

npub1y22…taj0

2023-06-07 18:30:59

in reply to nevent1q…0h6k

📅 Original date posted:2021-03-22
📝 Original message:yes that would be fine. not sure what your objection to sha3 is tho
(more provably secure) - i guess sticking with bitcoin-lib stuff tho.

On Fri, Mar 19, 2021 at 10:08 PM Arik Sosman <me at arik.io> wrote:
>
> Hi Erik,
>
> Would sha256-hmac(nonce, publicKeyPoint) still be a suitable/safe alternative without relying on sha3? That should at the very least eliminate length extension attacks.
>
> Best,
> Arik
>
> > On Mar 19, 2021, at 6:32 PM, Erik Aronesty via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
> >
> > use sha3-256. sha256 suffers from certain attacks (length extension,
> > for example) that could make your scheme vulnerable to leaking info,
> > depending on how you concatenate things, etc. better to choose
> > something where padding doesn't matter.
> >
> > On Fri, Mar 19, 2021 at 7:28 PM vjudeu via bitcoin-dev
> > <bitcoin-dev at lists.linuxfoundation.org> wrote:
> >>
> >> I recently found some interesting and simple HD wallet design here: https://bitcointalk.org/index.php?topic=5321992.0
> >> Could anyone see any flaws in such design or is it safe enough to implement it and use in practice?
> >> If I understand it correctly, it is just pure ECDSA and SHA-256, nothing else:
> >>
> >> masterPublicKey = masterPrivateKey * G
> >> masterChildPublicKey = masterPublicKey + ( SHA-256( masterPublicKey || nonce ) mod n ) * G
> >> masterChildPrivateKey = masterPrivateKey + ( SHA-256( masterPublicKey || nonce ) mod n )
> >>
> >> Also, it has some nice properties, like all keys starting with 02 prefix and allows potentially unlimited custom derivation path by using 256-bit nonce.
> >> _______________________________________________
> >> bitcoin-dev mailing list
> >> bitcoin-dev at lists.linuxfoundation.org
> >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

Author Public Key

npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0

Show more details

Published at

2023-06-07 18:30:59

Kind type

1 Short Text Note

Event JSON

{ "id": "ddbe586378e1474291a35bf9b8c9a81c79c172e4b04890ace9a7e5fb758ecd64", "pubkey": "22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa", "created_at": 1686162659, "kind": 1, "tags": [ [ "e", "69708790841c33eb579cf900d3977a71d1f4f272db7c13d1670b70f61a12c1cb", "", "root" ], [ "e", "f29fa0d18cf6676426c01205669388f5607d806d403762c46f1fc88e041ad6e6", "", "reply" ], [ "p", "6cb2abb6615d9f6aa0741afd161306be3c6b5a1624a2a0eb6865cdad3bebffb4" ] ], "content": "📅 Original date posted:2021-03-22\n📝 Original message:yes that would be fine. not sure what your objection to sha3 is tho\n(more provably secure) - i guess sticking with bitcoin-lib stuff tho.\n\nOn Fri, Mar 19, 2021 at 10:08 PM Arik Sosman \u003cme at arik.io\u003e wrote:\n\u003e\n\u003e Hi Erik,\n\u003e\n\u003e Would sha256-hmac(nonce, publicKeyPoint) still be a suitable/safe alternative without relying on sha3? That should at the very least eliminate length extension attacks.\n\u003e\n\u003e Best,\n\u003e Arik\n\u003e\n\u003e \u003e On Mar 19, 2021, at 6:32 PM, Erik Aronesty via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\n\u003e \u003e use sha3-256. sha256 suffers from certain attacks (length extension,\n\u003e \u003e for example) that could make your scheme vulnerable to leaking info,\n\u003e \u003e depending on how you concatenate things, etc. better to choose\n\u003e \u003e something where padding doesn't matter.\n\u003e \u003e\n\u003e \u003e On Fri, Mar 19, 2021 at 7:28 PM vjudeu via bitcoin-dev\n\u003e \u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\u003e\n\u003e \u003e\u003e I recently found some interesting and simple HD wallet design here: https://bitcointalk.org/index.php?topic=5321992.0\n\u003e \u003e\u003e Could anyone see any flaws in such design or is it safe enough to implement it and use in practice?\n\u003e \u003e\u003e If I understand it correctly, it is just pure ECDSA and SHA-256, nothing else:\n\u003e \u003e\u003e\n\u003e \u003e\u003e masterPublicKey = masterPrivateKey * G\n\u003e \u003e\u003e masterChildPublicKey = masterPublicKey + ( SHA-256( masterPublicKey || nonce ) mod n ) * G\n\u003e \u003e\u003e masterChildPrivateKey = masterPrivateKey + ( SHA-256( masterPublicKey || nonce ) mod n )\n\u003e \u003e\u003e\n\u003e \u003e\u003e Also, it has some nice properties, like all keys starting with 02 prefix and allows potentially unlimited custom derivation path by using 256-bit nonce.\n\u003e \u003e\u003e _______________________________________________\n\u003e \u003e\u003e bitcoin-dev mailing list\n\u003e \u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e", "sig": "69206bc928cfc77f56526c9a8631340abc33fdb534bffe05fad0361606e33c0356f4e24ce602535d5a89eee15903888ae5f2ed0f49e80258ffb492ecc94a5a22" }