{"type":"rich","version":"1.0","author_name":"npub1ac86vemj7ce5z8jyxt39rna3tvwql6xd30ha3vxcd6esysp23d9qrlswfj","author_url":"https://nostr.ae/npub1ac86vemj7ce5z8jyxt39rna3tvwql6xd30ha3vxcd6esysp23d9qrlswfj","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-20\n📝 Original message:Whats a sensible limit on practical/convenient QR code size?\n\nHow much of the payment protocol message size comes from use of x509?\n\n(Just exploring what the options are).\n\nAdam\n\nOn Thu, Mar 20, 2014 at 11:36:09AM +0100, Mike Hearn wrote:\n\u003e   Encoding entire payment requests into qrcodes is definitely not the way\n\u003e   to go. They can already be large when signed and we're just at the\n\u003e   start of adding features.\n\u003e   Finishing off and standardising the bluetooth support is the way to go\n\u003e   (r=bt:mac). Andreas' app already has some support for this I believe,\n\u003e   so Alex you could prototype with that, but we need to:\n\u003e   1) Add an encryption/auth layer on top, because it runs over RFCOMM\n\u003e   sockets. The authentication would require proof of owning the Bitcoin\n\u003e   key that's in the address part of the URI (which is needed for\n\u003e   backwards compat anyway).\n\u003e   2) Write a BIP for it and make sure it's interoperable\n\u003e   For the auth layer we could either use SSL and then just ignore the\n\u003e   server certificate and require signing of the session public key with\n\u003e   the Bitcoin key, which should be easy to code up but is rather heavy on\n\u003e   the air, or roll a custom lightweight thing where we just do a basic\n\u003e   ECDH, with the servers key being the same as the address key. But\n\u003e   rolling such protocols is subtle and I guess it'd need to be reviewed\n\u003e   by people familiar with such things.\n\u003e   This feels like a good opportunity to grow the community - perhaps we\n\u003e   can find a volunteer in the forums who enjoys crypto."}