summaryrefslogtreecommitdiff
path: root/df/a0a9043e24905cea75e7a3b2c647fadb3e4e5a
blob: 66ae11f73d7aa1a3113c68b26fd6dc6672fd2cf7 (plain)
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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1WTXQb-00019W-Oq
	for bitcoin-development@lists.sourceforge.net;
	Fri, 28 Mar 2014 14:06:37 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.45 as permitted sender)
	client-ip=209.85.219.45; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f45.google.com; 
Received: from mail-oa0-f45.google.com ([209.85.219.45])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WTXQb-0006Qv-09
	for bitcoin-development@lists.sourceforge.net;
	Fri, 28 Mar 2014 14:06:37 +0000
Received: by mail-oa0-f45.google.com with SMTP id eb12so6116855oac.4
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 28 Mar 2014 07:06:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.219.167 with SMTP id pp7mr213578obc.85.1396015591643;
	Fri, 28 Mar 2014 07:06:31 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Fri, 28 Mar 2014 07:06:31 -0700 (PDT)
In-Reply-To: <CABsx9T1POJ3KTqSz_c=SdYTg=EKWa9jqjOpHPZoMoPGXozsvJA@mail.gmail.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>
Date: Fri, 28 Mar 2014 15:06:31 +0100
X-Google-Sender-Auth: pjEA-4txKgREvN8Nhf5ELXOM8t4
Message-ID: <CANEZrP3BzGBcAgeppqbyYX4CcAH2ZVn+_-YUdCJRgSzBagOCpA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=089e0141ab8270e0ef04f5ab35f9
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: 1WTXQb-0006Qv-09
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:06:38 -0000

--089e0141ab8270e0ef04f5ab35f9
Content-Type: text/plain; charset=UTF-8

Yeah. Though there's actually a proposal for recurring payments from the
KillBill folks. I keep bugging BitPay to review it but it seems they're
lagging behind there, so perhaps we should just move ahead with that
candidate extension.


On Fri, Mar 28, 2014 at 3:01 PM, 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?
>>
>
> It doesn't.
>
> "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.
>
> --
> --
> Gavin Andresen
>

--089e0141ab8270e0ef04f5ab35f9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yeah. Though there&#39;s actually a proposal for recurring=
 payments from the KillBill folks. I keep bugging BitPay to review it but i=
t seems they&#39;re lagging behind there, so perhaps we should just move ah=
ead with that candidate extension.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Mar 2=
8, 2014 at 3:01 PM, Gavin Andresen <span dir=3D"ltr">&lt;<a href=3D"mailto:=
gavinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D"">On Fri, Mar 28, 2014 at 9:18 AM,=
 Tamas Blummer <span dir=3D"ltr">&lt;<a href=3D"mailto:tamas@bitsofproof.co=
m" target=3D"_blank">tamas@bitsofproof.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">May I as=
k how the current payment protocol is supposed to handle salaries?</div></b=
lockquote>

<div><br></div></div><div>It doesn&#39;t.</div><div><br></div><div>&quot;wa=
lk before you run&quot; and all that; lets see what problems we run into wi=
th the minimal payment protocol we have now (like refund outputs you have t=
o remember forever) before we create an insurmountable set of problems by t=
rying to solve everything we can think of all at once.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
</font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br=
></div>-- <br>--<br>Gavin Andresen<br>
</font></span></div></div>
</blockquote></div><br></div>

--089e0141ab8270e0ef04f5ab35f9--