📅 Original date posted:2014-03-21
📝 Original message:On 03/20/2014 01:12 PM, Adam Back wrote:
> Whats a sensible limit on practical/convenient QR code size?
Technically 3 KB. In my experience codes above 1.5 KB become impossible
to scan (ZXing scanner, 3 years ago). You will want to stay below 500
bytes for convenient scanning. That said, I'm convinced there is a lot
of room for scanning improvements.
> How much of the payment protocol message size comes from use of x509?
As said in the OP, a minimal PR uses 50 bytes. X.509 seems to put about
4000 bytes on top of that.
As you can see, we have quite some room for improvements to PR payload
(PaymentDetails). X.509 certification will probably not be possible via
QR, at least not until specialized CA's will issue space-efficient certs
(using ECDSA?).
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:14:22
in reply to nevent1q…2n63
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:14:22Event JSON
{
"id": "23f4d24bd1a20049bb704295daab9c333d680e249b59c51324a0a4750f78e171",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686150862,
"kind": 1,
"tags": [
[
"e",
"d70d8d12a406cb1c9a067111bb9c717b35fd85b951e12f89e562fccc2fad4277",
"",
"root"
],
[
"e",
"5d1c1a4b48684ccc2cb769dd2211325f9b8415dab54de704f5f79fd3bd274690",
"",
"reply"
],
[
"p",
"ac99e5ca3122fca258fbfcb6cb62d10d4dba423b3243251cbc0c4e0042656dec"
]
],
"content": "📅 Original date posted:2014-03-21\n📝 Original message:On 03/20/2014 01:12 PM, Adam Back wrote:\n\n\u003e Whats a sensible limit on practical/convenient QR code size?\n\nTechnically 3 KB. In my experience codes above 1.5 KB become impossible\nto scan (ZXing scanner, 3 years ago). You will want to stay below 500\nbytes for convenient scanning. That said, I'm convinced there is a lot\nof room for scanning improvements.\n\n\u003e How much of the payment protocol message size comes from use of x509?\n\nAs said in the OP, a minimal PR uses 50 bytes. X.509 seems to put about\n4000 bytes on top of that.\n\nAs you can see, we have quite some room for improvements to PR payload\n(PaymentDetails). X.509 certification will probably not be possible via\nQR, at least not until specialized CA's will issue space-efficient certs\n(using ECDSA?).",
"sig": "2f806df41fa0ce72547758aab69403a048f1992499765379dc983dd28e2f5678c0a761485ab26ce3cc325701659dc20edfe236606abb48ac8eed6a3aa8578c1f"
}