Author: Rick Staa, Livepeer Foundation

Funding Mechanism: RFP (Funded by Transformation SPE)

Submission URL: Closed

Winning Submission URL: Forum Post

Claimed By: RaidGuild

Track Progress: Forum Updates - Github Board

1. Purpose

Restore the Livepeer Explorer to a secure, maintainable, and high-performance state, as the current deprecated and unreliable Explorer limits visibility into the network, introduces security and stability risks, and prevents informed decision-making; recent outages, poor performance, and data quality issues make this work urgent to re-establish a trusted source of truth and enable future network and governance dashboards.

2. Outcome

Overview:

Overall success means the Explorer becomes a clean, secure, well-tested, high-performance codebase with no critical bugs, modern dependencies and a clear backlog. It delivers faster UX, a simplified data layer, and integrated voting transparency. It emerges as trusted infrastructure with a 6-month roadmap and an active maintainer team.

Key Metrics To Measure The Outcome Against:

• Resolution of existing issues in the Explorer repository.

• Degree of improvement in voting transparency based on the new voting-transparency feature.

• Degree of improvement in data quality, performance, codebase health, and security compared to the initial state.

3. Requirements

Must Have

1. A clean, maintainable Explorer codebase with unnecessary or duplicated components removed.

2. A well-tested foundation supported by automated checks and reliable build processes.

3. A simplified, efficient data-fetching layer that eliminates redundant calls and improves responsiveness.

4. All critical bugs resolved and the backlog reviewed, cleaned, and brought up to date.

5. A fully delivered voting-transparency feature connected to the correct data source.

6. Regular public progress updates throughout the engagement.

Should Have

1. A six-month maintenance roadmap plus clear contributor documentation and workflows.

2. A well-organized, clearly labeled issue board that supports ongoing maintenance.

3. A support plan with defined response and resolution timelines, including a minimum 60-day post-delivery support window.

4. Collaboration with the Foundation and advisors to align fixes and scoped enhancements with network priorities.

Out of Scope

1. Full UI/UX redesigns or new visual styles for the Explorer.

2. Major new product features beyond the voting-transparency integration.

3. Broad data-gap analyses or network-wide data mapping efforts.

4. Protocol, client, or on-chain changes required to expose entirely new data.

4. Proposal Guidelines

Your proposal must include the following in your proposal. Here is a guideline for what we are looking for: Livepeer RFP — Proposal Template

• Company Overview & Capabilities

• Experience and why you are a great fit for this work

• Milestones (with funding amount, timeline, deliverables, demo day for each)

• Outcomes

• Budget & Governance (how funds will be distributed)