aave / aave/protocol-subgraphs
Inconsistent query results for AAVE positions at fixed blockNumber
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 150
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
I’m querying the AAVE subgraph to fetch all positions at a specific blockNumber. However, I’ve noticed that the query results are inconsistent across repeated requests. Each time I query, I receive a different subset of positions.
When I aggregate the results across multiple queries, it takes about ~20 requests before the set of positions stops growing.
Questions:
-
Can the final aggregated set be considered complete?
-
Is this inconsistency caused by missing data on individual nodes?
-
Is this behavior expected/unavoidable when querying the subgraph?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. Start by reproducing the AAVE subgraph query at the same fixed blockNumber across repeated requests and compare the returned position sets. Done means establishing whether the aggregate can be considered complete, whether node data is missing, and whether the inconsistency is expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100