{"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-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150312/4e18a33f/attachment.html\u003e"}