From: Andy Schroder <info@AndySchroder•com>
To: Erik Aronesty <erik@q32•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
Date: Wed, 22 Jun 2016 12:20:38 -0400 [thread overview]
Message-ID: <576ABAD6.7080308@AndySchroder.com> (raw)
In-Reply-To: <CAJowKgLK=AbsXcfsRKWNRQ=N=0QC3EVsALWxw6UOMCUXPo70fA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1905 bytes --]
I understand the need for people to make repeated payments to
individuals in real life that they know, without the payee every even
taking the effort to make a formal payment request (say you're just
paying a family member of friend back for picking something up for you
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
about a model where service providers could deliver invoices, receipts,
and payment requests in a standardized and secure way. In addition to
having a send, receive, and transaction history tab in your bitcoin
wallet, you'd also have an open payment channels tab (which would
include all applications on your computer that have an open real time
payment channel, such as a wifi access point, web browser, voip
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
logging into a million different websites to get the bills and then pay
them. If it were this easy, why would you ever want to do a recurring
payment from a single payment request? I understand why you may think
you want to given current work flows, but I'm wondering if it may be
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,
> don't change a bit, and stick any subscription information (future
> payment schedule) in the PaymentACK. Then the wallet then
> re-initiates an invoice (unattended or attended.. up to the user),
> after the subscription interval is passed. Subscriptions are pretty
> important for Bitcoin to be used as a real payment system.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2016-06-22 16:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 17:33 Erik Aronesty
2016-06-21 9:43 ` Andreas Schildbach
2016-06-21 17:09 ` Erik Aronesty
2016-06-21 19:50 ` Andy Schroder
2016-06-21 20:44 ` Luke Dashjr
2016-06-21 21:42 ` Erik Aronesty
2016-06-22 0:36 ` Luke Dashjr
2016-06-21 22:10 ` Peter Todd
2016-06-21 22:19 ` Peter Todd
2016-06-21 20:56 ` James MacWhyte
2016-06-21 21:17 ` Matt David
2016-06-21 22:13 ` Peter Todd
2016-06-21 22:50 ` James MacWhyte
2016-06-21 23:02 ` Peter Todd
2016-06-22 0:14 ` Justin Newton
2016-06-23 10:56 ` Peter Todd
2016-06-23 11:30 ` Pieter Wuille
2016-06-23 11:39 ` Peter Todd
2016-06-23 12:01 ` Pieter Wuille
2016-06-23 12:10 ` Peter Todd
2016-06-23 12:16 ` Pieter Wuille
2016-06-23 12:43 ` Peter Todd
2016-06-23 13:03 ` Erik Aronesty
2016-06-23 16:58 ` Aaron Voisine
2016-06-23 20:46 ` s7r
2016-06-23 21:07 ` Justin Newton
2016-06-23 21:31 ` Police Terror
2016-06-23 22:44 ` Justin Newton
2016-06-24 2:26 ` Erik Aronesty
2016-06-24 5:27 ` James MacWhyte
2016-06-22 7:57 ` Thomas Voegtlin
2016-06-22 14:25 ` Erik Aronesty
2016-06-22 15:12 ` Andy Schroder
2016-06-22 15:30 ` Erik Aronesty
2016-06-22 16:20 ` Andy Schroder [this message]
2016-06-22 17:07 ` Erik Aronesty
2016-06-22 20:11 ` James MacWhyte
2016-06-22 20:37 ` Erik Aronesty
2016-06-23 11:50 ` Andreas Schildbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=576ABAD6.7080308@AndySchroder.com \
--to=info@andyschroder$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox