{"type":"rich","version":"1.0","author_name":"npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0","author_url":"https://nostr.ae/npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2021-03-19\n📝 Original message:use sha3-256.  sha256 suffers from certain attacks (length extension,\nfor example) that could make your scheme vulnerable to leaking info,\ndepending on how you concatenate things, etc.  better to choose\nsomething where padding doesn't matter.\n\nOn Fri, Mar 19, 2021 at 7:28 PM vjudeu via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e I recently found some interesting and simple HD wallet design here: https://bitcointalk.org/index.php?topic=5321992.0\n\u003e Could anyone see any flaws in such design or is it safe enough to implement it and use in practice?\n\u003e If I understand it correctly, it is just pure ECDSA and SHA-256, nothing else:\n\u003e\n\u003e masterPublicKey = masterPrivateKey * G\n\u003e masterChildPublicKey = masterPublicKey + ( SHA-256( masterPublicKey || nonce ) mod n ) * G\n\u003e masterChildPrivateKey = masterPrivateKey + ( SHA-256( masterPublicKey || nonce ) mod n )\n\u003e\n\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 _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"}