Feat: Allow using txindex with pruning #35240

Please describe the feature you'd like to see added.

Use case: I run an indexer but only care about blocks 30 days and newer.

I need to use -txindex but can't use pruning because they are incompatible and node refuses to start if both are set.

Except.. they are not really as far as I can understand. AI explained it like this:

• txindex is a pointer to a raw block in file
• pruning deletes the whole file
• thus there is a fundamental issue that we end up with pointers pointing to deleted data

But for my use case this is completely irrelevant. Indexer will initially index the 30 days, then index from tip. Blocks older than 30 days will never be accessed again so the fact that the underlying file was deleted and txindex gracefully fails is completely fine.

So it seems to me the enforcement is essentially artificial and this could be allowed for people who want it and understand the consequences. Obviously can't change the current behavior but could hide it under extra force flag.

Hopefully the information is correct, otherwise I'd gladly be educated.

If you are only interested in a small subset of transaction ids that map to a block hash, you can just keep track of them in a wallet, or externally. Then, use the getrawtransaction block hash option.

I'll look into it, ty.

I'm not interested in a small transaction so can you fix it for a better one

I want to see the balance and functionality