Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 3E152F6C for ; Tue, 26 Jan 2016 02:57:16 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id F0F7863 for ; Tue, 26 Jan 2016 02:57:15 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 2E32538A9581; Tue, 26 Jan 2016 02:56:56 +0000 (UTC) X-Hashcash: 1:25:160126:tobypadilla@gmail.com::zNoTlSZysyyJfJCC:ax2G0 X-Hashcash: 1:25:160126:bitcoin-dev@lists.linuxfoundation.org::5SbS31g1YA4LAXXE:AOOX From: Luke Dashjr To: Toby Padilla Date: Tue, 26 Jan 2016 02:56:54 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.13-gentoo; KDE/4.14.8; x86_64; ; ) References: <201601260224.16917.luke@dashjr.org> In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201601260256.55378.luke@dashjr.org> X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,RCVD_IN_SBL, RP_MATCHES_RCVD autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] [BIP Draft] Allow zero value OP_RETURN in Payment Protocol X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2016 02:57:16 -0000 On Tuesday, January 26, 2016 2:54:16 AM Toby Padilla wrote: > Luke - As stated in the Github thread, I totally understand where you're > coming from but the fact is people *will* encode data on the blockchain > using worse methods. For all of the reasons that OP_RETURN was a good idea > in the first place, it's a good idea to support it in PaymentRequests. As I explained, none of those reasons apply to PaymentRequests. > As for keyless - there's no way (that I know of) to construct a transaction > with a zero value OP_RETURN in an environment without keys since the > Payment Protocol is what defines the method for getting a transaction from > a server to a wallet. You can make a custom transaction and execute it in > the same application but without Payments there's no way to move > transactions between two applications. You need to build the transaction > where you execute it and thus need a key. I have no idea what you are trying to say here. Luke