From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Instant / contactless payments
Date: Thu, 06 Mar 2014 17:46:53 +0100 [thread overview]
Message-ID: <lfa8pf$ckc$1@ger.gmane.org> (raw)
In-Reply-To: <CALDj+BZE1KtMGpMH3UHtxjN2vXxu39o_hAWPdg==KLsWpe1zqA@mail.gmail.com>
> Not sure if you've seen it, but here is how we do NFC right
> now http://www.youtube.com/watch?v=DGOMIG9JUY8 with XBTerminal.
Thanks for the video! It's always good to see these things in action so
you can start believing in it.
> For now this is just an NDEF URI message with Bitcoin URI inside, and
> then transaction itself propagated to the network by the phone using
> it's own Internet connection. Far not ideal, but even this is supported
> only by Andreas' Wallet, so we cannot move ahead alot really until other
> wallets will have some support in this area.
Supporting Bluetooth is optional in the sense that if a wallet should
not support it, you will still receive the transaction via the P2P
network. So I'd say definately go for Bluetooth.
> As you see - it's taking just few seconds, most of which is manual
> payment confirmation.
I wonder about the receipt step -- are you generating a PDF on device
and sending it via NFC? This is something that could be supported by the
BIP70 payment protocol. We should try to avoid the second tap, its not
intuitive.
> And btw, have you been to London
> lately? Oyster readers now accept contactless cards directly along with
> Oyster cards itself.
Contactless cards? Last I was to London, the Oyster card was already
contactless. Have there ever been magnet-strip-based Oyster cards?
> I wonder if eventually in future we could add
> bitcoin support into that system directly, without hardware replacements.
Neat thought (-:
next prev parent reply other threads:[~2014-03-06 16:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:45 [Bitcoin-development] Instant / contactless payments Mike Hearn
2014-03-06 11:26 ` Andreas Schildbach
2014-03-06 13:44 ` Mike Hearn
2014-03-06 14:51 ` Andreas Schildbach
2014-03-06 16:55 ` [Bitcoin-development] Instant / contactless payments, IsoDep Andreas Schildbach
2014-03-06 17:00 ` Mike Hearn
2014-03-07 8:45 ` Andreas Schildbach
2014-03-07 9:26 ` [Bitcoin-development] Instant / contactless payments Johannes Zweng
2014-03-07 10:00 ` Mike Hearn
2014-03-07 10:23 ` Andreas Schildbach
2014-03-07 11:01 ` Mike Hearn
2014-03-07 12:00 ` Johannes Zweng
2014-03-06 14:20 ` Brooks Boyd
2014-03-06 17:07 ` Mike Hearn
2014-03-06 18:08 ` Brooks Boyd
2014-03-06 18:12 ` Mike Hearn
2014-03-06 18:20 ` Brooks Boyd
2014-03-06 18:24 ` Mike Hearn
2014-03-07 18:07 ` Joel Kaartinen
2014-03-06 14:39 ` Alex Kotenko
2014-03-06 16:46 ` Andreas Schildbach [this message]
2014-03-06 16:52 ` Mike Hearn
2014-03-06 18:03 ` Alex Kotenko
2014-03-07 8:59 ` Andreas Schildbach
2014-03-06 17:03 ` Mike Hearn
2014-03-06 18:49 ` Alex Kotenko
2014-03-08 8:52 ` Jan Vornberger
2014-03-10 15:09 ` Alex Kotenko
2014-03-10 19:28 ` Andreas Schildbach
2014-03-10 19:47 ` Alex Kotenko
2014-03-07 19:08 ` Troy Benjegerdes
2014-03-10 16:04 ` Mike Hearn
2014-03-10 16:14 ` Jean-Paul Kogelman
2014-03-10 16:27 ` Alex Kotenko
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='lfa8pf$ckc$1@ger.gmane.org' \
--to=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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