<oembed><type>rich</type><version>1.0</version><author_name>npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6</author_name><author_url>https://nostr.ae/npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-04-23&#xA;📝 Original message:We do not want BIP64 to be incompatible with BIP32 in any way. BIP64 is&#xA;just set of some recommendations for wallet developers how to browse bip32&#xA;tree.&#xA;&#xA;Modifying serialization format would break the compatibility.&#xA;&#xA;However we have our solution for storing wallet birth time, which is out of&#xA;scope of BIP64, but we&#39;ll communicate it as soon as we&#39;ll write down that&#xA;idea to some more specific format.&#xA;&#xA;Marek&#xA;&#xA;&#xA;On Wed, Apr 23, 2014 at 9:36 PM, Tamas Blummer &lt;tamas at bitsofproof.com&gt;wrote:&#xA;&#xA;&gt; Pieter suggested in IRC couple of months ago to append key birth to key&#xA;&gt; serialization in xprv.... at unixtime format.&#xA;&gt;&#xA;&gt; What about picking this idea up in BIP64? It would greatly help the&#xA;&gt; importing client.&#xA;&gt;&#xA;&gt; Regards,&#xA;&gt;&#xA;&gt; Tamas Blummer&#xA;&gt; http://bitsofproof.com&#xA;&gt;&#xA;&gt;&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140423/db8776a4/attachment.html&gt;</html></oembed>