From: Matthew Mitchell <matthewmitchell@godofgod•co.uk>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Fwd: Segmented Block Relaying BIP draft.
Date: Mon, 10 Sep 2012 16:25:25 +0100 [thread overview]
Message-ID: <4EA837E8-7224-497D-A3F7-B027A5148509@godofgod.co.uk> (raw)
In-Reply-To: <8819BE21-AB14-4407-8007-8D3DBD40444E@godofgod.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
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>
>
> 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.
>
>
> On 10 Sep 2012, at 16:14, Gregory Maxwell <gmaxwell@gmail•com> wrote:
>>
>> 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.
>
[-- Attachment #2: Type: text/html, Size: 2555 bytes --]
parent reply other threads:[~2012-09-10 15:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8819BE21-AB14-4407-8007-8D3DBD40444E@godofgod.co.uk>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA837E8-7224-497D-A3F7-B027A5148509@godofgod.co.uk \
--to=matthewmitchell@godofgod$(echo .)co.uk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox