{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-12-13\n🗒️ Summary of this message: A proposal for a Bitcoin payment system using HTTPS requests for public keys instead of fixed addresses, which can expose private data.\n📝 Original message:\u003e\n\u003e I was in brmlab and wanted to pay 1 BTC for a Club Mate. They had on the\n\u003e wall a picture of their QR code and a bitcoin address. I don't own a mobile\n\u003e phone so the QR code is\n\u003e useless.\n\n\nFixed addresses like that are a temporary thing during Bitcoins maturation\nperiod. They lead to merchants exposing data they probably don't realize\nthey're exposing, like their income, which is basically unacceptable for\nany payment system.\n\nThere's no point trying to optimize a case where:\n\n1) You are in the minority (no phone?)\n2) The \"perfect experience\" leaks private data in such a way that would be\ndeemed a gross security breach by any serious payment processor.\n\nOK, some thoughts on the general proposal, from the POV of what it'd take\nfor a large deployment, like for every Gmail or every Facebook user. In\nterms of ease of implementation it is ordered HTTPS/HTTP then DNS trailing\nby a large margin. Big sites, even small sites, typically have high-speed\nload balancing and demuxing already implemented for HTTP[S] and it's\nusually easy to add new endpoints. The same is *not* true of DNS, and\nwhilst coding up a custom DNS server is possible it's definitely a worse\nfit.\n\nFirstBits seems out of the question for the same privacy reasons as given\nabove. No banking system worth its salt would let everyone look up other\npeoples income.\n\nThe simplest approach would be to request a full public key with an HTTPS\nrequest like\n\n   foo at domain -\u003e\nhttps://domain/_bitcoin/getnewkey?user=foo\u0026label=Payment%20from%20Bob\n\nIf you then want to turn the resulting public key into an address before\ncreating a transaction you can obviously do that.\n\nBTW the BIP is pretty hard to read. Your spec for the HTTPS proposal is a\nbig pile of source code. I think it's the same as above, but it's hard to\ntell without more effort.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111213/f32e484c/attachment.html\u003e"}