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