Support query historical states that is pruned

[yihuang]

Summary

Say the states between 100 and 200 are pruned, when trying to query state at 110, we can replay the blocks between 100 and 110 based on the state 100 to get the state 110.

This may allow user to use some prunning settings, while keeping the ability to query all historical states, a trade-off between db size and query performance.

Problem Definition

Proposal

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[tac0turtle]

Personally the best solution is to stream the data elsewhere. Not sure we need to add more intricate logic here

[alexanderbez]

This is not a good solution. This is why we have archive mode (i.e. no pruning). Disk space is cheap. Query against an archive node or stream your state to an external DB.

Are you Ok with me closing this?

[yihuang]

yeah, I guess it's too complicated, only little to gain.