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
|
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 <mh.in.england@gmail.com>) id 1WzT89-0002j4-Tq
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 15:59:33 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.179 as permitted sender)
client-ip=209.85.214.179; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f179.google.com;
Received: from mail-ob0-f179.google.com ([209.85.214.179])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WzT89-0007al-3H
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 15:59:33 +0000
Received: by mail-ob0-f179.google.com with SMTP id uz6so570008obc.38
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Jun 2014 08:59:27 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.115.67 with SMTP id jm3mr2008763oeb.8.1403625567626; Tue,
24 Jun 2014 08:59:27 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Tue, 24 Jun 2014 08:59:27 -0700 (PDT)
In-Reply-To: <loc6bn$ck0$1@ger.gmane.org>
References: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
<loc6bn$ck0$1@ger.gmane.org>
Date: Tue, 24 Jun 2014 17:59:27 +0200
X-Google-Sender-Auth: SQByGvkCVFOP3vRdWl7EwcvDTzE
Message-ID: <CANEZrP3G0BxGh7PnN_czGnqLLzQZ-gbR=uPhOjO5_b_5dMQ1zA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=089e011619825b2de804fc970b0a
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: 1WzT89-0007al-3H
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:59:34 -0000
--089e011619825b2de804fc970b0a
Content-Type: text/plain; charset=UTF-8
>
> I think it should be made more clear what's the reference price for the
> discount.
>
That might be useful for merchants that already provide a series of
price-differentiated payment methods, yes. Will think about it.
> Also, currently PR are created by the payment processors afaik. How can
> they know what other payment option the merchant provides and what's the
> conditions?
>
Currently Coinbase let merchants specify the size of their discount (I
guess in percentage terms, I should ask). So the merchants tell the payment
processor. I don't think this is a worry at the moment.
--089e011619825b2de804fc970b0a
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">I think it should be made more clear what's =
the reference price for the<br>
discount.<br></blockquote><div><br></div><div>That might be useful for merc=
hants that already provide a series of price-differentiated payment methods=
, yes. Will think about it.</div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
Also, currently PR are created by the payment processors afaik. How can<br>
they know what other payment option the merchant provides and what's th=
e<br>
conditions?<br></blockquote><div><br></div><div>Currently Coinbase let merc=
hants specify the size of their discount (I guess in percentage terms, I sh=
ould ask). So the merchants tell the payment processor. I don't think t=
his is a worry at the moment.</div>
</div></div></div>
--089e011619825b2de804fc970b0a--
|
