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
|
Return-Path: <info@AndySchroder.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id BF2759C
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 22 Jun 2016 16:20:42 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from uschroder.com (uschroder.com [74.142.93.202])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 220F017B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 22 Jun 2016 16:20:42 +0000 (UTC)
Received: from [192.168.253.4] (cpe-96-28-21-149.kya.res.rr.com [96.28.21.149])
by uschroder.com (Postfix) with ESMTPSA id 3DC96233B25AD;
Wed, 22 Jun 2016 12:20:41 -0400 (EDT)
To: Erik Aronesty <erik@q32.com>
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
<576A44F1.9050108@electrum.org>
<CAJowKgLTtPKCV_6YWdTU2DiF0CAAiouggfGYVA+cax0Fyzc9Mg@mail.gmail.com>
<576AAAC4.1020304@AndySchroder.com>
<CAJowKgLK=AbsXcfsRKWNRQ=N=0QC3EVsALWxw6UOMCUXPo70fA@mail.gmail.com>
From: Andy Schroder <info@AndySchroder.com>
Openpgp: id=893F9F58D7AECF9DF0F772F534FAEFDB2D44186B;
url=http://andyschroder.com/static/AndySchroder.asc
Message-ID: <576ABAD6.7080308@AndySchroder.com>
Date: Wed, 22 Jun 2016 12:20:38 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CAJowKgLK=AbsXcfsRKWNRQ=N=0QC3EVsALWxw6UOMCUXPo70fA@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="V43DbUVN5405JSiChiA4EuIn4OKOf7reC"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 22 Jun 2016 19:34:08 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2016 16:20:42 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--V43DbUVN5405JSiChiA4EuIn4OKOf7reC
Content-Type: multipart/mixed; boundary="CW7il04V0TjL6lP63vUTIdL6FCswtxrlE"
From: Andy Schroder <info@AndySchroder.com>
To: Erik Aronesty <erik@q32.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Thomas Voegtlin <thomasv@electrum.org>
Message-ID: <576ABAD6.7080308@AndySchroder.com>
Subject: Re: Even more proposed BIP extensions to BIP 0070
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
<576A44F1.9050108@electrum.org>
<CAJowKgLTtPKCV_6YWdTU2DiF0CAAiouggfGYVA+cax0Fyzc9Mg@mail.gmail.com>
<576AAAC4.1020304@AndySchroder.com>
<CAJowKgLK=AbsXcfsRKWNRQ=N=0QC3EVsALWxw6UOMCUXPo70fA@mail.gmail.com>
In-Reply-To: <CAJowKgLK=AbsXcfsRKWNRQ=N=0QC3EVsALWxw6UOMCUXPo70fA@mail.gmail.com>
--CW7il04V0TjL6lP63vUTIdL6FCswtxrlE
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
I understand the need for people to make repeated payments to=20
individuals in real life that they know, without the payee every even=20
taking the effort to make a formal payment request (say you're just=20
paying a family member of friend back for picking something up for you=20
at the store, and you've already payed them many times before).
For a subscription, wouldn't it be better to promote payment channels or =
just send another payment request? I've been brainstorming recently=20
about a model where service providers could deliver invoices, receipts,=20
and payment requests in a standardized and secure way. In addition to=20
having a send, receive, and transaction history tab in your bitcoin=20
wallet, you'd also have an open payment channels tab (which would=20
include all applications on your computer that have an open real time=20
payment channel, such as a wifi access point, web browser, voip=20
provider, etc.), as well as a "bills to pay" tab. Since everything would =
be automated and consolidated locally, you wouldn't have to deal with=20
logging into a million different websites to get the bills and then pay=20
them. If it were this easy, why would you ever want to do a recurring=20
payment from a single payment request? I understand why you may think=20
you want to given current work flows, but I'm wondering if it may be=20
better to just skip over to a completely better way of doing things.
Andy Schroder
On 06/22/2016 11:30 AM, Erik Aronesty wrote:
> My conclusion at the bottom of that post was to keep BIP 75 the same,=20
> don't change a bit, and stick any subscription information (future=20
> payment schedule) in the PaymentACK. Then the wallet then=20
> re-initiates an invoice (unattended or attended.. up to the user),=20
> after the subscription interval is passed. Subscriptions are pretty=20
> important for Bitcoin to be used as a real payment system.=20
--CW7il04V0TjL6lP63vUTIdL6FCswtxrlE--
--V43DbUVN5405JSiChiA4EuIn4OKOf7reC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJXarrXAAoJEDT679stRBhrxCIH/imAZaiwPSvzSzbf203VYzMc
z5CY63wDRHIa07CM0gv6Fzv19Tfiim54sFOkHMiSPMVJya2Edwji9CY025M2nUZJ
uyPyRxowuXV9xsnUc+nRHzzaEfVC+DIuQFe5O0UQy9XFa4U3smxvGM5rWEw4iRuB
eu1lDJ7434b/gcwsaRktc6o4ebdAK6dAapovpQR5VRqgcyZTgsEAspKb8X52YhBL
+UpDNPWnCYezPR9CGBbWlrGarAMJ1xQ0s5vHh+uGpNt1riKfiL52QpQI8lFHoPfb
oMGMzJ8N/2OCIxM1dZx5zwuJc4D6GYAjWKI7CAvKM6NfXNr34nJ5DkE40Cmj5Lo=
=h9Ux
-----END PGP SIGNATURE-----
--V43DbUVN5405JSiChiA4EuIn4OKOf7reC--
|
