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 1XnGAd-0001Pu-2y for bitcoin-development@lists.sourceforge.net; Sun, 09 Nov 2014 00:15:55 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.52 as permitted sender) client-ip=209.85.192.52; envelope-from=tier.nolan@gmail.com; helo=mail-qg0-f52.google.com; Received: from mail-qg0-f52.google.com ([209.85.192.52]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XnGAc-0003NE-4k for bitcoin-development@lists.sourceforge.net; Sun, 09 Nov 2014 00:15:55 +0000 Received: by mail-qg0-f52.google.com with SMTP id a108so3933525qge.25 for ; Sat, 08 Nov 2014 16:15:48 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.87.11 with SMTP id q11mr23820515qgd.6.1415490327462; Sat, 08 Nov 2014 15:45:27 -0800 (PST) Received: by 10.140.41.18 with HTTP; Sat, 8 Nov 2014 15:45:27 -0800 (PST) Date: Sat, 8 Nov 2014 23:45:27 +0000 Message-ID: From: Tier Nolan To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a113a61de26cb3a0507618636 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (tier.nolan[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1XnGAc-0003NE-4k Subject: [Bitcoin-development] BIP draft - Auxiliary Header Format 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: Sun, 09 Nov 2014 00:15:55 -0000 --001a113a61de26cb3a0507618636 Content-Type: text/plain; charset=UTF-8 I created a draft BIP detailing a way to add auxiliary headers to Bitcoin in a bandwidth efficient way. The overhead per auxiliary header is only around 104 bytes per header. This is much smaller than would be required by embedding the hash of the header in the coinbase of the block. It is a soft fork and it uses the last transaction in the block to store the hash of the auxiliary header. It makes use of the fact that the last transaction in the block has a much less complex Merkle branch than the other transactions. https://github.com/TierNolan/bips/blob/aux_header/bip-aux-header.mediawiki --001a113a61de26cb3a0507618636 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I created a draft BIP detailing a way to add aux= iliary headers to Bitcoin in a bandwidth efficient way.=C2=A0 The overhead = per auxiliary header is only around 104 bytes per header.=C2=A0 This is muc= h smaller than would be required by embedding the hash of the header in the= coinbase of the block.

It is a soft fork and it uses the last= transaction in the block to store the hash of the auxiliary header.
It makes use of the fact that the last transaction in the block has = a much less complex Merkle branch than the other transactions.
--001a113a61de26cb3a0507618636--