| Age | Commit message (Collapse) | Author |
|---|
|
aedc74d contrib: make linearize-data.py cope with out-of-order blocks (Wladimir J. van der Laan)
|
|
Make it possible to read blocks in any order. This will be required
after headers-first (#4468), so should be merged before that.
- Read block header. For expected blocks, continue, else skip.
- For in-order blocks: copy block contents directly. Write prior
out-of-order blocks if this connects a consecutive span.
- For out-of-order blocks, store extents of block data for later
retrieval. Cache out-of-order blocks in memory up to 100MB
(configurable).
|
|
Batch up to 10000 requests for a ~30x speedup.
|
|
|
|
time.
|
|
|
|
This was typically ensured implicitly by virtue of normal bitcoind
operation. Adding an explicit check provides a stronger guarantee, and
it is cheap to add.
|
|
max-file-size
|
|
Break into two steps:
* Generate hash list
* Build data file(s) from local bitcoind blocks/ directory.
This supports building one large bootstrap.dat, or multiple
smaller blocks/blkNNNNN.dat files.
|
|
linearize.py: harmonize rpcpass to rpcpassword according settings in
bitcoin.conf
|
|
|
|
Add the ability to start at a non-zero height, and allow for appending to
an existing file.
|
|
File and Link Fix.
|
