<oembed><type>rich</type><version>1.0</version><author_name>npub14fwd2yh320mh4ge46ute8ukdyx2kjxy2ak4a05prjwrtzlmh9rvq8hksaj</author_name><author_url>https://nostr.ae/npub14fwd2yh320mh4ge46ute8ukdyx2kjxy2ak4a05prjwrtzlmh9rvq8hksaj</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-03-11&#xA;📝 Original message:i guess you look at the glass half full :)&#xA;even though what you say is true, we should aim for wallets not to&#xA;require those instructions, by standardizing these things in BIPs.&#xA;let&#39;s hope bitcoin doesn&#39;t fail in standards as our industries have in&#xA;the past...&#xA;&#xA;2015-03-11 19:04 GMT+00:00 Jim &lt;jim618 at fastmail.co.uk&gt;:&#xA;&gt; The wallet words system isn&#39;t perfect for sure but it does help the user in two main ways:&#xA;&gt; 1) Assuming wallet devs ensure forward compatibility for _their_ wallet the user knows they can recover their bitcoins using the same wallet software in case of a Bad Thing Happening.&#xA;&gt; 2) To an imperfect degree, they can transfer/ recover their bitcoins that are stored in Wallet X into Wallet Y. We need to give them guidance on how to do this.&#xA;&gt;&#xA;&gt; I think it is up to each wallet team to explain to their users clearly how they can do this in their help. It&#39;s only good manners to show your guests where the fire exits are.&#xA;&gt;&#xA;&gt; It can be a simple help page saying:&#xA;&gt; &#34;If you want to transfer your bitcoin out of MultiBit HD to Lighthouse, do this, this and this.&#xA;&gt; If you want to use the Trezor wallet you created in MultiBit HD on myTrezor.com, do this, this and this.&#34;&#xA;&gt;&#xA;&gt; That way users have clear instructions on how to recover their bitcoins.&#xA;&gt; Users don&#39;t care about BIP this or BIP that but they REALLY DO CARE about keeping their bitcoins.&#xA;&gt;&#xA;&gt; --&#xA;&gt; http://bitcoin-solutions.co.uk&#xA;&gt;&#xA;&gt; On Wed, Mar 11, 2015, at 05:14 PM, Mike Hearn wrote:&#xA;&gt;&gt; Sigh. The wallet words system is turning into kind of a mess.&#xA;&gt;&gt;&#xA;&gt;&gt; I thought the word list is in fact not a fixed part of the spec, because&#xA;&gt;&gt; the entropy is a hash of the words. But perhaps I&#39;m misunderstanding&#xA;&gt;&gt; something.&#xA;&gt;&gt;&#xA;&gt;&gt; The main problem regular SPV wallets have with BIP39 is that there is no&#xA;&gt;&gt; birth time included in the data. Therefore we must ask users to write down&#xA;&gt;&gt; a timestamp as well, so we know where to start rescanning the chain. It&#xA;&gt;&gt; sounds like the Electrum version doesn&#39;t fix this, so now we have at least&#xA;&gt;&gt; FIVE incompatible results from a 12 word list:&#xA;&gt;&gt;&#xA;&gt;&gt;    - Electrum v2 with a version number but no date&#xA;&gt;&gt;    - myTREZOR with no version and no date and BIP44 key derivation. Some&#xA;&gt;&gt;    seeds I believe are now being generated with 24 words instead of 12.&#xA;&gt;&gt;    - MultiBit HD with no version and a date in a custom form that creates&#xA;&gt;&gt;    non-date-like codes you are expected to write down. I think BIP32 and BIP44&#xA;&gt;&gt;    are both supported (sorta).&#xA;&gt;&gt;    - GreenAddress with no version, no date and BIP32&#xA;&gt;&gt;    - Other bitcoinj based wallets, with no version and a date written down&#xA;&gt;&gt;    in normal human form, BIP32 only.&#xA;&gt;&gt;&#xA;&gt;&gt; I really hope we can recover from this somehow because otherwise all&#xA;&gt;&gt; wallets will have to provide the user with a complicated matrix of&#xA;&gt;&gt; possibilities and software combinations, and in practice many won&#39;t bother&#xA;&gt;&gt; so these word combinations will actually end up being wallet specific for&#xA;&gt;&gt; no particularly good reason, just very minor details like the presence or&#xA;&gt;&gt; absence of single fields.&#xA;&gt;&gt;&#xA;&gt;&gt; It feels like we somehow fell flat on our faces just before the finishing&#xA;&gt;&gt; line. This is deeply unfortunate. Compatibility and UX consistency is&#xA;&gt;&gt; important!&#xA;&gt;&gt;&#xA;&gt;&gt; Currently, I don&#39;t have any bright ideas for how to get everyone back onto&#xA;&gt;&gt; the same page with a fully compatible system that is acceptable to all. If&#xA;&gt;&gt; anyone else has suggestions, I&#39;m all ears.&#xA;&gt;&gt; ------------------------------------------------------------------------------&#xA;&gt;&gt; Dive into the World of Parallel Programming The Go Parallel Website, sponsored&#xA;&gt;&gt; by Intel and developed in partnership with Slashdot Media, is your hub for all&#xA;&gt;&gt; things parallel software development, from weekly thought leadership blogs to&#xA;&gt;&gt; news, videos, case studies, tutorials and more. Take a look and join the&#xA;&gt;&gt; conversation now. http://goparallel.sourceforge.net/&#xA;&gt;&gt; _______________________________________________&#xA;&gt;&gt; Bitcoin-development mailing list&#xA;&gt;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development&#xA;&gt;&#xA;&gt; ------------------------------------------------------------------------------&#xA;&gt; Dive into the World of Parallel Programming The Go Parallel Website, sponsored&#xA;&gt; by Intel and developed in partnership with Slashdot Media, is your hub for all&#xA;&gt; things parallel software development, from weekly thought leadership blogs to&#xA;&gt; news, videos, case studies, tutorials and more. Take a look and join the&#xA;&gt; conversation now. http://goparallel.sourceforge.net/&#xA;&gt; _______________________________________________&#xA;&gt; Bitcoin-development mailing list&#xA;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development</html></oembed>