Bitcoin full node and query server

Sep 11, 2025

View in context in the libbitcoin Slack #general mirror.

R
rose16:41
Hello, I'm running libbitcoin-explorer with a local libbitcoin-server. Both libbitcoin-explorer and libbitcoin-server are version 3.8.0. I'm able to fetch the block height 848141 (using bx fetch-height), so it seems the explorer and server are connected correctly and the server is reading from the blockchain datastore. However, when I run "bx fetch-history 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz" it returns: transfers "", and it should return more detailed info per https://github.com/libbitcoin/libbitcoin-explorer/wiki/bx-fetch-history. Do I need to re-index the blockchain datastore? Perhaps there is some indexing missing? The entire datastore directory is 918GB, so I suspect it is fully synced and indexed already... but I'm probably missing something. Any help is appreciated!
evoskuil11:41
If the first snapshot didn’t complete then there is no snapshot to recover to. If a second or later snapshot failed, then there will be /secondary directory and no /primary directory, and startup will recover from /secondary. The final step of a snapshot is to rename the snap to /primary, which is a file system atomic operation. So if it’s there it’s complete, if it isn’t then /secondary is used.
(edited)