From: Mike Hearn <mike@plan99•net>
To: Andreas Schildbach <andreas@schildbach•de>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Payment protocol and reliable Payment messages
Date: Tue, 14 Jan 2014 11:45:59 +0100 [thread overview]
Message-ID: <CANEZrP3BeFMLtcThr=Gp5mudbtQeT_dHno1DGQzOg28YKBNkzA@mail.gmail.com> (raw)
In-Reply-To: <lb30mu$jjh$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
>
> 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.
Usually if the merchant has not delivered, then at that point it's not a
problem and he is allowed to change his mind. It's only if they change
their mind *after* you pay that it's a problem, right?
[-- Attachment #2: Type: text/html, Size: 588 bytes --]
next prev parent reply other threads:[~2014-01-14 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:43 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
2014-01-14 10:45 ` Mike Hearn [this message]
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='CANEZrP3BeFMLtcThr=Gp5mudbtQeT_dHno1DGQzOg28YKBNkzA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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