From: Mike Hearn <mike@plan99•net>
To: Paul Goldstein <paul@skydroid•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bill Request Message - (another) Proposed BIP 70 extension
Date: Wed, 25 Jun 2014 16:38:06 +0200 [thread overview]
Message-ID: <CANEZrP19T4q73Y9Y4x2gyD26MK5CPkuDdd12-Ewr_DhpGsGzng@mail.gmail.com> (raw)
In-Reply-To: <CADE3-jBdEM4YnBKue6_Q_ZDitUZ7aSGGqrYg6X=N0c0PC1az+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Alright. I still tend to think it's not a big deal, but there's no reason
both or all mechanisms can't co-exist.
BTW: a QR code next to a cash register can be fixed i.e. printed on paper
when using BIP70. The PoS would upload payment details to the server and
the URL for that particular PoS unit would then serve it when the user
scans the QR code. Alternatively, Andreas' work on Bluetooth may be more
appropriate: the QR code can contain the BT MAC of the device and the
payment request is downloaded that way. That's already implemented! I still
feel that if a seller can scan a users phone, the users phone can certainly
scan some rectangle that's physically near by the sales counter.
The other nice thing about that approach is the QRcode can also be an NFC
tag i.e. have the tag behind it with a little icon in the middle of the QR
code to indicate that touching works as well as scanning.
One project I keep wanting to play with is making these little NFC-QRcode
hybrids and a simple PoS app to go with them. But no time, alas ....
[-- Attachment #2: Type: text/html, Size: 1166 bytes --]
prev parent reply other threads:[~2014-06-25 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 19:44 Paul Goldstein
2014-06-25 11:23 ` Mike Hearn
[not found] ` <CADE3-jBdEM4YnBKue6_Q_ZDitUZ7aSGGqrYg6X=N0c0PC1az+g@mail.gmail.com>
2014-06-25 14:38 ` Mike Hearn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP19T4q73Y9Y4x2gyD26MK5CPkuDdd12-Ewr_DhpGsGzng@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=paul@skydroid$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox