path: root/82/e037c32076f4ef89fadf015bba70aacedca47a

Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from
	<SRS0=lbq4E4=HJ=godofgod.co.uk=matthewmitchell@eigbox.net>)
	id 1TB5ru-0004vY-6n for bitcoin-development@lists.sourceforge.net;
	Mon, 10 Sep 2012 15:25:46 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of eigbox.net
	designates 66.96.187.8 as permitted sender)
	client-ip=66.96.187.8;
	envelope-from=SRS0=lbq4E4=HJ=godofgod.co.uk=matthewmitchell@eigbox.net;
	helo=bosmailout08.eigbox.net; 
Received: from bosmailout08.eigbox.net ([66.96.187.8])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1TB5rq-0004bv-GK for bitcoin-development@lists.sourceforge.net;
	Mon, 10 Sep 2012 15:25:46 +0000
Received: from bosmailscan16.eigbox.net ([10.20.15.16])
	by bosmailout08.eigbox.net with esmtp (Exim) id 1TB5rl-0007yt-1O
	for bitcoin-development@lists.sourceforge.net;
	Mon, 10 Sep 2012 11:25:37 -0400
Received: from bosimpout01.eigbox.net ([10.20.55.1])
	by bosmailscan16.eigbox.net with esmtp (Exim) id 1TB5rk-00087L-CA
	for bitcoin-development@lists.sourceforge.net;
	Mon, 10 Sep 2012 11:25:36 -0400
Received: from bosauthsmtp11.eigbox.net ([10.20.18.11])
	by bosimpout01.eigbox.net with NO UCE
	id xTRc1j00K0EKspE01TRcrC; Mon, 10 Sep 2012 11:25:36 -0400
X-Authority-Analysis: v=2.0 cv=aPZHX8Bm c=1 sm=1
	a=EdgcOKDBJpMkesC5stW6Qg==:17 a=Goz4v7xpImgA:10 a=d6MfxKz5A4QA:10
	a=RmqW3wxksLsA:10 a=eGitJVp2AAAA:8 a=3c7jKd1tqgEA:10 a=pGLkceISAAAA:8
	a=5MiiPSIP-Fm_Q504cY8A:9 a=CjuIK1q_8ugA:10 a=uxwbsKC18SQA:10
	a=MSl-tDqOz04A:10 a=5dpPJnmuTADNgDJPBc4A:9 a=_W_S_7VecoQA:10
	a=anyYG9rjTBM1sAjEBQ8Cew==:117
X-EN-OrigOutIP: 10.20.18.11
X-EN-IMPSID: xTRc1j00K0EKspE01TRcrC
Received: from 5adb753d.bb.sky.com ([90.219.117.61] helo=[192.168.0.7])
	by bosauthsmtp11.eigbox.net with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim) id 1TB5rk-0001K0-44
	for bitcoin-development@lists.sourceforge.net;
	Mon, 10 Sep 2012 11:25:36 -0400
From: Matthew Mitchell <matthewmitchell@godofgod.co.uk>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A381379A-4955-497F-85C3-2177802B78C7"
Date: Mon, 10 Sep 2012 16:25:25 +0100
References: <8819BE21-AB14-4407-8007-8D3DBD40444E@godofgod.co.uk>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Message-Id: <4EA837E8-7224-497D-A3F7-B027A5148509@godofgod.co.uk>
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
X-EN-UserInfo: c68a83c59c94ef03b40bb4bc312c51e4:dffc0a9b4c8a0435ad832ff5852cab82
X-EN-AuthUser: godofgod@godofgod.co.uk
Sender: Matthew Mitchell <matthewmitchell@godofgod.co.uk>
X-EN-OrigIP: 90.219.117.61
X-EN-OrigHost: 5adb753d.bb.sky.com
X-Spam-Score: -0.9 (/)
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.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain 1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1TB5rq-0004bv-GK
Subject: [Bitcoin-development] Fwd:  Segmented Block Relaying BIP draft.
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: Mon, 10 Sep 2012 15:25:46 -0000


--Apple-Mail=_A381379A-4955-497F-85C3-2177802B78C7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Almost forgot...

Begin forwarded message:

> From: Matthew Mitchell <matthewmitchell@godofgod.co.uk>
> Subject: Re: [Bitcoin-development] Segmented Block Relaying BIP draft.
> Date: 10 September 2012 16:23:45 BST
> To: Gregory Maxwell <gmaxwell@gmail.com>
>=20
> By "gettreelevel" and "treelevel" you get the level of the merle tree =
with the hashes for the segments you want to download. You could request =
all the transaction hashes by specifying a very deep level. You could =
modify the proposal by removing the "level" byte in "gettreelevel" and =
always send the deepest level ie. The transaction hashes. Though by =
specifying the level you do not need to download all of the transaction =
hashes, only the hashes you need to verify each segment.
>=20
>=20
> On 10 Sep 2012, at 16:14, Gregory Maxwell <gmaxwell@gmail.com> wrote:
>>=20
>> Why does this focus on actually sending the hash tree?  The block
>> header + transaction list + transactions a node doesn't already know
>> (often just the coinbase) is enough.
>=20


--Apple-Mail=_A381379A-4955-497F-85C3-2177802B78C7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Almost forgot...<br><div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">Matthew Mitchell =
&lt;<a =
href=3D"mailto:matthewmitchell@godofgod.co.uk">matthewmitchell@godofgod.co=
.uk</a>&gt;<br></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>Subject: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><b>Re: [Bitcoin-development] Segmented Block Relaying =
BIP draft.</b><br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>Date: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">10 September 2012 16:23:45 BST<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">Gregory Maxwell =
&lt;<a =
href=3D"mailto:gmaxwell@gmail.com">gmaxwell@gmail.com</a>&gt;<br></span></=
div><br><div>By "gettreelevel" and "treelevel" you get the level of the =
merle tree with the hashes for the segments you want to download. You =
could request all the transaction hashes by specifying a very deep =
level. You could modify the proposal by removing the "level" byte in =
"gettreelevel" and always send the deepest level ie. The transaction =
hashes. Though by specifying the level you do not need to download all =
of the transaction hashes, only the hashes you need to verify each =
segment.<br><br><br>On 10 Sep 2012, at 16:14, Gregory Maxwell &lt;<a =
href=3D"mailto:gmaxwell@gmail.com">gmaxwell@gmail.com</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br>Why does this focus on actually =
sending the hash tree? &nbsp;The block<br>header + transaction list + =
transactions a node doesn't already know<br>(often just the coinbase) is =
enough.<br></blockquote><br></div></blockquote></div><br></body></html>=

--Apple-Mail=_A381379A-4955-497F-85C3-2177802B78C7--