Block Store¶
Block Store keeps durable copies of blocks and their receipts. It provides historical block lookup without making the consensus state database serve as a block archive.
Dependencies and inputs¶
Block Store connects to RabbitMQ and consumes accepted-block information. In the official Compose topology it starts after RabbitMQ and Chain.
Its RPC interface supports reading blocks by ID or height, reading the highest stored block, and adding a block to storage.
Outputs and interfaces¶
P2P uses Block Store when serving blocks to peers and while coordinating block synchronization. Account History can also read stored blocks while catching up. API gateways can expose the lookup methods when Block Store is enabled.
State and consistency¶
The selected release stores blocks, receipts, and lookup metadata in BadgerDB. This is durable blockchain history, but storage does not make a block canonical. Chain performs consensus validation and fork choice.
The highest block in Block Store and the current Chain head can differ while a service is starting or catching up. A historical query can therefore be behind even when Chain itself is healthy.
If Block Store is unavailable, the node can lose historical-query and peer-serving capabilities, and services that rely on stored blocks may be unable to catch up.
Operating the service
Backup, restoration, reindexing, and storage checks are documented under Node Operators.