<oembed><type>rich</type><version>1.0</version><author_name>npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47</author_name><author_url>https://nostr.ae/npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-03-27&#xA;📝 Original message:Le 27/03/2014 13:49, Mike Hearn a écrit :&#xA;&gt; Ah, BIP32 allows for a range of entropy sizes and it so happens that&#xA;&gt; they picked 256 bits instead of 128 bits.&#xA;&gt;&#xA;&gt; I&#39;d have thought that there is a right answer for this. 2^128 should not&#xA;&gt; be brute forceable, and longer sizes have a cost in terms of making the&#xA;&gt; seeds harder to write down on paper. So should this be a degree of freedom?&#xA;&gt;&#xA;&#xA;&#xA;Here is what I understand:&#xA;&#xA;2^128 iterations is not brute forcable today, and will not be for the &#xA;foreseeable future.&#xA;&#xA;An EC pubkey of length n can be forced in approximately 2^(n/2) &#xA;iterations (see http://ecc-challenge.info/) Thus, Bitcoin pubkeys, which &#xA;are 256 bits, would require 2^128 iterations. This is why unused &#xA;addresses (160 bits hash) are better protected than already used ones.&#xA;&#xA;However, people tend to believe that a public key of size n requires 2^n &#xA;iterations. This belief might have been spread by this popular image:&#xA;https://bitcointalk.org/index.php?topic=508880.msg5616146#msg5616146</html></oembed>