Original issue: tendermint/tendermint#9943

Problem definition

We do not have a complete picture on how our users as well as different CometBFT components interact with storage. We therefore need to collect all the relevant use cases for the storage backend. While issue #67 captures internal storage use cases, we need to understand how CometBFT storage is used not including CometBFT itself:

• Who are the main users and how are they using CometBFT storage (validators, sentries, full nodes, relayers, etc., but with specific emphasis on what people are doing with full nodes).

• What are their pain points with regards to storage (usage, querying time, impact from unavailable data) ?

• What types of queries do they typically run agains CometBFT?

• What RPC endpoints are relevant? Are all fields returned by the endpoint of importance?

• How big is their data (block, genesis file)?

• Do they enable data indexing ?

DoD

• A list of different users, their typical usage patterns and issues with regards to CometBFT storage.
• Make sure we understand what types of data they access and whether and how we could allow them to configure individual storage usage.