From: Adam Back <adam@cypherspace.org>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] Payment protocol and reliable Payment messages
Date: Tue, 14 Jan 2014 14:18:38 +0100 [thread overview]
Message-ID: <20140114131838.GA10516@netbook.cypherspace.org> (raw)
In-Reply-To: <20140114114134.GA9838@netbook.cypherspace.org>
Maybe even pay to (address derived from) contract hash has a hole: it
assumes the merchant cashes the funds (or cashes then reimburses via the
refund address). There is another rational (though abusive) move for the
merchant: let the buyers funds sit in limbo. Then the buyer has the onus to
go into disupte, maybe the seller is anonymous, in another country, or the
cost of dispute resolution more than the value lost, and anyway its not very
smart-contract like.
It might be better if the buyer has time-stamped evidence of having sent the
funds to the merchant, and evidence of non-collection of funds by the
merchant (by omission from the block chain).
Adam
prev parent reply other threads:[~2014-01-14 13:19 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
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 [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=20140114131838.GA10516@netbook.cypherspace.org \
--to=adam@cypherspace.org \
--cc=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.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