Skip to content
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

Interactive strategy allocation history #15

Open
micahalcorn opened this issue Dec 1, 2022 · 1 comment
Open

Interactive strategy allocation history #15

micahalcorn opened this issue Dec 1, 2022 · 1 comment
Labels
enhancement New feature or request P4 Something to consider, a feature request that we may not pursue

Comments

@micahalcorn
Copy link
Member

Add a slider at the top of the allocations module to allow users see historical allocations going back 365 days. By the time we implement this, we likely would have stopped using the old Curve (non-Convex) strategy, so we shouldn't need to add it to the list. We may need to account for prior versions of the current strategies depending on when they were upgraded (e.g. Aave).

When the slider is moved, the strategies should remain in the same order rather than rearranged. (see #10)

Screen Shot 2022-12-01 at 8 18 01 AM

@micahalcorn micahalcorn added enhancement New feature or request P2 Small number of users are affected, major cosmetic issue labels Dec 1, 2022
@micahalcorn micahalcorn modified the milestones: Sprint 40, Sprint 41 Dec 1, 2022
@micahalcorn micahalcorn added the planned In-scope at the beginning of the sprint label Dec 8, 2022
@micahalcorn micahalcorn modified the milestones: Sprint 41, Sprint 42 Dec 15, 2022
@micahalcorn
Copy link
Member Author

micahalcorn commented Dec 20, 2022

I think we'll let this project take a backseat to Proof of Yield. This would be a fun one to build but it's going to require a lot of work and it does a worse job answering the question of how the historical APY was generated. It's better to just answer literally what each strategy's contribution to the APY was rather than implying it based on prior allocations.

@micahalcorn micahalcorn removed this from the Sprint 42 milestone Dec 20, 2022
@micahalcorn micahalcorn added P4 Something to consider, a feature request that we may not pursue and removed P2 Small number of users are affected, major cosmetic issue planned In-scope at the beginning of the sprint labels Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P4 Something to consider, a feature request that we may not pursue
Projects
Status: To-do
Development

No branches or pull requests

1 participant