GIVfi Subgraph

[divine-comedian]

We'll need to be able to relay indexed information from the GIVsavings contract to the dApp. We'll probably need a subgraph but I could be wrong.

Tagging @KurtMerbeth and @aminlatifi to keep you in the loop.

A vault (GIVsavings account) is defined by the chain it is on and it's underlying asset (ETH, DAI etc.... A vault only manages 1 asset/token
We will need to relay this information to users:

• Current & Historical APYs of a given vault
• Value of user's net deposits ( total balance - interest earned) for each vault
• Value of user's yield earned (total balance - net deposits) since last withdrawal or vault inception
• Historical information of user's withdrawals and deposits

[divine-comedian]

Need to find a way to aggregate the user's total balance from all GIVsavings vaults on all chains to show the user their total balance in GIVsavings

[divine-comedian]

We will write a new subgraph service specifically for GIVfi - starting scope will be GIVsavings.

Test deployments should be up my mid next-week

@mateodaza has the contracts and will begin writing the subgraph files
should converse with @aminlatifi but we think it should be a separate file to reduce complexity of existing subgraph

test deployment will probably be optimism-goerli and production will be optimism mainnet