From: Mike Hearn <mike@plan99•net>
To: Chuck <chuck+bitcoindev@borboggle•com>
Cc: Bitcoin-Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 message delivery reliability
Date: Thu, 30 Jan 2014 11:49:32 +0100 [thread overview]
Message-ID: <CANEZrP0soR0xRqW=vsKaL__HRuWstA5vW=6_JkGZm=8wkm8Q3g@mail.gmail.com> (raw)
In-Reply-To: <52E9E787.8080304@borboggle.com>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Hi Chuck,
Both Bitcoin Core and bitcoinj are about to ship with the protocol as-is,
so any changes from this point on have to be backwards compatible.
On Thu, Jan 30, 2014 at 6:47 AM, Chuck <chuck+bitcoindev@borboggle•com>wrote:
> I presume the receipt R=(PaymentRequest,[transactions]) would suffice.
>
That's all you need to prove payment, yes.
> In the well-behaved case, I presume the point is to help the
> merchant associate some arbitrary data with the purchase as well as
> provide a refunding address for the customer.
That's right (+memo). And to provide an additional hook for future
features, like recurring billing, ECDH key agreements etc.
> In Step 3, it's critical the customer sign the message with the private
> key of the refund address, so that the merchant can be confident the
> refund address is correct.
>
Refund addresses as specced currently are optional. For instance bitcoinj
currently doesn't use them and won't until HD wallets support is done.
Let's get some practical experience with what we've got so far. We can
evolve PaymentRequest/Payment/PaymentACK in the right direction with
backwards compatible upgrades, I am hoping.
[-- Attachment #2: Type: text/html, Size: 1903 bytes --]
next prev parent reply other threads:[~2014-01-30 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 5:47 Chuck
2014-01-30 10:49 ` Mike Hearn [this message]
2014-01-30 11:15 ` Chuck
2014-01-30 11:31 ` Mike Hearn
2014-01-30 11:42 ` Chuck
2014-01-30 11:46 ` Pieter Wuille
2014-01-30 11:59 ` Mike Hearn
2014-01-30 12:02 ` Pieter Wuille
2014-01-30 12:03 ` Chuck
2014-01-30 12:20 ` Roy Badami
2014-01-30 12:38 ` Mike Hearn
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='CANEZrP0soR0xRqW=vsKaL__HRuWstA5vW=6_JkGZm=8wkm8Q3g@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=chuck+bitcoindev@borboggle$(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