-
Notifications
You must be signed in to change notification settings - Fork 0
Restructuring, rebaseOpt In/Out, Financial Statement #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- start working on the financial statement - implement etl for the vault
…tement records remove txHash since it is inaccurate - multiple txs exist per block - we're storing by timestamp/block
switch some floats to bigint apy was using some incorrect date calculations perf to run everything is around ~25-30 minutes on my wifi
|
@shahthepro can you take a look at it? You can check the graphql endpoint here: https://squid.subsquid.io/origin-squid/v/v6/graphql |
Yeah, started looking at it yesterday, so far looks good to me, will approve once I'm done with a few tests in a bit :) |
shahthepro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question about Vault's ETH holding assumptions. Other than that, looks good to me
…to represent the 'Token Supply' liability which i forgot
|
I'm going to remove the FinancialStatement object entirely and create it in the view instead. |
Uh oh!
There was an error while loading. Please reload this page.