aave / aave/protocol-subgraphs
E-Mode Parameters Incorrectly Tracked on V3 Subgraph
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 150
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
Polygon V3 subgraph is returning parameters from eModeCategories that do not match onchain values.
Example:
{
emodeCategories{
id
ltv
liquidationBonus
}
reserves(where:{symbol: "USDC"}){
eMode{
id
ltv
liquidationBonus
}
}
}
Onchain query for E-Mode category 1 returns different parameters.
Potentially the event schema may have changed in Aave v3.2 leading to parameters updates that are not handle.
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
Start by comparing the emodeCategories and reserves query results with the linked onchain query for E-Mode category 1. Inspect the Polygon V3 subgraph's event handling for parameter updates, especially the possible Aave V3.2 schema change; done means indexed values match the onchain values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100