From: Chuck <chuck+bitcoindev@borboggle•com>
To: 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 18:42:56 +0700 [thread overview]
Message-ID: <52EA3AC0.5090709@borboggle.com> (raw)
In-Reply-To: <CANEZrP2JMGdcCa_6p-vmLJ3yO=GVBZXA39VLwiPRUbDu2zeH5w@mail.gmail.com>
On 1/30/2014 6:31 PM, Mike Hearn wrote:
> The arbitrator would presumably have some rules about what is or isn't
> an acceptable form of payment.
Do you think this puts unnecessary trust into a third party? If the
merchant instead signed and agreed to the unsigned transactions before
they were broadcast (as in my OP), these arbitration concerns disappear.
> HTTP has response codes for submission of the Payment message. We
> could add signing to PaymentACK and other things in future, if that
> turns out to be insufficient in practice.
HTTP isn't the only message delivery mechanism. Merchants can also lie:
reply with 200 OK and an empty body. Or, reply with 404 not found and
broadcast transactions anyway.
Cheers,
Chuck
next prev parent reply other threads:[~2014-01-30 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 5:47 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 [this message]
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
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=52EA3AC0.5090709@borboggle.com \
--to=chuck+bitcoindev@borboggle$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)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