Milestones
List view
Turn the research into accepted, actionable follow-on work. Incorporate the public comment window, weigh feedback from the Review Team and community, and finalize the prioritized backlog. Output: - Final prioritized backlog - Public feedback summary - Updated recommendations where needed - At least 3 clearly scoped follow-on items suitable for retro grants or future RFPs
Due by July 3, 2026•2/2 issues closedTranslate the findings into a design-ready brief for a minimum competitive self-custody staking experience. Output: - Design brief with wireframes or annotated flow diagrams - Instrumentation plan - Initial prioritized backlog
Due by June 24, 2026•3/3 issues closedComplete the competitive teardown and identify Explorer gaps. Output: - Competitive teardown - Explorer gap specification - Annotated screenshots / flow notes
Due by June 16, 2026•3/3 issues closedConfirm the research plan, benchmark set, comparison dimensions, and access assumptions. This includes confirming which centralized exchanges and decentralized staking products will be analyzed, what scenarios will be measured, and how findings will be captured. Output: - Kickoff / audit plan - Confirmed competitive teardown scope - Confirmed comparison matrix - Confirmed methodology and access constraints
Due by June 8, 2026•6/6 issues closed## Main Goals - Add Option to Expand or Separate Panels for Easier Data Viewing - Provide more detailed orchestrator info - Add the number of active gateways to usage graphs - Add i18n - multi-currency diversity
Due by August 3, 2026•0/4 issues closed## Main Goals - Show annotation on historical performance score graph for orchestrators - Add ability to export orchestrator history as CSV - Ensure overview data is fetched on-chain - Add gateway tab to Explorer
Due by July 6, 2026•2/4 issues closed## Main Goals - Upgrade Apollo to v4 - Scan current libraries for version bumping - Tackle any security issues (likely involves an SSR refactor) - Extend Voting Transparency to Governance page
Due by June 8, 2026•1/2 issues closed## Main Goals - Feature request house cleaning - There are numerous old feature requests that still need to be closed, sorted to a later milestone, or included in this milestone - Small features will be tackled in this milestone; large features will get sorted into future milestones - Tackle any features or bugs that are not completed during Explorer Maintenance - Milestone 5 - Ensure the migration from RPC data to subgraph data is completed - Add Sepolia contracts for testing (big feature)
Due by May 11, 2026•3/11 issues closed## Ongoing Monitoring & Reliability - Continuous monitoring and alerting via pino logs and BetterStack (from milestone 3). - Automated CI pipelines to catch regressions before deployment (from milestone 2). - Strict linting and pre-commit checks to maintain code quality (from milestone 2). ## Bug Response Commitment - Critical bugs acknowledged within 24 hours. - Resolution of critical issues within 3 business days whenever technically feasible. - If not technically feasible, this will be communicated quickly. - Non-critical issues triaged and scheduled according to impact and severity. ## Community Transparency - Biweekly progress updates shared on the Livepeer forum during the 60-day maintenance window. - Demonstrations of any fixes or improvements presented in Livepeer community calls when relevant. ## Scope of Maintenance - Closing out any new bug reports. - We will collaborate with external contributors if PRs are raised by the broader community. - Continuous attention will be paid to whether fixes or changes move closer towards the overall goal of eliminating known limitations and closing data gaps.
Due by April 10, 2026•29/29 issues closed### Main Tasks - Conduct final QA sweep. - Update any documentation as needed. - Tackle prioritized backlog items identified throughout the engagement. ### Deliverables - Polished, stable Explorer ready for long-term maintenance - Updated documentation ### Demo Day - Full walkthrough of stable explorer - Updated documentation
Due by January 30, 2026•14/14 issues closed### Main Tasks - Resolve or close all bug issues. - Remaining issues are older than 2023, and are likely stale. These will all be checked. - Close stale feature issues. - Resolve feature issues that RaidGuild, the Foundation, and Advisory Boards have agreed to complete (from milestone 1). - Implement governance vote indexing via The Graph (current PR is using an RPC). - Finish any incomplete frontend components. - UI/UX adjustments for clarity and responsiveness. - Integrate monitoring/alerting stack (e.g., pino + BetterStack or equivalent). ### Deliverables - Monitoring dashboard - Email alerts - All bug issues closed out or resolved - Stale feature issues closed out - Agreed upon feature issues resolved - Improved logging - Voting Transparency feature ### Demo Day - Voting Transparency feature - New minor features, if any - Monitoring dashboard
Due by January 2, 2026•27/27 issues closed## Main Tasks - Continue to less critical bug fixes. - From preliminary audit, this is issues #256, #244, and #236. - Implement stricter linting, Husky pre-commit checks, and CI pipelines with new unit & integration tests. - Optimize data queries and frontend rendering for improved load times. - Migrate core data fetching from RPCs to The Graph subgraph. - Ensure compatibility with existing UI and new infra. ## Deliverables - Automated pipelines - Unit and integration tests - Performance benchmarks met - Less critical issues resolved - Data layer migration to The Graph ## Demo Day: - Improved performance - CI/CD walkthrough - Bug fixes - Brief overview of new data layer using The Graph
Due by December 1, 2025•18/18 issues closed## Main Tasks - Remove unused or duplicate code. - Delineate and resolve critical bugs. - From preliminary audit, this is issues #313, #307, and #304. - Upgrade runtime to Node v22. - Upgrade other dependencies if runtime upgrades or security vulnerabilities demand it. - Add retry logic and fail-safes for reliable data normalization. ## Deliverables - Clean, stable codebase baseline - Critical bugs resolved - List of prioritized issues and features - Runtime and dependency upgrades ## Demo Day - Frontend stability after upgrades and new data layer - Critical bug fixes - Issues and features 4-month roadmap
Due by November 7, 2025•8/8 issues closedRelease the new voting transparency feature to the community.
Due by May 30, 2025•1/1 issues closed