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

Ranked assets component *OR* deprecate ranking #471

Open
6 tasks
idiom-bytes opened this issue Feb 22, 2023 · 0 comments
Open
6 tasks

Ranked assets component *OR* deprecate ranking #471

idiom-bytes opened this issue Feb 22, 2023 · 0 comments

Comments

@idiom-bytes
Copy link
Member

idiom-bytes commented Feb 22, 2023

Problem:

Ranked rewards were introduced but users have no ability to view how assets are being ranked. They are unable to understand how rewards are being distributed across assets and manage their farms accordingly.

Candidate solutions

  • Cand 1: Create a component or view that enables users to understand how rewards are being distributed across assets that are ranking.
  • Cand 2: "ranking" is layer of indirection adds additional complexity: (a) it's kinda hard to reason about, (b) it's significant additional complexity if we show it in FE It's harder to reason about, and (c) it is still susceptible to attack vectors.

Recommendation from Trent (May 4, 2023): cand 2

TODOs

  • Discuss, decide on cand 1 vs cand 2.

If Cand 1:

  • A "wireframe" showing how the component works
  • The component, visible and implemented inside a page
  • Users are able to understand how rewards are being distributed across the top performing assets, determined by the reward function (RF)

If Cand 2:

  • Deprecate "ranking" from df-py (easy!)
  • In weekly DF blog post, mention the change
@trentmc trentmc changed the title Ranked assets component Ranked assets component *OR* deprecate ranking May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant