From: Geir Harald Hansen <operator@bitminter.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Request for review/testing: headers-first synchronization in Bitcoin Core
Date: Sun, 12 Oct 2014 12:06:25 +0200 [thread overview]
Message-ID: <543A52A1.2010408@bitminter.com> (raw)
In-Reply-To: <CA+s+GJA=zgacbURh83DKyAV=x_t15xT=5cJTwSY8Omk2XZyuxA@mail.gmail.com>
On 12.10.2014 11:52, Wladimir wrote:
> On Sun, Oct 12, 2014 at 10:41 AM, Geir Harald Hansen
> <operator@bitminter.com> wrote:
>> On 12.10.2014 01:34, Pieter Wuille wrote:
>>> * No orphan blocks stored in memory anymore (reducing memory usage during sync).
>>
>> Will this slow down reorgs after a fork, compared to today?
>
> Why would you think so? Orphan blocks are blocks whose parent is not
> known. In the case of a reorganization the client 'jumps' to a new
> best chain, for this to happen the original tip and the new best tip
> and all their parents must be already known.
I was thinking of shorter sides of forks as being orphaned. Sorry for
the confusion.
Regards,
Geir H. Hansen, Bitminter
next prev parent reply other threads:[~2014-10-12 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 23:34 [Bitcoin-development] Request for review/testing: headers-first synchronization in Bitcoin Core Pieter Wuille
2014-10-12 5:51 ` Aaron Voisine
2014-10-12 7:14 ` Gregory Maxwell
2014-10-12 8:41 ` Geir Harald Hansen
2014-10-12 9:44 ` Luke Dashjr
2014-10-12 9:52 ` Wladimir
2014-10-12 10:06 ` Geir Harald Hansen [this message]
2014-10-12 19:13 ` Jameson Lopp
2014-10-13 22:43 ` 21E14
2014-10-16 5:05 ` Rebroad (sourceforge)
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=543A52A1.2010408@bitminter.com \
--to=operator@bitminter.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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