...
The block data should be stored in an instance of RSpace- or at a minimum in an LMDB store - and there should be a mechanism to query the block data. DApp developers can use a read-only node (unbonded validator) for the purposes of serving up the blockchain data. A gRPC API will provide a mechanism to query the block data in a fashion similar to GraphQL.
There is a desire to store the Rholang terms in an RSpace instance - Medha to get more details on what the specific use cases are for querying the blockchain. Will ask David Currin, Kevin and other folks via Telegram. The problem can't be simply that they want to look up block id's, there must be specific pieces of data that they are interested in.
What are the various kinds of queries that people want to run in the blockstore? We want to organize the the store in such a way that scanning the entire corpus is as fast as possible, or retrieving the desired data points as fast as possible.
If they have particular contracts that they are interested in, they run a node that targets specific contracts or wallet addresses, and the node can keep track of the events that occur in the transaction stream that affect the wallet address, and log those separately as desired. Which enables them to specifically target their dApps traffic. Generate a separate log that is a subset of the traffic.