{"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:What I'm trying to achieve, is to have a very simple way of authenticating\nyourself with one Bitcoin address from your wallet.\nFor most of the people using Bitcoin, their wallet is on their phone.\n\nThe UX is clear and simple :\n1. click on \"connect with Bitcoin\" (the audience is normal people)\n2. flash the QRcode with your wallet (blockchain.info, mycelium, ...)\n3. accept the authentication request (same style than OpenID or Facebook\nconnect)\n4. user is autologged and identified by the chosen Bitcoin public address\n\nIt makes sense only if major wallets are supporting the protocol. If you\nneed to install a plugin or download a third party software, no one will do\nit.\nI see only benefits for the entire ecosystem, and if I'm working on such a\nproposition it is because I really need this feature.\n\nOf course, it can be done without a BIP, I just need to convince wallet\ndeveloppers one by one to implement the feature.\nBut I thought it was much better to start the \"official\" way, so all wallet\ncould easily find and implement the same authentication mechanism.\n\n\u003e  Bitcoin and website authentication are unrelated problems\n\nI respectfully disagree. Many services require your Bitcoin address, and to\ndo that they artificially request an email/password to store it.\nThis is not about authentication as an identity (as \"I'm Eric\nLarcheveque\"), but as in \"I'm proving to you that I control this address\".\n\nWithout such a standard protocol, you could never envision a pure Bitcoin\nphysical locker rental, or booking an hotel room via Bitcoin and opening\nthe door through the paying address.\n\nEric\n\n\n\nOn Fri, Apr 4, 2014 at 3:08 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\n\u003e This comes up every few months. I think the problem you are trying to\n\u003e solve is already solved by SSL client certificates, and if you want to help\n\u003e make them more widespread the programs you need to upgrade are web browsers\n\u003e and not Bitcoin wallets. There are certainly bits of infrastructure you\n\u003e could reuse here and there, like perhaps a TREZOR with a custom firmware\n\u003e extension for really advanced/keen users, but overall Bitcoin and website\n\u003e authentication are unrelated problems.\n\u003e\n\u003e\n\u003e On Fri, Apr 4, 2014 at 2:15 PM, Eric Larchevêque \u003celarch at gmail.com\u003e wrote:\n\u003e\n\u003e\u003e Hello,\n\u003e\u003e\n\u003e\u003e I've written a draft BIP description of an authentication protocol based\n\u003e\u003e on Bitcoin public address.\n\u003e\u003e\n\u003e\u003e By authentication we mean to prove to a service/application that we\n\u003e\u003e control a specific Bitcoin address by signing a challenge, and that all\n\u003e\u003e related data and settings may securely be linked to our session.\n\u003e\u003e\n\u003e\u003e The aim is to greatly facilitate sign ups and logins to services and\n\u003e\u003e applications, improving the Bitcoin ecosystem as a whole.\n\u003e\u003e\n\u003e\u003e https://github.com/bitid/bitid/blob/master/BIP_draft.md\n\u003e\u003e\n\u003e\u003e Demo website :\n\u003e\u003e http://bitid-demo.herokuapp.com/\n\u003e\u003e\n\u003e\u003e Classical password authentication is an insecure process that could be\n\u003e\u003e solved with public key cryptography. The problem is that it theoretically\n\u003e\u003e offloads a lot of complexity and responsibility on the user. Managing\n\u003e\u003e private keys securely is complex. However this complexity is already being\n\u003e\u003e addressed in the Bitcoin ecosystem. So doing public key authentication is\n\u003e\u003e practically a free lunch to bitcoiners.\n\u003e\u003e\n\u003e\u003e I've formatted the protocol description as a BIP because this is the only\n\u003e\u003e way to have all major wallets implementing it, and because it completely\n\u003e\u003e fits in my opinion the BIP \"process\" category.\n\u003e\u003e\n\u003e\u003e Please read it and let me know your thoughts and comments so we can\n\u003e\u003e improve on this draft.\n\u003e\u003e\n\u003e\u003e Eric Larcheveque\n\u003e\u003e elarch at gmail.com\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e\n\u003e\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140404/caca26c8/attachment.html\u003e"}