How to memory map blkindex.dat? | Bitcointalksearch.org

altcoinex

sr. member

Activity: 293

Merit: 250

Director - www.cubeform.io

To clarify, As mentioned the blk*.dat are the actual dumped blocks.
The format is:

Quote from: patvarilly on July 16, 2011, 03:29:01 PM

4 bytes: network message start (0xf9, 0xbe, 0xb4, 0xd9)
4 bytes: block size N (little endian)
N bytes: block raw data (see https://en.bitcoin.it/wiki/Protocol_specification#block)

However, the blkindex.dat is a berkely db file, not a raw dump and contains where and in which blk*.dat file the block is contained.

--edit-- Note: this applies to versions <0.8 as the format was changed.

cloudboy

hero member

Activity: 690

Merit: 501

Quote from: TierNolan on May 21, 2015, 11:38:44 AM

It follows the network protocol. They take the network serialization and dump it to disk. Unused space at the end of the file is left as all zeros.

Protocol messages have this format.

Blocks are "block" type (and all zeros) for the command.

Blocks are given here.

Got it! Thanks

TierNolan

legendary

Activity: 1232

Merit: 1084

It follows the network protocol. They take the network serialization and dump it to disk. Unused space at the end of the file is left as all zeros.

Protocol messages have this format.

Blocks are "block" type (and all zeros) for the command.

Blocks are given here.

cloudboy

hero member

Activity: 690

Merit: 501

Hi,

I want to mmap blkindex.dat to have a pointer to each CBlockIndex in the file. I see there are the 4 magic bytes at the beginning, followed by some zeroes and then the genesis block. Anybody familiar with the exact layout?

Topic: How to memory map blkindex.dat? (Read 616 times)