public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] ECDH in the payment protocol
Date: Tue, 13 May 2014 05:19:07 -0400	[thread overview]
Message-ID: <CAJHLa0M1T8XyiYNqbVp2ch_J1n-eE63UzXyb0XA9bDASGEnrLQ@mail.gmail.com> (raw)
In-Reply-To: <20140509150325.GA30436@savin>

On Fri, May 9, 2014 at 11:03 AM, Peter Todd <pete@petertodd.org> wrote:
> Of course we quickly rejected the idea of depending solely on a
> communications backchannel to retrieve funds. Any communications medium
> that isn't the blockchain makes the payment non-atomic, and thus creates
> opportunities for it to fail.

This is extremely simple-minded logic that encourages ephemeral, junk
data in the blockchain.  Not a scalable approach.

The implication is to put the communications medium in the blockchain
itself, which is wrong.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/



      parent reply	other threads:[~2014-05-13  9:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 12:05 [Bitcoin-development] ECDH in the payment protocol Mike Hearn
2014-05-09 15:03 ` Peter Todd
2014-05-09 15:15   ` Mike Hearn
2014-05-09 15:27     ` Peter Todd
2014-05-09 15:34       ` Mike Hearn
2014-05-09 15:43         ` Peter Todd
2014-05-09 16:12           ` Mike Hearn
2014-05-09 15:50         ` Pieter Wuille
2014-05-09 18:13           ` Peter Todd
2014-05-09 18:38             ` Pieter Wuille
2014-05-12 13:07               ` Peter Todd
2014-05-12 22:40               ` Chris Pacia
2014-05-13 10:29                 ` Mike Hearn
2014-05-13  9:19   ` Jeff Garzik [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=CAJHLa0M1T8XyiYNqbVp2ch_J1n-eE63UzXyb0XA9bDASGEnrLQ@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pete@petertodd.org \
    /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