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