Open mvadari opened 1 week ago
To save on storage space, the indexer skips meta.AffectedNodes
field. Would 'involved accounts' query need access to meta.AffectedNodes
field? I'm afraid the indexer needs to be rerun to include meta.AffectedNodes
. This may be done in the future with better storage capacity planning.
For my curiosity, can you post an example query that may benefit from the ability to query by involved accounts?
I was thinking of "involved accounts" using meta.AffectedNodes
. For example, all transactions that affect an AMM.
Got it! This type of query will be possible after the indexer stars indexing AffectedNodes
post storage capacity planning. I'll keep this issue open until then.
e.g. can I see all the transactions that touched a certain AMM? Or all the updates for a certain oracle?