{"type":"rich","version":"1.0","author_name":"npub1j8mfekhmgtne6ptzxptudrcpwd6wtyxk64qdn3swy2nv46zuledskwpach","author_url":"https://nostr.ae/npub1j8mfekhmgtne6ptzxptudrcpwd6wtyxk64qdn3swy2nv46zuledskwpach","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-03-12\n📝 Original message:When Jim and I were selecting which combination of HD wallet structures to\nsupport we noted the following:\n\n* BIP39 is a good standard list to select from that mandates words that do\nnot look similar to each other, a certain spelling (no English US/UK\nconfusion) and possible foreign language variants provided by experts later\n* BIP32 (m/0h/0/0) and BIP44 (m/44h/0h/0h/0/0) allow for maximum\ncompatibility with other wallets\n* including a date in the \"wallet words\" themselves is open to spoofing\nsince the generator cannot be sure the date is correct (local time drift,\nprovided externally by untrusted third party etc)\n* a timestamp as optional external metadata is useful to reduce sync times\nin SPV\n* our experience verified that users will very often enter a timestamp\nincorrectly (locale, fat fingers, bad memory etc) so we opted for \"number\nof days elapsed since Bitcoin genesis block with a modulo 97 checksum\nappended\" (e.g. 1850/07) to mitigate this\n* if a user has no timestamp then blank is the only alternative (no\nguessing) which is interpreted as \"earliest possible BIP32 date\"\n* if restoring the user has to select where the \"wallet words\" came from\n(e.g. MultiBit HD, Trezor, Mycelium etc)\n\nUsers will naturally assume that they can type their \"wallet words\" (a more\nmainstream-friendly term than \"seed phrase\") into any wallet and with a bit\nof fiddling about get their bitcoins back. As wallet developers it is\nwithin our capability to make that happen and I think we're quite close\nalready.\n\nOn 12 March 2015 at 16:47, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\n\u003e b) \"Creation date\" is just a short-term hack.\n\u003e\u003e\n\u003e\n\u003e I agree, but we need things to be easy in the short term as well as the\n\u003e long term :)\n\u003e\n\u003e The long term solution is clearly to have the 12 word seed be an\n\u003e encryption key for a wallet backup with all associated metadata. We're\n\u003e heading in that direction one step at a time. Unfortunately it will take\n\u003e time for wallets to start working this way, and all the pieces to fall into\n\u003e place. Restoring from the block chain will be a semi regular operation for\n\u003e users until then.\n\u003e\n\u003e WRT version number I have no real strong feelings about this. But\n\u003e representing short pieces of binary data as words is so convenient, it\n\u003e seems likely that it could be similar to addresses: people find other uses\n\u003e for this mechanism beyond just storing a raw private key. Bitcoin addresses\n\u003e have versions and that's proven to be useful several times, even though in\n\u003e theory an address is \"just\" a hash of a pubkey.\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Dive into the World of Parallel Programming The Go Parallel Website,\n\u003e sponsored\n\u003e by Intel and developed in partnership with Slashdot Media, is your hub for\n\u003e all\n\u003e things parallel software development, from weekly thought leadership blogs\n\u003e 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\n\n\n-- \nBitcoin Solutions Ltd provides bespoke software and consultancy. Find us at\nbitcoin-solutions.co.uk.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150312/cb5f3188/attachment.html\u003e"}