Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WHyTG-0003HD-D2 for bitcoin-development@lists.sourceforge.net; Mon, 24 Feb 2014 16:33:34 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.171 as permitted sender) client-ip=74.125.82.171; envelope-from=jgarzik@bitpay.com; helo=mail-we0-f171.google.com; Received: from mail-we0-f171.google.com ([74.125.82.171]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WHyTF-0006M1-DY for bitcoin-development@lists.sourceforge.net; Mon, 24 Feb 2014 16:33:34 +0000 Received: by mail-we0-f171.google.com with SMTP id u56so4821948wes.2 for ; Mon, 24 Feb 2014 08:33:27 -0800 (PST) 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:date :message-id:subject:from:to:cc:content-type; bh=BLDKrB25DbN3DzubaDvTnYNkMqHY3fuuJ9gpehjUNSk=; b=BmU2XbGstizOLaFKrEscPDJNaaS2pobunpU2TNtJHGJotcEFbeCUoAHQKT0hV3EKse qZHxJqalwtTdmAKgNWZ95Uj+j0CFh9kLSsOPzt1KNn2dUeNlWoubsRCM8niw9vrtM/XN IxPuXP3f0NHshLzUnlOb24owUjQ9JRau0snDR7B217f9KKSF0UXm7X1wfPrNiR8WbM0k RotGZZHZ77VFTmeSav9NM9czCg9Ej7b4gfcJEW6Qct8M+BMgd/n+XTcapXYYBmJSm/YR Z3+221+2aBI77/1MqRV/vtpP1qS6nfv+nRuGjn27L4IMPqZn9dDagY5tTIecmHc7ynwq l67Q== X-Gm-Message-State: ALoCoQl36ogVs7O4CncVJDqxYkJ8mmK7CXwi6LmwQkFnMZ/SmqfVRquAcyGO6L3ci7mIi0R+imAK MIME-Version: 1.0 X-Received: by 10.180.189.139 with SMTP id gi11mr15071442wic.53.1393259607160; Mon, 24 Feb 2014 08:33:27 -0800 (PST) Received: by 10.194.82.197 with HTTP; Mon, 24 Feb 2014 08:33:27 -0800 (PST) In-Reply-To: References: Date: Mon, 24 Feb 2014 11:33:27 -0500 Message-ID: From: Jeff Garzik To: Pieter Wuille Content-Type: text/plain; charset=ISO-8859-1 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: 1WHyTF-0006M1-DY Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] On OP_RETURN in upcoming 0.9 release 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: Mon, 24 Feb 2014 16:33:34 -0000 (fscking 'send' hotkey in GMail) Not really - a MasterCoin or JPEG image transaction is not a "regular" transaction. On Mon, Feb 24, 2014 at 11:16 AM, Pieter Wuille wrote: > On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik wrote: > >> I do think >> regular transactions should have the ability to include some metadata. > > and > >> 2) Endorsement of chain data storage. >> >> Nothing could be further from the truth. > > These two statements are in direct contradiction with each other. > > -- > Pieter -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/