From: Mike Hearn <mike@plan99•net>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bootstrapping full nodes post-pruning
Date: Mon, 11 Jun 2012 22:48:36 +0200 [thread overview]
Message-ID: <CANEZrP3NKRiCHWFUeBDJLN9PzBmhFnEjAk+v+HZXOw3aeJWdeA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQ7sspfZ+aBDhCj7Y+Dzmv1ku7u4wO=VUFVcBSuuTzo6Q@mail.gmail.com>
> Actual BDB files are absolutely not deterministic. Nor is the raw
> blockchain itself currently, because blocks aren't always added in the
> same order (plus they get orphans in them)
That's true. Though if you prune up to the last checkpoint, orphans
before that point can be safely thrown away.
I wonder if swapping out bdb for LevelDB might make sense at some
point. I'm not sure how deterministic that is either though :)
prev parent reply other threads:[~2012-06-11 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 23:06 Mike Hearn
2012-06-11 15:39 ` Gregory Maxwell
2012-06-11 20:36 ` Mike Hearn
2012-06-11 20:43 ` Gregory Maxwell
2012-06-11 20:48 ` Mike Hearn [this message]
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=CANEZrP3NKRiCHWFUeBDJLN9PzBmhFnEjAk+v+HZXOw3aeJWdeA@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/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