{"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:2014-03-20\n📝 Original message:Encoding entire payment requests into qrcodes is definitely not the way to\ngo. They can already be large when signed and we're just at the start of\nadding features.\n\nFinishing off and standardising the bluetooth support is the way to go\n(r=bt:mac). Andreas' app already has some support for this I believe, so\nAlex you could prototype with that, but we need to:\n\n1) Add an encryption/auth layer on top, because it runs over RFCOMM\nsockets. The authentication would require proof of owning the Bitcoin key\nthat's in the address part of the URI (which is needed for backwards compat\nanyway).\n\n2) Write a BIP for it and make sure it's interoperable\n\nFor the auth layer we could either use SSL and then just ignore the server\ncertificate and require signing of the session public key with the Bitcoin\nkey, which should be easy to code up but is rather heavy on the air, or\nroll a custom lightweight thing where we just do a basic ECDH, with the\nservers key being the same as the address key. But rolling such protocols\nis subtle and I guess it'd need to be reviewed by people familiar with such\nthings.\n\nThis feels like a good opportunity to grow the community - perhaps we can\nfind a volunteer in the forums who enjoys crypto.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140320/ad3cb0fd/attachment.html\u003e"}