{"type":"rich","version":"1.0","author_name":"npub1sv4psc5psjztuewa8xzcxrdsm743zl3lvje7ha36xp3da86hmpyqdjg7a4","author_url":"https://nostr.ae/npub1sv4psc5psjztuewa8xzcxrdsm743zl3lvje7ha36xp3da86hmpyqdjg7a4","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-22\n📝 Original message:The reason why client side certificates have never gained traction because\nit is a pain to safely store/backup secrets.\nIn bitcoinland we are forced to solve the problem of safely storing\nsecrets, and over the years we have come up with software and hardware\nsolutions to make this safer and easier to manage for ordinary people.\nSolving this is paramount to the success of Bitcoin, and nobody has solved\nit before on a grand scale.\n\nI see no reason for forcing end users to use two different mechanisms for\nsafely managing secrets.\n\nI agree that using a bitcoin address for authentication purposes might be\nconfusing and potentially linking your funds with your identity. So I am\nall for using something else than bitcoin addresses and bitcoin private\nkeys.\n\nWith bip32 we have finally agreed on a mechanism for generating a hierarchy\nof bitcoin private keys from a master seed. A similar approach can be used\nfor generating a parallel hierarchy for authentication purposes.\n\n- Jan\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140422/34e800f0/attachment.html\u003e"}