On 03/12/2014 04:45 PM, Jean-Paul Kogelman wrote: > Yes I am. There are some differences between BIP 39 and my proposal though. > > - BIP 39 offers an easy list of words, no gnarly string of case sensitive > letters and numbers.
Which is better IMO. I can't imagine anyone writing down a long Base58 encoded string. > - BIP 39 only offers one fixed length of entropy, always 12 words, no option > to increase or decrease the length. Not true, BIP39 supports 12/18/24 words (= 128/192/256 bits of entropy). > - BIP 39 doesn't have a genesis date field, so no optimization during > blockchain rescan. This is nice addition, indeed. But we needed to limit the data as possible in order not to increase the number of words needed to be noted down. > - BIP 39 doesn't have password typo detection. No easy way to recover a > password if you know most of it. It has a detection. Not correction though. > - BIP 39 does not have a user selectable KDF, only 2048 round > PBKDF2-HMAC-SHA512. > - BIP 39 can't outsource the KDF computation to a 3rd party. True, but having one or two solid options are better than having gazillions of possible options. > - BIP 39 wallet implementors can use their own word lists, breaking cross > wallet compatibility. True, but they are encouraged to use the list provided. Possibility to outsource KDF outside of your "standard" breaks much more compatibility than this. -- Best Regards / S pozdravom, Pavol Rusnak <st...@gk2.sk> ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
