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

Weighted-Aggregated-Attestation-API #36

Open
MoeNick opened this issue May 13, 2024 · 7 comments
Open

Weighted-Aggregated-Attestation-API #36

MoeNick opened this issue May 13, 2024 · 7 comments
Assignees
Labels
P3 Required but not over ordinary tasks

Comments

@MoeNick
Copy link
Contributor

MoeNick commented May 13, 2024

Related to #23 and #24

we should have an aggregated weighted results API which is calculated daily or twice a day. This API is a result of reading all user attestations and weighting them with voting power points and calculating the aggregated results.
More information is here: https://www.notion.so/giveth/Weighted-Aggregated-Attestation-APIs-0d7c33180e2744e5943b31f1f53d67d5

Success Criteria

  • Calculations will be made on Pairwise servers.
  • We need to divide data into 4 views by stakeholder
  • each view has a final overall ranking for every project.
  • Final number would be like: ProjectX {rankTotal} ({rankInTheirCategory})
  • APIs Requirements:
  1. Ranked Projects List and Ranked Category List in Four views:
    1. Filtered by Holders’ vote
    2. Filtered by Delegates’ vote
    3. Filtered by Badgeholders vote
    4. Filtered by Recipients’ vote
  2. The list of projects should include
    1. the logo of the project,
    2. the name of the project,
    3. The category of the project
    4. The rank of the project inside their category.
    5. a relation to RPGF Project ID
  3. The Ranked list of projects should be able to be filtered by category
  4. The list of categories should include
    1. Name
    2. Rank (based on the votes)
  5. Each service preferably has sorting and paginations for all views
  6. A final metric for each project: ProjectX {rankTotal} ({rankInTheirCategory})
@MoeNick
Copy link
Contributor Author

MoeNick commented May 13, 2024

@jainkrati I added all notion docs for this issue here.
The bad news is we should make it up and working 10th June and end up by 18th.

@MoeNick MoeNick added the P0 the site is down and all work stops, until this issue is resolved. label May 13, 2024
@mmahdigh mmahdigh assigned mmahdigh and unassigned jainkrati Jun 13, 2024
@maryjaf
Copy link

maryjaf commented Jun 18, 2024

I've tested based on this temp/api
https://pairwise.melodicdays.shop/flow/temp/api

I tested with different address and badges and it seems it works correctly and weight of each project in category is calculated correctly

Is this view is fine in point of you for this phase ? @MoeNick
https://pairwise.melodicdays.shop/flow/temp/api

@MoeNick
Copy link
Contributor Author

MoeNick commented Jun 26, 2024

We should have filtering in API as inputs based on :

  • StakeHolder (4 voter roles)
  • Category

We should have project logo
we should have ranking as whole without filtering any category.

For success criteria please go to the notion doc attached to teh isssue.

@MoeNick
Copy link
Contributor Author

MoeNick commented Jun 26, 2024

Also please lets have staging and production data separated ASAP.

@MoeNick
Copy link
Contributor Author

MoeNick commented Jul 7, 2024

Shall I wait for filtering inputs on API r we can call it done?
@mmahdigh @maryjaf

@MoeNick
Copy link
Contributor Author

MoeNick commented Jul 17, 2024

  • Badgeholders filter is important
  • Result of csv.

@MoeNick MoeNick added P3 Required but not over ordinary tasks and removed P0 the site is down and all work stops, until this issue is resolved. labels Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Required but not over ordinary tasks
Projects
None yet
Development

No branches or pull requests

4 participants