Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wk8s4-0007iA-71 for bitcoin-development@lists.sourceforge.net; Tue, 13 May 2014 09:19:36 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.178 as permitted sender) client-ip=209.85.212.178; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f178.google.com; Received: from mail-wi0-f178.google.com ([209.85.212.178]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wk8s3-0002ea-AB for bitcoin-development@lists.sourceforge.net; Tue, 13 May 2014 09:19:36 +0000 Received: by mail-wi0-f178.google.com with SMTP id hm4so226776wib.17 for ; Tue, 13 May 2014 02:19:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=nZg7QX+tKlUXKsrSjSths+q9iiJKywfTiysTP4LX3IQ=; b=D/MUpQ6cnhf0BcP1hg6sH5m/oGbsWDN7sgK0jb7EGyjgaEcKS3xJaKxnenaln80esK wsh9Qvwo6wOZjbh0X2RQqyMZQ1LLpPwjCGUMcaSvbE4I5LyOy9vT6fmHezaDivhgUUO6 2bbf1HydsnATFVa1qmu2MV///KdAFpn9dx5K2OPPA1gl6zvUSt1Q2rI/8VMPraTNA4vD TY+k+QUlNWEBBdGL4ZSlHxADMHLlb23HXUgAta92o6kZE/TfqVd7jzD2HfmN1eWr2jk2 oitMWd7a3sTyOUMhbq0IW0vCiOYSa8QwDw5vjuU9AfH9TEvc1VAhWRzt/Th8Lpmid2+H euHw== X-Gm-Message-State: ALoCoQl8Qk57OY5klptwH9OZkapCTj1kseX43ILuhofzDzqHk++KLquSlU+ppBLUzBqnzN1agLai X-Received: by 10.180.14.233 with SMTP id s9mr20194705wic.53.1399972768840; Tue, 13 May 2014 02:19:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.243.138 with HTTP; Tue, 13 May 2014 02:19:07 -0700 (PDT) In-Reply-To: <20140509150325.GA30436@savin> References: <20140509150325.GA30436@savin> From: Jeff Garzik Date: Tue, 13 May 2014 05:19:07 -0400 Message-ID: To: Peter Todd Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wk8s3-0002ea-AB Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] ECDH in the payment protocol X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2014 09:19:36 -0000 On Fri, May 9, 2014 at 11:03 AM, Peter Todd 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/