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
132
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tamas@bitsofproof.com>) id 1WTXl3-0003RD-12
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Mar 2014 14:27:45 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WTXl1-0000YU-Ds
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Mar 2014 14:27:44 +0000
Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1WTXku-0003b7-Nj; Fri, 28 Mar 2014 15:27:36 +0100
Content-Type: multipart/signed;
boundary="Apple-Mail=_F38B8628-DDF1-43C0-92CC-1BF69D284D48";
protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <CABsx9T1POJ3KTqSz_c=SdYTg=EKWa9jqjOpHPZoMoPGXozsvJA@mail.gmail.com>
Date: Fri, 28 Mar 2014 15:27:35 +0100
Message-Id: <85A1792C-502E-4AC6-B8BC-A10C8FC1917F@bitsofproof.com>
References: <CANEZrP0AwR3WgHfwYWcrC9Z_MHPDwymWXAQwp7D8XZ+o2FsK8g@mail.gmail.com>
<612FFAAD-14FF-4261-927D-BD2E0F287257@bitsofproof.com>
<D7D06593-1987-490A-8DCD-21922E022E39@bitsofproof.com>
<CABsx9T1POJ3KTqSz_c=SdYTg=EKWa9jqjOpHPZoMoPGXozsvJA@mail.gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1396016863;
64c91abf;
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WTXl1-0000YU-Ds
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 70 refund field
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: Fri, 28 Mar 2014 14:27:45 -0000
--Apple-Mail=_F38B8628-DDF1-43C0-92CC-1BF69D284D48
Content-Type: multipart/alternative;
boundary="Apple-Mail=_888B4E7F-921E-440E-BFA8-9870CC1FD117"
--Apple-Mail=_888B4E7F-921E-440E-BFA8-9870CC1FD117
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=iso-8859-1
I have nothing against incremental development. This will however not =
pick up until it offers some incremental benefit compared to current =
payment processor solutions,=20
such as e.g.
1. Symmetrical. One can also offer a payment.
2. Aggregating and Netting. Handle multiple installments and/or net with =
previous cash flows.
3. More secure. One has a check not only on the payment address (which =
already has one with https:// in the web shop scenario it is currently =
able support) but not on the refund.
On 28.03.2014, at 15:01, Gavin Andresen <gavinandresen@gmail.com> wrote:
> On Fri, Mar 28, 2014 at 9:18 AM, Tamas Blummer <tamas@bitsofproof.com> =
wrote:
> May I ask how the current payment protocol is supposed to handle =
salaries?
>=20
> It doesn't.
>=20
> "walk before you run" and all that; lets see what problems we run into =
with the minimal payment protocol we have now (like refund outputs you =
have to remember forever) before we create an insurmountable set of =
problems by trying to solve everything we can think of all at once.
>=20
> --=20
> --
> Gavin Andresen
--Apple-Mail=_888B4E7F-921E-440E-BFA8-9870CC1FD117
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
charset=iso-8859-1
<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I have nothing against incremental development. This will however not pick up until it offers some incremental benefit compared to current payment processor solutions, </div><div>such as e.g.</div><div><br></div><div>1. Symmetrical. One can also offer a payment.</div><div>2. Aggregating and Netting. Handle multiple installments and/or net with previous cash flows.</div><div>3. More secure. One has a check not only on the payment address (which already has one with https:// in the web shop scenario it is currently able support) but not on the refund.</div><div><br></div><div>
<br><div><div>On 28.03.2014, at 15:01, Gavin Andresen <<a href="mailto:gavinandresen@gmail.com">gavinandresen@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Mar 28, 2014 at 9:18 AM, Tamas Blummer <span dir="ltr"><<a href="mailto:tamas@bitsofproof.com" target="_blank">tamas@bitsofproof.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">May I ask how the current payment protocol is supposed to handle salaries?</div></blockquote>
<div><br></div><div>It doesn't.</div><div><br></div><div>"walk before you run" and all that; lets see what problems we run into with the minimal payment protocol we have now (like refund outputs you have to remember forever) before we create an insurmountable set of problems by trying to solve everything we can think of all at once.</div>
</div><div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div>
</blockquote></div><br></div></body></html>
--Apple-Mail=_888B4E7F-921E-440E-BFA8-9870CC1FD117--
--Apple-Mail=_F38B8628-DDF1-43C0-92CC-1BF69D284D48
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJTNYbYAAoJEPZykcUXcTkc2MwIALvirIuQ/SEDBqus/yRLCfUP
FWw9x2I3XEwMbEY8fiYUemU4n1p6ydHeGaVapJt9/g25I+a57qCY/URvBmRlKrrC
G7OncZ/OokJt1xGTUjjZ8cqjZhHgwOOEbZMLD+WOsDFLqr0Jrk3LQ8zKQYuBOsz7
reZV1hFnUaO0DUPx7ypz8LE6N7ycMo4EVTmrSNqrlqFJdHzFUm4RuxNTyI7ObFv3
6Ntpv4AnVjQgyddO8IYOVQ9P9GhIr6R611VApPBjuvwRLxY+rPDpLDCkkqS981A1
AEdKFQJjNImllayIwkxsT9trC1wSlye/VPtxbQL6u3prLVMhOL+lGz49tBrs690=
=uEP5
-----END PGP SIGNATURE-----
--Apple-Mail=_F38B8628-DDF1-43C0-92CC-1BF69D284D48--
|
