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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WzSIz-0008LA-Sx
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 15:06:41 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.47 as permitted sender)
client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f47.google.com;
Received: from mail-oa0-f47.google.com ([209.85.219.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WzSIy-0002jm-51
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 15:06:41 +0000
Received: by mail-oa0-f47.google.com with SMTP id n16so485374oag.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Jun 2014 08:06:34 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.52.77 with SMTP id r13mr1447710oeo.55.1403622394580; Tue,
24 Jun 2014 08:06:34 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Tue, 24 Jun 2014 08:06:34 -0700 (PDT)
In-Reply-To: <CAJna-HhX8HOci0KMe4ZScr4QW792S3n5twvU0QhbQe1N_3q7_w@mail.gmail.com>
References: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
<CAJHLa0Omiz+UhGjSKgYU7+b2YY7aN23w7o8CQntqMePFs7LkjA@mail.gmail.com>
<CANEZrP06gk-JhKaNpvYUTfjFq9AGnCay9=pjUGpVMjMSuX3_ew@mail.gmail.com>
<CAJna-HhX8HOci0KMe4ZScr4QW792S3n5twvU0QhbQe1N_3q7_w@mail.gmail.com>
Date: Tue, 24 Jun 2014 17:06:34 +0200
X-Google-Sender-Auth: OWKZAxlkN6Grt5vL2gBZINhpv2c
Message-ID: <CANEZrP0YV4xcK7y+H=gTmv_Hxs3nuACqEHWLUfcDdQeRhBF2Hw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=001a11330d023a55be04fc964e73
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WzSIy-0002jm-51
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
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: Tue, 24 Jun 2014 15:06:42 -0000
--001a11330d023a55be04fc964e73
Content-Type: text/plain; charset=UTF-8
>
> Sounds like marketing bullshit to me. It does not have even statistical
> meaning; well, you can "save" a lot of satoshis, but nobody tell you that
> the merchant cut you on BTC/USD exchange rate in tens of %.
>
Your own wallet can look up the exchange rate and compare it to what you're
getting (and in fact, wallets do!).
Besides, assuming the customer is *always* being scammed seems extreme.
There are plenty of merchants that genuinely care about their reputation
and genuinely want people to pay with Bitcoin so they can avoid card fees.
> Payment protocol should not contain these fictional data
>
Well, I think the protocol should contain whatever is useful.
I'll probably draft a BIP for this next week or so.
--001a11330d023a55be04fc964e73
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr">Sounds like marketing bullshit =
to me. It does not have even statistical meaning; well, you can "save&=
quot; a lot of satoshis, but nobody tell you that the merchant cut you on B=
TC/USD exchange rate in tens of %.</div>
</blockquote><div><br></div><div>Your own wallet can look up the exchange r=
ate and compare it to what you're getting (and in fact, wallets do!).</=
div><div><br></div><div>Besides, assuming the customer is <i>always</i>=C2=
=A0being scammed seems extreme. There are plenty of merchants that genuinel=
y care about their reputation and genuinely want people to pay with Bitcoin=
so they can avoid card fees.</div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Payme=
nt protocol should not contain these fictional data</div></div></blockquote=
><div><br>
</div><div>Well, I think the protocol should contain whatever is useful.</d=
iv><div><br></div><div>I'll probably draft a BIP for this next week or =
so.</div></div></div></div>
--001a11330d023a55be04fc964e73--
|
