livepeer / livepeer/grants

[Open Livepeer Network] Voting history for Orchestrators in the Livepeer Explorer - PYOR

Open
#248 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
42
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Application by: _scyther13

What is your project, and what problem does it solve?

The PYOR team proposes the following enhancements to the current Livepeer Explorer to complete the RFP:

  1. Implement a Voting Profile Dashboard for each orchestrator within the 'Orchestrator' section of the Livepeer Explorer.
  2. Include a comprehensive list of proposals voted on by each orchestrator within their profile.

Link to public GitHub repo (if applicable)

Link to demo website (if applicable)

Not applicale, PYOR website: https://www.pyor.xyz/

Please describe in more detail why this proposal is valuable for the Livepeer ecosystem

These two features will enhance transparency in an orchestrator's governance and treasury voting activities, providing delegators with valuable information. This will enable delegators to make more informed decisions when selecting nodes for staking.

Please describe in details what your final deliverable for this project will be.

The project's Final deliverables are:

  1. Add a Macro voting history dashboard to the orchestrators's section of Livepeer Explorer.
  2. Add a voting history subsection in each orchestrator's profile on Livepeer Explorer.

How will this deliverable benefit the Livepeer ecosystem?

These two features will enhance transparency in an orchestrator's governance and treasury voting activities, providing delegators with valuable information. This will enable delegators to make more informed decisions when selecting nodes for staking.

Please break up your development work into a clear set of milestones

NumberDescriptionDeliverableAmountStart DateEnd Date
2

-> Iterate on UI designs according to the feedback from the team and finish integration of Data dashboards in Livepeer explorer.

-> By the end of second milestone we will finish both the dashboard mentioned in application.

-> By 09/23/2024 we will finish on our dashboard integrations. Last week will be for any changes and feedback iteration.

$6,250.00September 2, 2024 UTCSeptember 30, 2024 UTC
1

-> Data Identification and data pipeline creation.

-> UI for dashboard design.

By the end of first milestone we will provide a doc containing our final data identification, methodology and pipeline as well as Draft 1 of UI design to Livepeer team for the feedback.

$6,250.00August 19, 2024 UTCSeptember 2, 2024 UTC

What is the total amount requested (in USD)?

12500

Specify your team's long-term plans to maintain this software and upgrade it over time

-> Data source and pipeline maintenance as well as any additional frontend efforts (by the agreement of both parties) will be provided for 12 months.

Please describe (in words) your team's relevant experience, and why you think you are the right team to build this project. You can cite your team's prior experience in similar domains, doing similar dev work, individual team members' backgrounds, etc.

PYOR is a crypto research and analytics company backed by Coinbase Ventures and Castle Island Ventures.

We work with institutional investors and protocols to answer the most critical business questions using on-chain data. Some of our previous contributions include:

  1. Institutional investors like Ribbit Capital and M31 Capital.

  2. We worked with ICP to build a governance participation reward dashboard: https://x.com/DFINITYDev/status/1802481631883571400

  3. We worked with Compound to create a v3 Dashboard which had a Yield and fees simulator as one of the core features: https://app.pyor.xyz/compoundv3/supplier

  4. We have built a comprehensive analytics dashboard for Eigenlayer: https://app.pyor.xyz/eigen-layer

  5. We are currently working with Arbitrum to analyze the grant efficacy of the LTIPP program and with Cosmos to build a web front for a partial security set.

Who is your target user group? How do you plan on getting your users to use this?

Target users for these features are major 2 user groups:

  1. Delegators
  2. Orchestrators

Once finished we will update these user groups via Discord community update. Also(if permission given) we will announce details for these features on our twitter handle and via Livepeer twitter handle.

How did you learn about the Livepeer Grants Program?

personal research

Was this project started at a hackathon or another web3 event? Which one?

Not relevant

Please include any additional information that you think would be useful in helping us to evaluate your proposal.

For all the micro details on features, their current UI concepts and navigation information please refer to this document: https://invincible-drink-c85.notion.site/Voting-history-for-Orchestrators-in-Livepeer-Explorer-Feature-requirements-document-f45945f540ea47aba151e426bd8a16e8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or code entry points are identified. Start by locating the Livepeer Explorer's Orchestrator section and reviewing the proposed data identification and pipeline work before assessing the dashboard integration. Done means an orchestrator voting profile and a comprehensive voting-history dashboard are integrated and usable.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, data, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.