Rootul P

> afaiu we're just waiting to cut v6.x, right? Yes. IMO we shouldn't do that until we need to merge changes that are breaking (i.e. can't be merged to main)....

That error is non-intuitive but I assume this line ``` Jul 31 10:27:23 celestia-mainnet-archive-lsn-fra-12495 celestia-appd[36070]: 10:27AM ERR failed to LoadFinalizeBlockResponse err="could not find results for height #1034505" module=rpc ``` is...

Also `v0.23.58` isn't a valid celestia-app version. I assume you're on v4.x.x or v5.x.x.

I assume this is because your `config.toml` has `discard_abci_responses = true`. If that's not the case, please re-open.

To confirm: are you getting the error for blocks that your node has synced through? The OP cites block [1034505](https://www.mintscan.io/celestia/block/1034505) which is from March, 2024. I only expect archive nodes...

@ella-quicknode can you please share: - Which version of celestia-app you're on? - What is the earliest block available? It is in the output of the `/status` endpoint. - Your...

I just tried to reproduce with `./scripts/single-node-all-upgrades.sh` but all blocks are retrievable via `/block_results` so I'm not sure how to reproduce the issue without more info. @ella-quicknode @jaguera-qn

Thanks for all the info. - Does the `/block_results` endpoint work for recent blocks and only fail on old blocks? I.e. ``` # works on recent block curl --location 'http://localhost:26657/block_results?height=6867338...

> If our nodes requires to host archival data, we need to set this flag to true? discard_abci_responses = true No. You want to set `discard_abci_responses = false` to preserve...

It still seems like the node synced through that height with `discard_abci_responses = true` so my only suggestion to overcome the error would be to sync from genesis with `discard_abci_responses...