public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chuck <chuck+bitcoindev@borboggle.com>
To: Pieter Wuille <pieter.wuille@gmail.com>, Mike Hearn <mike@plan99.net>
Cc: Bitcoin-Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 message delivery reliability
Date: Thu, 30 Jan 2014 19:03:57 +0700	[thread overview]
Message-ID: <52EA3FAD.5080802@borboggle.com> (raw)
In-Reply-To: <CAPg+sBhzLVxdU+Kg2N7eW=34X1-6qbg1+rPzyMqfsy01zqnfGA@mail.gmail.com>

On 1/30/2014 7:02 PM, Pieter Wuille wrote:
> On Thu, Jan 30, 2014 at 12:59 PM, Mike Hearn <mike@plan99.net> wrote:
>> With the way it works in bitcoinj, the tx is only committed to the wallet if
>> the server accepts the Payment message and ACKs it. So the tx would not be
>> retried if there's a failure submitting or some kind of internal server
>> error, and the UI would show that the payment failed. That seems
>> straightforward and how I'd expect things to work as a user.
> That's one right way to do it imho, but not what is suggested or
> required by the specification, and not what bitcoin core master
> currently implements.
>
If you sent the Payment message and the server goes silent after 
receiving it, you retry to delivery.  However, the merchant can 
broadcast the transactions and force them into your wallet anyway. You 
could, quite likely, pay and never get an ACK.



  reply	other threads:[~2014-01-30 12:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30  5:47 [Bitcoin-development] BIP70 message delivery reliability Chuck
2014-01-30 10:49 ` Mike Hearn
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 [this message]
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=52EA3FAD.5080802@borboggle.com \
    --to=chuck+bitcoindev@borboggle.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mike@plan99.net \
    --cc=pieter.wuille@gmail.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