From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1WWjGl-0002ry-Ou
	for bitcoin-development@lists.sourceforge.net;
	Sun, 06 Apr 2014 09:21:39 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.50 as permitted sender)
	client-ip=209.85.215.50; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f50.google.com; 
Received: from mail-la0-f50.google.com ([209.85.215.50])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WWjGk-00077K-VB
	for bitcoin-development@lists.sourceforge.net;
	Sun, 06 Apr 2014 09:21:39 +0000
Received: by mail-la0-f50.google.com with SMTP id pv20so3866427lab.9
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 06 Apr 2014 02:21:32 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.120.168 with SMTP id ld8mr16770108lab.12.1396776092271; 
	Sun, 06 Apr 2014 02:21:32 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Sun, 6 Apr 2014 02:21:32 -0700 (PDT)
In-Reply-To: <CAD=_8RSn+ZtxJL1=3BsaEvfc4Wrg7MW-uDTcnQo75GQbrVP3Ng@mail.gmail.com>
References: <CAD=_8RSn+ZtxJL1=3BsaEvfc4Wrg7MW-uDTcnQo75GQbrVP3Ng@mail.gmail.com>
Date: Sun, 6 Apr 2014 02:21:32 -0700
Message-ID: <CAAS2fgQktr1j1hGosyVH=rJJSnGz+Q9LAesGWLYYHk99Fq5Qag@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Maciej Trebacz <maciej@bitalo.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 1.1 (+)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gmaxwell[at]gmail.com)
	1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
	[Blocked - see <http://www.spamcop.net/bl.shtml?209.85.215.50>]
	-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
	1.5 SF_NO_SPF_SPAM         SF_NO_SPF_SPAM
X-Headers-End: 1WWjGk-00077K-VB
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Standardizing OP_RETURN message format
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 09:21:39 -0000

On Sun, Apr 6, 2014 at 12:35 AM, Maciej Trebacz <maciej@bitalo.com> wrote:
> 00 01 | none | Proof of burn transaction. Use it if you want to effectively
> destroy coins (by sending it all as fees to miners)

For just having a dummy output for an all fee transaction you do not
need to have a PUSH at all.