Issue Details

Number: 27085
Title: Failing to fetch `cfheader` corresponding to block header in `headers` message
Description:  Occasionally when I receive a `headers` message on the p2p network, and attempt to fetch the `cfheader` that corresponds to a block header inside of a `headers`, i get this error message inside of my `debug.log` >2023-02-07T16:47:15Z [net] Failed to find block filter hashes in index: filter_type=basic, start_height=150, stop_hash=3ca9030aeb6c2721cfbab0116b8d96e2d3c7e00738238010e0bc622566dc2aed **Expected behavior** I should be able to fetch a `cfheader` for a block after the block has been relayed to me over the p2p network via `headers` p2p message.  **Actual behavior** It fails to fetch the `cfheader` that corresponds to the block. **To reproduce** I am unable to reproduce reliably, but this does occur ~1/5 times when running test suites on bitcoin-s. **System information** 24.0 (although i have seen this behavior for awhile and believe this issue exists in older versions of `bitcoind`) The OS/CPU arch does not seem to be a factor in this bug. I can reproduce on Linux/mac machines with older/newer versions of bitcoind I've attached the `debug.log` for my `bitcoind` instance. The block hash in question is `3ca9030aeb6c2721cfbab0116b8d96e2d3c7e00738238010e0bc622566dc2aed`. [debug.log](https://github.com/bitcoin/bitcoin/files/10714034/debug.log) This is related to: https://github.com/bitcoin-s/bitcoin-s/issues/4976
URL: https://github.com/bitcoin/bitcoin/issue/27085
Closed by

Back to List