📅 Original date posted:2013-09-25
📝 Original message:BitPay experimented with QR codes in low light, restaurant and other
conditions. QR codes become difficult to use even at 100 chars.
On the merchant side, we prefer a short URL that speaks payment
protocol if visited via bitcoin client, but will gracefully work if
scanned by a phone with zero bitcoin support -- you will simply be
redirected to a BitPay invoice page for a normal browser.
On Wed, Sep 25, 2013 at 7:59 AM, Andreas Schildbach
<andreas at schildbach.de> wrote:
> On 09/25/2013 01:45 PM, Mike Hearn wrote:
>
>> OK, it might fit if you don't use any of the features the protocol
>> provides :)
>
> Now you're dver-dramaticing (-:
>
> I'm just skipping one feature which I think is useless for QR codes
> scanned in person.
>
>> You can try it here:
>
> Thanks. A typical request would be around 60 bytes, which should produce
> an URL with around 100 chars. That should be fine for scanning, but I
> will experiment.
>
>> If you're thinking about governments and so on subverting CA's, then
>> there is a plan for handling that (outside the Bitcoin world) called
>> certificate transparency which is being implemented now.
>
> Good to hear. Let's see if it gets momentum.
>
>> Now when you are getting a QR code from the web, it's already being
>> served over HTTPS. So if you're up against an attacker who can break a
>> CA in order to steal your money, then you already lose, the QRcode
>> itself as MITMd.
>
> Sure. I was talking about QR codes scanned in person.
>
>> In the Bluetooth case we might have to keep the address around and use
>> it to do ECDHE or something like that.
>
> Yeah, will look at that as soon as we're implementing the payment
> protocol fully.
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 17:06:59
in reply to nevent1q…vssk
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Published at
2023-06-07 17:06:59Event JSON
{
"id": "1da6c27512ede494c0483167d59d3033b3e4308eeeb2cf7ecd56571e26d779fd",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686150419,
"kind": 1,
"tags": [
[
"e",
"a751be3c813f9be7c191d199bd218d957841ef330cc8bf258e75cbaf91bae46f",
"",
"root"
],
[
"e",
"5d56b8c3503bde4769dc770f52883e1075af2afe2c82ae1ae7c4cfae57b2ce4c",
"",
"reply"
],
[
"p",
"3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc"
]
],
"content": "📅 Original date posted:2013-09-25\n📝 Original message:BitPay experimented with QR codes in low light, restaurant and other\nconditions. QR codes become difficult to use even at 100 chars.\n\nOn the merchant side, we prefer a short URL that speaks payment\nprotocol if visited via bitcoin client, but will gracefully work if\nscanned by a phone with zero bitcoin support -- you will simply be\nredirected to a BitPay invoice page for a normal browser.\n\n\n\nOn Wed, Sep 25, 2013 at 7:59 AM, Andreas Schildbach\n\u003candreas at schildbach.de\u003e wrote:\n\u003e On 09/25/2013 01:45 PM, Mike Hearn wrote:\n\u003e\n\u003e\u003e OK, it might fit if you don't use any of the features the protocol\n\u003e\u003e provides :)\n\u003e\n\u003e Now you're dver-dramaticing (-:\n\u003e\n\u003e I'm just skipping one feature which I think is useless for QR codes\n\u003e scanned in person.\n\u003e\n\u003e\u003e You can try it here:\n\u003e\n\u003e Thanks. A typical request would be around 60 bytes, which should produce\n\u003e an URL with around 100 chars. That should be fine for scanning, but I\n\u003e will experiment.\n\u003e\n\u003e\u003e If you're thinking about governments and so on subverting CA's, then\n\u003e\u003e there is a plan for handling that (outside the Bitcoin world) called\n\u003e\u003e certificate transparency which is being implemented now.\n\u003e\n\u003e Good to hear. Let's see if it gets momentum.\n\u003e\n\u003e\u003e Now when you are getting a QR code from the web, it's already being\n\u003e\u003e served over HTTPS. So if you're up against an attacker who can break a\n\u003e\u003e CA in order to steal your money, then you already lose, the QRcode\n\u003e\u003e itself as MITMd.\n\u003e\n\u003e Sure. I was talking about QR codes scanned in person.\n\u003e\n\u003e\u003e In the Bluetooth case we might have to keep the address around and use\n\u003e\u003e it to do ECDHE or something like that.\n\u003e\n\u003e Yeah, will look at that as soon as we're implementing the payment\n\u003e protocol fully.\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e October Webinars: Code for Performance\n\u003e Free Intel webinars can help you accelerate application performance.\n\u003e Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from\n\u003e the latest Intel processors and coprocessors. See abstracts and register \u003e\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=60133471\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n\n\n-- \nJeff Garzik\nSenior Software Engineer and open source evangelist\nBitPay, Inc. https://bitpay.com/",
"sig": "8ce0d125ca599d43f7c54633151ea512f1c56efaee2376dc4f202d490112a3b22bc34e9376e1a3848d1a589e5365f23620444f154e2b85c26c9bced32c0963f5"
}