Aave Treasury Data about subgraphs

[melotik]

If/when we go down the route of treasury tracking with subgraphs I think the plan will be to make it it's own schema/subgraph. Open to other opinions though

[this-username-is-taken]

Thanks @defispartan! We will revisit this when we get to the v3 subgraph.

[melotik]

Since this is different from reserves I think this should be an add on field for aave v2 and v3.

[bye43]

@dmelotik are these fields in the 3.0.0 schema? We are going to table this then till AAVE is upgraded to 3.0.0

[melotik]

No, it would be an addon field there as well. It really wouldn't make a difference if we added to the current schema as an additional field. But depends on priority

[melotik]

If we decide to go down this route of grabbing treasury data. I think we would set ourselves up much better long term to create a small schema for treasury metrics and make separate subgraphs for that. Rather than adding it onto existing subgraphs and waiting to sync.

[tnkrxyz]

@dmelotik, (and maybe @defispartan), I appreciate your guidance on a few things related to the treasury addition. Since we already track protocol side revenue, so this new field/entity will just track the actual treasury balance? Any preference between using an (optional) field of the market entity (seems making most sense to me as the balance is collected in aToken), vs a separate entity? Any other information besides balance, e.g. source, amountUSD? I suppose it/they needs to be added to daily/hourly snapshot? thx!