Pool Burn and Mint refactor + user and pool entity refactor #358
Conversation
| type User { | ||
| id: ID! # user address | ||
| # Entity for tracking user activity and positions in specific pools | ||
| type UserStatsPerPool { |
There was a problem hiding this comment.
a user can have activity on multiple pools, so it's best to have an entity per ID where ID = userAddress_poolAddress_chainId
There was a problem hiding this comment.
so previously there was a single entity for all pools on all chains and now it is entity per pool per chain right?
we should just make a note to aggregate all of these different entities for same user address when swapping out previously used entity for the new ones (if relevant)
There was a problem hiding this comment.
previously the entity didn't have a pool-specific field. So basically all the stats would be from all pools on aggregate
I think separating and having a user entity per pool per chain allows to have more granularity that i'm almost certain that will be useful for metrics
| } | ||
| } | ||
|
|
||
| /** |
There was a problem hiding this comment.
grouped here pool loading logic
| @@ -0,0 +1,164 @@ | |||
| import type { UserStatsPerPool, handlerContext } from "generated"; | |||
|
|
|||
| /** | |||
There was a problem hiding this comment.
load or create user entity
There was a problem hiding this comment.
module that is used in both pool mint and pool burn event handlers, because they basically share the same logic
2 participants
Implements: