{"type":"rich","version":"1.0","author_name":"npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47","author_url":"https://nostr.ae/npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-03-12\n📝 Original message:Hi Andreas,\n\nI don't think it's a problem that BIP43 is tied to BIP32.\n\nWhat I don't like is that you have to explore branches of the derivation\ntree, in order to know if there is a wallet. As a result, it is not\npossible for the software to give a negative answer, like \"this wallet\nis empty\", because you do not know if you have explored all the possible\nderivations; a new one may have been added after the software was written.\n\nWith a version number, you can answer \"sorry this seed is not recognized\nby me\", and you do not need to be online to do that.\nIf you are online, you can answer \"this wallet is empty\" after exploring it.\n\n\n\n\nLe 11/03/2015 16:31, Andreas Schildbach a écrit :\n\u003e Thanks Thomas, for sharing your experience!\n\u003e \n\u003e I'd like know why you think it's a problem that BIP43 is tied to BIP32?\n\u003e I understand we all agreed at least on the BIP32-derivation spec\n\u003e (excluding the BIP32-hierarchy spec)?\n\u003e \n\u003e \n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Dive into the World of Parallel Programming The Go Parallel Website, sponsored\n\u003e by Intel and developed in partnership with Slashdot Media, is your hub for all\n\u003e things parallel software development, from weekly thought leadership blogs to\n\u003e news, videos, case studies, tutorials and more. Take a look and join the \n\u003e conversation now. http://goparallel.sourceforge.net/\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \n\u003e"}