Q1 2026

Q2 2026

Q3 2026

Q4 2026

Ecosystem Roadmap

Understand the existing Livepeer system: map how decisions actually get made (vs. how stakeholders believe they're made), identify where power and narrative ownership currently sit, and surface the story across Foundation, Inc, Gateway and contributor touchpoints

In Progress

Foundation - Narrative Readiness

Admin Team

<h2>Purpose</h2>What is the specific business problem that this solves? How does this align with and advance the vision? And why should we be working on this now?Livepeer needs to define its core opportunity which can form the foundation of a GTM effort.Since its launch in 2017, Livepeer’s mission has been to offer the world’s open video infrastructure, building a respected and trusted brand rooted in decentralized video technology enabled by cryptoeconomic primitives.More recently, Livepeer has expanded into AI through multiple ecosystem initiatives, but without a dedicated GTM effort to unify them around a clear network value proposition. Defining the core opportunity now is necessary to align these efforts, focus resources, and prevent further fragmentation as the ecosystem grows.<h2> Outcome</h2>What does overall success look like in one paragraph? And what are some of the tangible key results that the submissions should focus on?Success means delivering a detailed market intelligence report which can be used for lead generation.Building on detailed interviews with prospective customers, the report should equip the Livepeer ecosystem with a clear overview of the market landscape and a breakdown of ideal customer profiles (ICPs) with clear value propositions for each.All of the work should tee up the core teams behind the Livepeer network’s GTM. For Network ProdEng, the report should provide direction for core requirements and competitor benchmarking. For Livepeer Marketing, it should give clear ICPs to target. For BD, it should provide a pipeline of potential customers and the basis for a sales deck. Key Metrics To Measure The Outcome Against:<ol><li>Engagement from content pieces published</li><li>Number of new customer opportunities identified</li><li>Total number of new customer interviews</li><li>Leads generated by the report</li></ol>

Foundation - Map Market Landscape

(November → February) Output: A dashboard with an overview of core network data (aligned with Cloud SPE). To Ship: Gateway audit; automated network testing and visibility; metrics collector; network-wide orchestrator data dashboard. Enables: Dashboard overview with key network data; gateway manager dashboard with SLA configuration.Features &amp; User Stories<ul><li>Network DataAs a network user, I can see an overview of core metrics</li><li>NaaP PlatformAs a network user, I can understand what the NaaP Platform is and how to get involved</li></ul>

NaaP Epic 1: Foundational Metrics & Platform

<h2>Purpose</h2>What is the specific business problem that this solves? How does this align with and advance the vision? And why should we be working on this now?Livepeer has acute pain points around current capital. On chain liquidity is low, leaking value of LPT holders through high slippage. Inflation is high against external benchmarks, which acts as a barrier to new participants. The treasury is not accumulating new LPT and the current treasury is not actively deployed and so does not generate any yield. We need to address all of this in a holistic way now, as actions in one area can have unintended second-order consequences if not managed carefully.<h2> Outcome</h2>What does overall success look like in one paragraph? And what are some of the tangible key results that the submissions should focus on?Overview:Overall success is creating a working group that collaborates to assess the ecosystem holistically, enabling clear decision-making and actively managing ecosystem capital through more strategic deployment.Key Metrics To Measure The Outcome Against:<ul><li>Improvements in liquidity depth and market efficiency.</li><li>Reduction of treasury concentration risk and clearer capital allocation strategy.</li><li>Measurable progress toward sustainable inflation and data-driven utility models.</li></ul>

Completed

Transformation SPE - Improve Capital Management

<h2>Purpose</h2>What is the specific business problem does this solve? How does this align with an advance the vision? And why should we be working on this now?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.<h2> Outcome</h2>What does overall success look like in one paragraph? And what are some of the tangible key results that the submissions should focus on?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:<ul><li>Resolution of existing issues in the Explorer repository.</li><li>Degree of improvement in voting transparency based on the new voting-transparency feature.</li><li>Degree of improvement in data quality, performance, codebase health, and security compared to the initial state.</li></ul>

Raidguild RFP - Upgrade Explorer

<h2>Purpose</h2>What is the specific business problem does this solve? How does this align with an advance the vision? And why should we be working on this now?Lack of trusted, network-wide performance and demand metrics makes it difficult to assess reliability, surface bottlenecks, or confidently onboard real-time AI workloads. Without clear visibility into latency, success rates, capacity, and workload behavior, Livepeer cannot demonstrate production readiness, establish meaningful Service Level Agreements (SLAs), or give builders confidence to deploy real workloads.To advance the real-time AI vision, Livepeer must first measure what matters by establishing unified, trustworthy network observability. A shared data foundation enables consistent SLA tracking, informs scaling and incentive decisions, and gives operators, gateways, and developers a clear, objective view of network performance as demand grows.<blockquote>Prior work: Builds on <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/shtukaresearch/livepeer-data-geography">ecosystem research</a> highlighting fragmented network data and the need for unified, network-wide observability.</blockquote><h2> Outcome</h2>What does overall success look like in one paragraph? And what are some of the tangible key results that the submissions should focus on?Overall success is when Livepeer has a unified, trustworthy observability foundation for real-time AI and video workloads—defined by clear metric schemas and open data pipelines that aggregate network-wide performance and demand data into a single, queryable source. Orchestrators, gateways, and the community can access consistent real-time and historical views across key metrics, enabling analysis, insight, and action. This foundation directly enables SLA scoring, informed orchestrator selection, and continuous reliability improvements as demand grows.Key Metrics To Measure The Outcome Against:<ul><li>Unified Metrics Coverage: Number of core performance and demand metrics defined in a standardized schema and made available network-wide.</li><li>Data Source Integration: Number of distinct network data sources integrated into a unified aggregation layer and exposed through documented access paths.</li><li>Observability Completeness &amp; Reliability: Defined indicators showing freshness, completeness, and consistency of network telemetry (e.g. data latency, missing dimensions, ingestion success rates).</li><li>Reproducible Test Load Results: Availability of standardized test load execution producing repeatable, independently verifiable measurements for key SLA metrics.</li></ul>

Cloud SPE - Observable Network Data

<h2>Purpose</h2>Which specific business problem does this solve? How does this align with and advance the vision? And why should we be working on this now?Livepeer’s protocol secures meaningful on-chain value and increasingly supports real-time AI workloads that depend on reliability, safety, and predictable upgrades. Today, vulnerability response, protocol maintenance, and core development rely on limited shared resources, slowing iteration and making it harder to proactively evolve the protocol as the network grows.To strengthen Livepeer’s long-term foundations, the network needs a dedicated, always-available protocol development and security function with clear ownership, coordinated workflows, and the ability to respond quickly to issues, ship safe upgrades, and maintain essential infrastructure such as a public testnet. Establishing this structure now ensures the protocol remains secure, resilient, and scalable as demand increases.<h2> Outcome</h2>What does overall success look like in one paragraph? And what are some of the tangible key results that the submissions should focus on?Overall success is when Livepeer operates a clearly defined, continuously supported protocol development and security function. Immunefi response and upgrade workflows are formalized and resourced, a stable public testnet is launched for validation, and a lightweight triage and release pipeline is operating and used continuously ship <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.notion.so/Protocol-Engineering-Work-Completed-Under-Prior-Livepeer-Grants-2c6660222d0880349a36f0c6f27bd0ce?pvs=21">prioritized backlog upgrades</a>. This creates a predictable, accountable foundation for safe protocol evolution as the network scales into transcoding and real-time AI workloads.Key Metrics To Measure The Outcome Against:<ol><li>Immunefi Response Readiness: A defined and resourced workflow enabling timely triage and patch preparation.</li><li>Public Testnet Preparedness: A stable testnet launched or fully scoped with a clear operational plan.</li><li>Triage &amp; Release Pipeline: A lightweight prioritization and release process established and in active use.</li><li>Backlog Delivery Velocity: One or more prioritized backlog features or patches progressed through triage → testing → deployment per release cycle.</li></ol>

Establish a Protocol Security SPE (Sidestream)

<h2>Purpose</h2>Livepeer needs a new meme (realtime? realtime AI?). With Livepeer’s new focus on realtime AI &amp; video, the creation and focus of the Daydream community and product, and the development of new gateway services (Streamplace, Frameworks, Embody), each part of the Livepeer story needs to be coherently weaved together.The market for video is exploding as it merges with AI. This opportunity is to lead a team dedicated to advancing the Livepeer brand, connecting the network product, token and ecosystem. As both a compute network and specialised video infrastructure, Livepeer needs to communicate its value propositions to new customers and investors.<h2> Outcome</h2>By the end of this 6-month period, Livepeer will have formed its own category and positioned itself as a market leader in providing specialised infrastructure for real-time video and AI. It will have identified its market and have the foundations of a go to market, which can be taken forward in collaboration with other teams.Some key metrics include:<ol><li>Number of inbound, qualified developer leads</li><li>Social followers and/or social engagement</li><li>Discord members increase</li><li>Discord member engagement</li></ol>

Under Review

Coming Soon

Drive AI-centric Livepeer Brand

Objective:Define what "quality participation" means for delegators and orchestrators, how it's measured, and how emissions/treasury incentives can be tuned to reward it.Problem Statement: Today emissions reward participation without distinguishing quality. Passive stake, dormant delegators, and underperforming orchestrators all receive the same rewards as active, high-value participants. This is a tax on everyone else. ScopePhase 1 — Define<ul><li>What is "active" vs. "passive" participation for delegators?</li><li>What is "quality" for orchestrators? (uptime, performance, pricing, adoption of best practices?)</li><li>How is each measured on-chain vs. off-chain?</li><li>What are the known limitations and edge cases?</li></ul>Phase 2 — Design<ul><li>What mechanisms exist to reward quality? (protocol changes, treasury programs, reputation systems)</li><li>What are the tradeoffs of each approach?</li><li>How do we handle "vampire nodes," dormant stake, and inactive orchestrators?</li></ul>Phase 3 — Propose<ul><li>Draft recommendations for community discussion</li><li>Identify what requires a LIP vs. a treasury program vs. social norms</li></ul> Key Questions to Answer<ul><li>Can quality be measured purely on-chain, or do we need off-chain signals?</li><li>Is this a protocol change or can it be addressed through treasury incentive programs first?</li><li>Who defines the quality criteria — Foundation, community, or a working group?</li></ul> Out of Scope: Changing overall inflation rate (covered by other emissions LIP’s) Success Criteria: Community-agreed definition of active participation and quality participation + at least one concrete mechanism proposed for implementation in H2 2026

Tackling Free Riding & Participation Quality

Establish norms, processes, and accountability mechanisms for how the onchain treasury is allocated — ensuring capital flows to highest-impact ecosystem activities. Problem Statement: Now that the treasury rate cut is back online we need a prioritization criteria for the deployment of funds, a formal framework for projects where resource allocation is the key decision point, and a broader accountability framework that alleviates previous community concerns about the ROI of deployed funds Scope<ul><li>Define what treasury funds should and shouldn't be used for - eg. align treasury allocation priorities to Roadmap items</li><li>Establish norms and an evaluation framework for proposals (if needed)</li><li>Establish a process for use of RFPs, such that funds can be secured before RFP teams are chosen</li><li>Set performance, transparency and reporting norms for funded projects</li></ul> Key Questions to Answer<ul><li>How are Roadmap items suggested and determined?</li><li>What are the real differences between "Roadmap-aligned" vs. speculative proposals?</li><li>What should be used to evaluate proposals?</li><li>How can an RFP process work in advance of deployed funding given the onchain execution of the treasury?</li><li>What does performance, transparency and reporting look like post-funding?</li><li>What group should be engaged to best answer and propose action on the items above?</li></ul> Out of Scope: Size of treasury reward cut rate itself (separate LIP can be further created if needed) Success Criteria: Community-ratified norms published; new treasury proposals evaluated as per norms, future funded projects deliver as per norms

Onchain Treasury Allocation Improvements

(March → April) Output: An MVP of the NaaP platform to prove the Livepeer network can perform popular workflows, at low latency, with the needed scale, at market-best prices, without a large amount of technical overhead for app developers. To Ship: Shell App Foundation; ****dashboard overview; shared UI components; a staging and production infra that is open to community to build, test, and deploy Solutions to the NaaP; successful integration with design partner (Daydream). Enables: Live NaaP platform with Solutions Providers marketplace; community ability build and deploy custom solutions; hypothesis-driven development approach.Features &amp; User Stories<ul><li>(1) Network OverviewAs a network user, I can see the network overall metrics using overview dashboardAs a network user, I can get an overview of the pricing of different pipelinesAs a network user, I can track the usage of top pipelinesAs a network user, I can easily query network data to see more detailed performance metrics from the network </li><li>(2) Developer APIAs an app developer, I can create an API key per billing provider.As an app developer, I can see my overall usage tracking from all signersAs an app developer, I can see my usage tracking per signer (with breakdown of project, and api key)As an app developer, I can view and search list of models that supported by the network.As an app developer, I can see my usage tracking per model (with breakdown of signer, project, and api key) </li><li>(3) Community HubAs a network user, I can get feedback on new community-built plugins or featuresAs a network user, I can request new community-built features to the network product </li><li>(4) Capacity PlannerAs a Service Provider or App Developer, I can request GPU capacity over an allotted time period at a given price.As an Orchestrator, I can soft commit and respond to a GPU capacity request.</li></ul>

NaaP Epic 2: MVP NaaP Platform Launched With Core Features

<h3>Epic 3: First Solutions Published on NaaP Platform (April → June)</h3>Outcome: A successful program to incentivise and integrate ~3 Solutions Providers and their APIs to the network, tested and owned by members of the Livepeer community.To Ship: Set up scalable way to integrate first solutions into the NaaP platform; work with 5 new Solutions Providers to scope needs; establish way to track usage on a public dashboard per Solution Provider. Enables: Developers can build applications directly from NaaP integrating with multiple Solutions Providers, validation of the concept of community-built plugins. [WORK IN PROGRESS] Features &amp; User Stories<ul><li>Coming Soon</li></ul>

NaaP Epic 3: First Solutions Published on NaaP Platform

Help Center

livepeernetwork

Beyond

Seeking Applications

Backlog

Next up

Done

A Roadmap for the Network Product to include future community opportunities and plugins