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 13:38:10 +0100 [thread overview]
Message-ID: <CANEZrP3L-pxEVZAYn+=HmiNjZTX7TTYmdsMoYMc-cZ1OnH105g@mail.gmail.com> (raw)
In-Reply-To: <52EA3FAD.5080802@borboggle.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
>
> 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.
>
No retries. If there's a timeout the wallet will consider the payment not
made, and if the merchant broadcasts anyway, the wallet will see the
transactions and sync with them correctly. The ACK is not particularly
important in the current design, so that's no big deal.
If we see this situation crop up routinely we can take measures to improve
things. I doubt we will.
[-- Attachment #2: Type: text/html, Size: 883 bytes --]
prev parent reply other threads:[~2014-01-30 12:38 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
2014-01-30 12:20 ` Roy Badami
2014-01-30 12:38 ` Mike Hearn [this message]
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='CANEZrP3L-pxEVZAYn+=HmiNjZTX7TTYmdsMoYMc-cZ1OnH105g@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=chuck+bitcoindev@borboggle.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