{"type":"rich","version":"1.0","author_name":"npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6","author_url":"https://nostr.ae/npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-23\n📝 Original message:We do not want BIP64 to be incompatible with BIP32 in any way. BIP64 is\njust set of some recommendations for wallet developers how to browse bip32\ntree.\n\nModifying serialization format would break the compatibility.\n\nHowever we have our solution for storing wallet birth time, which is out of\nscope of BIP64, but we'll communicate it as soon as we'll write down that\nidea to some more specific format.\n\nMarek\n\n\nOn Wed, Apr 23, 2014 at 9:36 PM, Tamas Blummer \u003ctamas at bitsofproof.com\u003ewrote:\n\n\u003e Pieter suggested in IRC couple of months ago to append key birth to key\n\u003e serialization in xprv.... at unixtime format.\n\u003e\n\u003e What about picking this idea up in BIP64? It would greatly help the\n\u003e importing client.\n\u003e\n\u003e Regards,\n\u003e\n\u003e Tamas Blummer\n\u003e http://bitsofproof.com\n\u003e\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140423/db8776a4/attachment.html\u003e"}