{"type":"rich","version":"1.0","author_name":"npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6","author_url":"https://nostr.ae/npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-03-12\n📝 Original message:On Wed, Mar 11, 2015 at 6:14 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\n\u003e\n\u003e    - Electrum v2 with a version number but no date\n\u003e    - myTREZOR with no version and no date and BIP44 key derivation. Some\n\u003e    seeds I believe are now being generated with 24 words instead of 12.\n\u003e    - MultiBit HD with no version and a date in a custom form that creates\n\u003e    non-date-like codes you are expected to write down. I think BIP32 and BIP44\n\u003e    are both supported (sorta).\n\u003e    - GreenAddress with no version, no date and BIP32\n\u003e    - Other bitcoinj based wallets, with no version and a date written\n\u003e    down in normal human form, BIP32 only.\n\u003e\n\u003e To my knowledge, myTREZOR, Multibit HD and GreenAddress uses BIP39, just\ndifferent scheme for key derivation (myTREZOR uses full BIP44, Multibit HD\nuses BIP44 with first account only and GreenAddress uses another scheme\nbecause it's multisig only wallet).\n\nI disagree with the need of some version \"magic flags\" or creation date\nstored in the mnemnonic, for those reasons:\n\na) If we fail in the way how mnemonic algo is defined, then some magic,\nextra version flag won't save our asses, because we'll fail in meaning of\nits meaning. Then it will be completely useless, as implementations cannot\nrely on it. I know Thomas was sound proponent of this solution, but he was\nunable to give any reasonable rules about who/how define meaning of version\nflag.\n\nb) \"Creation date\" is just a short-term hack. Considering that mnemonic\nwords are kind of cold storage (longterm storage), it *really* does not\nmake much difference in 2020, if your wallet has been created in 02/2014 or\n10/2016. If there's performance issue with scanning of the blockchain,\ncreation date don't save our asses. We need to find another solution, and\nas a bonus, we don't need users to know some weird numbers on top of\nmnemonic itself.\n\n\u003e From my interpretation of BIP39, wordlists DO NOT REQUIRE to be fixed\nbetween wallet providers. There is some recommendations regarding the\nwordlists to help with things such as predictive text, so mobile apps can\neasily predict the word being typed in after a few chars etc.\n\nExactly! After some community feedback, we changed BIP39 algo to be one-way\nonly, which means you can use *any* wordlist to create the mnemonic, and\nany other implementation can derive BIP32 root node even without knowing\nthat particular wordlist. Namely this has been changed because of\nconstructive criticism of ThomasV, and from discussion on the mailing list\nI had a feeling that we've found a consensus. I was *very* surprised that\nElectrum 2.0 started to use yet another algo \"just because\".\n\nShortly said, I think BIP39 does perfect job and there's no need to use\nanything else.\n\nCheers,\nMarek\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150312/318ad491/attachment.html\u003e"}