From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VdPyZ-0006uu-Iq for bitcoin-development@lists.sourceforge.net; Mon, 04 Nov 2013 19:38:15 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.177 as permitted sender) client-ip=209.85.214.177; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f177.google.com; Received: from mail-ob0-f177.google.com ([209.85.214.177]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VdPyY-0002ae-Qo for bitcoin-development@lists.sourceforge.net; Mon, 04 Nov 2013 19:38:15 +0000 Received: by mail-ob0-f177.google.com with SMTP id vb8so7411616obc.8 for ; Mon, 04 Nov 2013 11:38:09 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.161.10 with SMTP id xo10mr1272801oeb.71.1383593889427; Mon, 04 Nov 2013 11:38:09 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.156.42 with HTTP; Mon, 4 Nov 2013 11:38:09 -0800 (PST) In-Reply-To: <20131104181649.GA3847@petertodd.org> References: <20131104115314.GA1013@savin> <20131104181649.GA3847@petertodd.org> Date: Mon, 4 Nov 2013 20:38:09 +0100 X-Google-Sender-Auth: UyYTY2LVtdbNqJFM9zQznXx3ML0 Message-ID: From: Mike Hearn To: Peter Todd Content-Type: multipart/alternative; boundary=089e0117686b4af7e204ea5f0e29 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: petertodd.org] X-Headers-End: 1VdPyY-0002ae-Qo Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Committing to extra block data/a better merge-mine standard 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, 04 Nov 2013 19:38:15 -0000 --089e0117686b4af7e204ea5f0e29 Content-Type: text/plain; charset=UTF-8 I like the UUID-as-path idea. That resolves the problem of how to share the alt-chain merkle tree quite nicely. On Mon, Nov 4, 2013 at 7:16 PM, Peter Todd wrote: > No sense in compromising - you need a whole merkle path to prove the > extra data is valid so you might as well make this a full 256 bits; > The Merkle branch doesn't get stored indefinitely though, whereas the coinbase hash does. The data stored in the coinbase [output] can always just be the 256-bit root hash truncated to less. I doubt the additional bytes make much difference really, so the additional complexity may not be worth it. But it wouldn't be an issue to do. --089e0117686b4af7e204ea5f0e29 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I like the UUID-as-path idea. That resolves the problem of= how to share the alt-chain merkle tree quite nicely.

On Mon, Nov 4, 2013 at 7:16 PM, Peter T= odd <pete@petertodd.org> wrote:
No sense in compromising - you need a whole = merkle path to prove the
extra data is valid so you might as well make this a full 256 bits;

The Merkle branch doesn't get stored indef= initely though, whereas the coinbase hash does. The data stored in the coin= base [output] can always just be the 256-bit root hash truncated to less.

I doubt the additional bytes make much difference reall= y, so the additional complexity may not be worth it. But it wouldn't be= an issue to do.
--089e0117686b4af7e204ea5f0e29--