From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Payment protocol and reliable Payment messages
Date: Tue, 14 Jan 2014 10:40:58 +0100 [thread overview]
Message-ID: <lb30mu$jjh$1@ger.gmane.org> (raw)
In-Reply-To: <CAPg+sBji5sFWZ_mDVXKKwkyeGYDbLmvwau457nmntT_NgTT+Sw@mail.gmail.com>
On 01/13/2014 06:56 PM, Pieter Wuille wrote:
> I want to avoid the case where a transaction confirms, but the
> associated payment is not delivered. If there is a reasonable chance
> that this case occurs in normal operation, it means the payment
> transmission cannot be relied upon.
I was thinking about this some more. Generally I think you have a point.
However, there is one case I'm worried about.
Imagine you get a good offer (payment request) from a merchant. You
would like to accept that offer, however the merchant has changed his
mind. If you don't broadcast the payment to the blockchain, you won't
have a chance to accept and legally bind the offer. The merchant will
silently discard your payment messages.
At some point, you will involve a judge. If you can present the payment
request and the payment from the block chain, you're in a much better
position than if you just present a request but no confirmed payment.
I think in some cases you might want to broadcast your txn to the P2P
network, even if the payment messages get lost. What do you think?
next prev parent reply other threads:[~2014-01-14 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:43 [Bitcoin-development] Payment protocol and reliable Payment messages Pieter Wuille
2014-01-13 17:44 ` Andreas Schildbach
2014-01-13 17:56 ` Pieter Wuille
2014-01-13 22:24 ` Andreas Schildbach
2014-01-14 9:40 ` Andreas Schildbach [this message]
2014-01-14 10:45 ` Mike Hearn
2014-01-14 11:01 ` Andreas Schildbach
2014-01-14 11:41 ` Adam Back
2014-01-14 13:18 ` Adam Back
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='lb30mu$jjh$1@ger.gmane.org' \
--to=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
/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