<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-03-11&#xA;📝 Original message:Sigh. The wallet words system is turning into kind of a mess.&#xA;&#xA;I thought the word list is in fact not a fixed part of the spec, because&#xA;the entropy is a hash of the words. But perhaps I&#39;m misunderstanding&#xA;something.&#xA;&#xA;The main problem regular SPV wallets have with BIP39 is that there is no&#xA;birth time included in the data. Therefore we must ask users to write down&#xA;a timestamp as well, so we know where to start rescanning the chain. It&#xA;sounds like the Electrum version doesn&#39;t fix this, so now we have at least&#xA;FIVE incompatible results from a 12 word list:&#xA;&#xA;   - Electrum v2 with a version number but no date&#xA;   - myTREZOR with no version and no date and BIP44 key derivation. Some&#xA;   seeds I believe are now being generated with 24 words instead of 12.&#xA;   - MultiBit HD with no version and a date in a custom form that creates&#xA;   non-date-like codes you are expected to write down. I think BIP32 and BIP44&#xA;   are both supported (sorta).&#xA;   - GreenAddress with no version, no date and BIP32&#xA;   - Other bitcoinj based wallets, with no version and a date written down&#xA;   in normal human form, BIP32 only.&#xA;&#xA;I really hope we can recover from this somehow because otherwise all&#xA;wallets will have to provide the user with a complicated matrix of&#xA;possibilities and software combinations, and in practice many won&#39;t bother&#xA;so these word combinations will actually end up being wallet specific for&#xA;no particularly good reason, just very minor details like the presence or&#xA;absence of single fields.&#xA;&#xA;It feels like we somehow fell flat on our faces just before the finishing&#xA;line. This is deeply unfortunate. Compatibility and UX consistency is&#xA;important!&#xA;&#xA;Currently, I don&#39;t have any bright ideas for how to get everyone back onto&#xA;the same page with a fully compatible system that is acceptable to all. If&#xA;anyone else has suggestions, I&#39;m all ears.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150311/6feebf89/attachment.html&gt;</html></oembed>