1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <voisine@gmail.com>) id 1YPiF5-0004I4-VA
for bitcoin-development@lists.sourceforge.net;
Mon, 23 Feb 2015 01:55:27 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.175 as permitted sender)
client-ip=209.85.212.175; envelope-from=voisine@gmail.com;
helo=mail-wi0-f175.google.com;
Received: from mail-wi0-f175.google.com ([209.85.212.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YPiF4-0000Tv-60
for bitcoin-development@lists.sourceforge.net;
Mon, 23 Feb 2015 01:55:27 +0000
Received: by mail-wi0-f175.google.com with SMTP id r20so13706988wiv.2
for <bitcoin-development@lists.sourceforge.net>;
Sun, 22 Feb 2015 17:55:20 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.23.39 with SMTP id j7mr17810306wjf.9.1424656520169; Sun,
22 Feb 2015 17:55:20 -0800 (PST)
Received: by 10.27.76.149 with HTTP; Sun, 22 Feb 2015 17:55:20 -0800 (PST)
In-Reply-To: <mcducr$m1i$1@ger.gmane.org>
References: <20150222190839.GA18527@odo.localdomain>
<54EA5AAE.3040306@voskuil.org> <mcducr$m1i$1@ger.gmane.org>
Date: Sun, 22 Feb 2015 17:55:20 -0800
Message-ID: <CACq0ZD6AA3F06j6FG8H9a=Mna2gvFmFpZ=2L4RacCnXc1mrHiA@mail.gmail.com>
From: Aaron Voisine <voisine@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=047d7b3a8bcecfd067050fb7b1b8
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(voisine[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YPiF4-0000Tv-60
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin at POS using BIP70,
NFC and offline payments - implementer feedback
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2015 01:55:28 -0000
--047d7b3a8bcecfd067050fb7b1b8
Content-Type: text/plain; charset=UTF-8
>> However, I don't think we should base
>> bitcoin around what Apple wants us to do. They've already had their war
>> on bitcoin. They are going to do whatever they can to protect their NFC
>> based payment system. We need to make their platform the the less
>> desirable one if they are going to play the game that way. If that means
>> an Airbitz like proposal is implemented as a fallback, maybe that is
>> fine and POS systems need to support both, but I just don't think we
>> should limit what we can do because of Apple's products capabilities.
>
> Ack on Airbitz, and ack on our relationship to Apple (-:
I also agree we shouldn't limit specs to Apple product capabilities. If
history is any indication, NFC will be opened up to developers in iOS 9,
just like touch id in was in iOS 8, and bluetooth LE in iOS 5, one major OS
revision after the hardware capability is first introduced.
Also, I'm pretty sure that Apple doesn't care about bitcoin at all. When
they banned wallets from the app store, it was prior to the 2013 FinCEN
guidance. At the time many of us, myself included, assumed USG would take
the same stance with bitcoin as they did against e-gold. It wasn't clear at
all that bitcoin didn't violate legal tender laws or who knows what. When
Apple allowed wallets back in, it was just weeks before Apple pay launched.
It's seems clear that bitcoin is too small for them to be concerned about
in the slightest.
Aaron Voisine
co-founder and CEO
breadwallet.com
--047d7b3a8bcecfd067050fb7b1b8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><span class=3D"im" style=3D"font-size:13px">>> Howev=
er, I don't think we should base<br>>> bitcoin around what Apple =
wants us to do. They've already had their war<br>>> on bitcoin. T=
hey are going to do whatever they can to protect their NFC<br>>> base=
d payment system. We need to make their platform the the less<br>>> d=
esirable one if they are going to play the game that way. If that means<br>=
>> an Airbitz like proposal is implemented as a fallback, maybe that =
is<br>>> fine and POS systems need to support both, but I just don=
9;t think we<br>>> should limit what we can do because of Apple's=
products capabilities.<br>><br></span><span style=3D"font-size:13px">&g=
t; Ack on Airbitz, and ack on our relationship to Apple (-:</span><br><div>=
<br></div><div>I also agree we shouldn't limit specs to Apple product c=
apabilities. If history is any indication, NFC will be opened up to develop=
ers in iOS 9, just like touch id in was in iOS 8, and bluetooth LE in iOS 5=
, one major OS revision after the hardware capability is first introduced.<=
br clear=3D"all"><div><div class=3D"gmail_signature"><div dir=3D"ltr"><div =
dir=3D"ltr"></div></div></div></div></div><div class=3D"gmail_extra"><br></=
div><div class=3D"gmail_extra">Also, I'm pretty sure that Apple doesn&#=
39;t care about bitcoin at all. When they banned wallets from the app store=
, it was prior to the 2013 FinCEN guidance. At the time many of us, myself =
included, assumed USG would take the same stance with bitcoin as they did a=
gainst e-gold. It wasn't clear at all that bitcoin didn't violate l=
egal tender laws or who knows what. When Apple allowed wallets back in, it =
was just weeks before Apple pay launched. It's seems clear that bitcoin=
is too small for them to be concerned about in the slightest.</div><div cl=
ass=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div><div class=3D=
"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div>Aaron Voisine=
</div><div>co-founder and CEO<br><a href=3D"http://breadwallet.com" target=
=3D"_blank">breadwallet.com</a></div></div></div></div></div></div></div></=
div>
--047d7b3a8bcecfd067050fb7b1b8--
|
