Return-Path: <ctpacia@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 1F776412
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  9 Jan 2017 02:09:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com
	[209.85.220.178])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A8BE590
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  9 Jan 2017 02:09:11 +0000 (UTC)
Received: by mail-qk0-f178.google.com with SMTP id 11so29298210qkl.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 08 Jan 2017 18:09:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=to:from:subject:message-id:date:user-agent:mime-version
	:content-transfer-encoding;
	bh=o2c/H9b9er2RfUysmKP7OcV2mNCVKeKZ+vMBO5P7kzY=;
	b=WgQq8TDhOJS0OZtaqiEzp1P+UkkhZbqq0ZJcnkYi3tsLAwJR7pFC7XTZvbXEZhBSAR
	RMa7qxQszV8yHsjGhI5tU3U1FAYHZzyHUt1yr6UMdWEaRd/NubLUXM08wsWLJ7uwq6f8
	crNtqwGxlpMFJBlScxByBdpYS2UvY+EGAw2kPP7IQT2C8A9mr0lfWW4rdfzn0bqSRsa6
	ftzxkDpZGmBind80l99VarNm6o/vwtMFdG3cWxbcytKEcSaHZyQsvUE22bKrNuiGbKaH
	kUhjeGNImdnpS3V6AMc1H9Sv+pCDEj3C6ELFsWPagjQFIFjasnRap6lNOWof+1XNFSMi
	3a2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:to:from:subject:message-id:date:user-agent
	:mime-version:content-transfer-encoding;
	bh=o2c/H9b9er2RfUysmKP7OcV2mNCVKeKZ+vMBO5P7kzY=;
	b=PSKdcwJA+0Hozlm44m5p6iI5Xhqn1xxBvuOvIw84p8pL2FVwftUpjXuz5mLZ4QowR3
	HxHTecQW516IucKxz4ushDHuR9ovW4JiqmjP+onALnsznX+bW2YljwtaPYqtI+SgPeOL
	jrnUP2gzFecZfJtfq8MSJLyHP3+aHUQthoslEM20AKkC9LzY9GKGewUH5OYfVIPPOl/C
	48VyBNo8nakiYF3elVtzC3iLgxexAese690025y22MFZ788uDIJfcW6I66WloSTXi16+
	M925Rv3X57Ol7jCCUOBueyCkAQE4/e3QCrOIgTmI1UZRqSvlLMZvo1EB7/9hGzzy02Vu
	2Iqg==
X-Gm-Message-State: AIkVDXIvWJuayZIawDLXUS0J1bwQaxvrasxDP7vuiEkzqIvywP1mnj6wAg8QzNv8ixhgRg==
X-Received: by 10.55.114.2 with SMTP id n2mr61943203qkc.318.1483927750738;
	Sun, 08 Jan 2017 18:09:10 -0800 (PST)
Received: from ?IPv6:2601:18d:8181:e4d0:5c3e:2e5e:422f:1752?
	([2601:18d:8181:e4d0:5c3e:2e5e:422f:1752])
	by smtp.gmail.com with ESMTPSA id
	k26sm41159347qtc.36.2017.01.08.18.09.09
	for <bitcoin-dev@lists.linuxfoundation.org>
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Sun, 08 Jan 2017 18:09:10 -0800 (PST)
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: Chris <ctpacia@gmail.com>
Message-ID: <8c64f5db-7cac-3fde-85c0-a75d752c4192@gmail.com>
Date: Sun, 8 Jan 2017 21:09:09 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Thunderbird/45.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: [bitcoin-dev] Mutli-push op_return
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2017 02:09:12 -0000

Would there be an objection to making op_return outputs with two
pushdatas standard (same max data size)?

Use case is mostly tagging transactions so they can be returned by bloom
filtering nodes:

OP_RETURN <tag> <data>

Since bip37 nodes test each data element in each output script (which I
believe applies to op_return as well?) it provides a lightweight way of
fetching transactions where the tag matches a specific pattern.

It appears a sizable number of nodes/miners already accept such
transactions as this one was mined in the first block...
https://blockchain.info/tx/400b4738f1e4eab4062e085623b9a3a71670f5c0d42e32=
dbe5a4e71da5baabe0

- Chris