From: Gavin Andresen <gavinandresen@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP70: PaymentACK semantics
Date: Thu, 30 Jan 2014 10:06:23 -0500 [thread overview]
Message-ID: <CABsx9T1jAobC_p9oa_PX8M7Bo6Db3=oBhPuhp5CXVHqTRb=Hng@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0MVbDnC0i+uT9Sahxk8ht9R5ztSJ-kOU5ERapeVibH9eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
On Thu, Jan 30, 2014 at 9:51 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> Is this truly the intent? That the merchant/processor takes full
> responsibility for getting the TX confirmed?
>
The intent is to give the customer a great experience. We could talk for
months about whether having the wallet broadcast the transaction as soon as
possible or having it wait for the merchant to respond with a PaymentACK is
better. But I think we should let wallets experiment with different ways of
doing it, and see what works best in practice.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 971 bytes --]
next prev parent reply other threads:[~2014-01-30 15:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 21:56 [Bitcoin-development] BIP70: PaymentACK semantics Andreas Schildbach
2014-01-27 14:54 ` Gavin Andresen
2014-01-27 15:20 ` Andreas Schildbach
2014-01-27 15:52 ` Mike Hearn
2014-01-27 22:03 ` Kevin Greene
2014-01-27 22:17 ` Pieter Wuille
2014-01-27 22:39 ` Kevin Greene
2014-01-28 11:42 ` Mike Hearn
2014-01-28 12:53 ` Gavin Andresen
2014-01-28 13:09 ` Pieter Wuille
2014-01-28 13:24 ` Mike Hearn
2014-01-28 17:23 ` Peter Todd
2014-01-28 17:33 ` Mike Hearn
2014-01-28 21:12 ` Peter Todd
2014-01-30 14:51 ` Jeff Garzik
2014-01-30 14:58 ` Pieter Wuille
2014-01-30 15:01 ` Mike Hearn
2014-01-30 15:06 ` Gavin Andresen [this message]
2014-01-30 15:16 ` Pieter Wuille
2014-01-30 20:16 ` Jeremy Spilman
2014-01-31 4:16 ` Chuck
2014-01-31 16:21 ` Christophe Biocca
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='CABsx9T1jAobC_p9oa_PX8M7Bo6Db3=oBhPuhp5CXVHqTRb=Hng@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@bitpay.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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