From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Justin Newton <justin@netki•com>
Subject: Re: [bitcoin-dev] Proposed BIP extension to BIP 0070
Date: Tue, 8 Mar 2016 22:34:13 +0000 [thread overview]
Message-ID: <201603082234.14398.luke@dashjr.org> (raw)
In-Reply-To: <CABqynx+gGnJ2AVByr1eKueSaohHtJVFsAVKrfS94StW2NzLWjw@mail.gmail.com>
Is there a way for Joe Mobile Wallet User to upload a set of N PaymentRequests
authenticated by his key to an untrusted server, which encrypts and passes
them on in response to InvoiceRequests? Or does this necessarily require the
recipient to be online?
On Tuesday, March 01, 2016 6:58:16 PM Justin Newton via bitcoin-dev wrote:
> The following draft BIP proposes an update to the Payment Protocol.
>
> Motivation:
>
> The motivation for defining this extension to the BIP70 Payment Protocol is
> to allow 2 parties to exchange payment information in a permissioned and
> encrypted way such that wallet address communication can become a more
> automated process. Additionally, this extension allows for the requestor of
> a PaymentRequest to supply a certificate and signature in order to
> facilitate identification for address release. This also allows
> for automated creation of off blockchain transaction logs that are human
> readable, containing who you transacted with, in addition to the
> information that it contains today.
>
> The motivation for this extension to BIP70 is threefold:
>
> 1. Ensure that the payment details can only be seen by the participants in
> the transaction, and not by any third party.
> 2. Enhance the Payment Protocol to allow for store and forward servers in
> order to allow, for example, mobile wallets to sign and serve
> Payment Requests.
> 3. Allow a sender of funds the option of sharing their identity with the
> receiver. This information could then be used to:
>
> * Make bitcoin logs more human readable
> * Give the user the ability to decide who to release payment
> details to
> * Allow an entity such as a political campaign to ensure donors
> match regulatory and legal requirements
> * Allow for an open standards based way for regulated financial
> entities to meet regulatory requirements
> * Automate the active exchange of payment addresses, so static
> addresses and BIP32 X-Pubs can be avoided to maintain privacy
> and convenience
>
> In short we wanted to make bitcoin more human, while at the same time
> improving transaction privacy.
>
> Full proposal here:
>
> https://github.com/techguy613/bips/blob/master/bip-invoicerequest-extension
> .mediawiki
>
> We look forward to your thoughts and feedback on this proposal!
>
> Justin
next prev parent reply other threads:[~2016-03-08 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 18:58 Justin Newton
2016-03-08 22:34 ` Luke Dashjr [this message]
2016-03-08 23:07 ` James MacWhyte
2016-03-09 1:17 ` James MacWhyte
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=201603082234.14398.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=justin@netki$(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