{"type":"rich","version":"1.0","author_name":"npub1pa6l5jatv92d4vzk566r58zjawpuu0we8nhrywfhp90f9948e0tsx3rxtp","author_url":"https://nostr.ae/npub1pa6l5jatv92d4vzk566r58zjawpuu0we8nhrywfhp90f9948e0tsx3rxtp","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-04\n📝 Original message:Hello,\n\nI've written a draft BIP description of an authentication protocol based on\nBitcoin public address.\n\nBy authentication we mean to prove to a service/application that we control\na specific Bitcoin address by signing a challenge, and that all related\ndata and settings may securely be linked to our session.\n\nThe aim is to greatly facilitate sign ups and logins to services and\napplications, improving the Bitcoin ecosystem as a whole.\n\nhttps://github.com/bitid/bitid/blob/master/BIP_draft.md\n\nDemo website :\nhttp://bitid-demo.herokuapp.com/\n\nClassical password authentication is an insecure process that could be\nsolved with public key cryptography. The problem is that it theoretically\noffloads a lot of complexity and responsibility on the user. Managing\nprivate keys securely is complex. However this complexity is already being\naddressed in the Bitcoin ecosystem. So doing public key authentication is\npractically a free lunch to bitcoiners.\n\nI've formatted the protocol description as a BIP because this is the only\nway to have all major wallets implementing it, and because it completely\nfits in my opinion the BIP \"process\" category.\n\nPlease read it and let me know your thoughts and comments so we can improve\non this draft.\n\nEric Larcheveque\nelarch at gmail.com\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140404/78771884/attachment.html\u003e"}