Livepeer FrameWorks SPE: Pilot phase
Author(s): The MistServer Team
Contact: developers@mistserver.org
Abstract
The FrameWorks SPE proposes to strengthen the Livepeer protocol by bridging the gap between transcoding infrastructure and real-world media applications.
This includes:
- Providing dedicated engineering resources to ensure stability, feature enhancements, automated testing and a clear & complete documentation.
- Providing onboarding and infrastructure support for teams building on Livepeer.
- Operating an independent, Livepeer-powered E2E media pipeline that validates new transcoding features in real-world deployments.
By focusing on low operating costs, easy integration and strategic partnerships, FrameWorks aims to provide a viable, scalable alternative to traditional full-service video providers.
This first phase serves as a pilot to build trust and credibility within the Livepeer ecosystem while keeping the initial funding request modest.
Mission
The media industry is highly complex. Building reliable, scalable streaming applications requires complex deployments and industry expertise.
Livepeer Inc has laid a robust foundation for decentralized video infrastructure. However, there remains a gap between what the network offers versus what video applications need.
This proposal builds on their achievements by addressing key areas where we can contribute with our expertise.
The MistServer team proposes a Special Purpose Entity to take ownership of maintaining and enhancing the transcoding pipeline, ensuring that node operators have the support, documentation, and features they need.
FrameWorks will also bridge the DevOps gap by offering an E2E media pipeline that businesses can directly integrate or self-host, rather than relying on Livepeer Studio for infrastructure, support or custom features.
Instead of replicating Studios’ high-complexity, full-service model, FrameWorks aims to build a scalable, low-overhead alternative aimed at easy integration with external business logic.
Result: A more stable, performant, and accessible transcoding pipeline for node operators and Livepeer-powered media applications.
Terminology
Some of these terms are not present in this pre-proposal, but can be helpful when browsing through the feature board.
- E2E media pipeline: Provides the core infrastructure for a full media pipeline. Including but not limited to: ingesting, processing, storing, and delivering video.
- Transcoding: The process of decoding a video stream, transforming it (resolution, bitrate, etc.), and encoding it for delivery or storage.
- Segmented Workflow: A process of breaking video streams into discrete segments for transcoding. A full segment is required before it can be transcoded by the network.
- Streaming Workflow: A continuous processing method where the video stream is sent in small chunks and immediately transcoded.
- Intel QSV: Intel’s “Quick Sync Video” hardware for video encoding/decoding, allowing efficient transcoding on Intel CPUs and GPUs.
- AV1: A royalty-free, high-efficiency video coding format which is gaining in popularity.
- Latency: In the context of Livepeer we consider the delay between the stream ingest at a Gateway node and receiving the transcoded frames back.
- Netint: Specialized hardware device for video transcoding.
- LPMS: Livepeer Media Server, the core transcoding library used within the Livepeer stack.
- FTE: Full Time Equivalent, indicates the amount of hours dedicated to a project. 1 FTE equals one fulltime employee, but could also be two people each contributing 0.5 FTEs worth of effort.
Structure
The MistServer Team leads the SPE, with Marco (stronk-tech.eth
) acting as the primary decision-maker and point of contact.
The SPE is open to expand the core SPE team with additional applications from outside the MistServer team.
Structure
- Lead: Marco, long-time Orchestrator and MistServer maintainer.
- Core Team: MistServer maintainers with expertise in transcoding and live streaming.
- Open-Source Contributors: Developers in the Livepeer community who take on bounties.
- Advisors:
- Rick (
transcode.eth
): AI SPE Lead. - Brad (
ad-astra-video.eth
): AI SPE Engineer, also familiar with the transcoding codebase. - Josh: Livepeer Inc engineer with extensive experience with relevant code repositories (
LPMS
andgo-livepeer
). - Rich: Livepeer Ecosystem Growth Team
- Rick (
Responsibilities
- Core Team: Scoping out tasks, assigning bounties, conducting code reviews, and core development of the transcoding pipeline.
- DDVTech: The business entity of the MistServer team, responsible for hiring, team coordination, and administrative processes.
- Advisors: Provide strategic & operational guidance and brainstorming about potential solutions.
About the MistServer Team
The MistServer team is composed of experts in live streaming and media server technology. Our journey began in 2009 when we set out to build a better media server following the failure of a media-related project due to unreliable software. Since then, MistServer has become our core business, and we’ve dedicated our professional lives to advancing live streaming technology.
We bring over half a century of combined hands-on experience in live streaming and media server development, including experience managing streaming infrastructure (like Picarto).
This hands-on expertise positions us uniquely to lead the FrameWorks SPE and contribute meaningfully to the ecosystem.
Scope
The core responsibilities of this SPE include:
- Making the Livepeer transcoding pipeline more robust and competitive.
Adding codecs, adding device support, reducing latency and enhancing transcoding jobs with more parameters.
- Supporting node operators.
Identifying & addressing common pain points, like replacing the static session limit with smarter GPU load balancing and improving Gateway Documentation.
- Ongoing core maintenance
This is a task which also sees ownership from existing core contributors. The Transcoding SPE intends to jump in (wherever required) to assist with tasks like keeping the build pipelines up-to-date, rebasing the LPMS FFMPEG patches and fixing bugs or crashes.
- Research & integrations
The media industry landscape changes over time (slowly evolving). WebRTC and SRT are now common methods to transport media, but are unsupported by Gateway nodes.
These kind of features could also be supported by siderunning applications, like how WebRTC has limited support through go-livepeer
’s MediaMTX integration.
This topic covers exploring enhancements to the Gateway with additional protocols or improving integrations with external applications.
- Expanding testing & QA practices
Implementing automated testing to ensure network stability and prevent regressions.
This includes writing feature-specific tests for each change we make, while also expanding coverage with additional regression or benchmark tests.
- Bridging the DevOps gap for media applications
Providing support to entities looking to build on the network as well as setting up an E2E media pipeline, making it easier for applications to integrate Livepeer-powered streaming without reliance on Livepeer Studio.
Any development work will of course be published open-source and under the Unlicense.
Phase 1: Pilot
Goals
- Gather pain points from Gateway and Orchestrator operators.
- Prioritize roadmap items to address critical gaps in the transcoding pipeline.
- Set up a transcoding bounty program.
- Scope out the E2E media pipeline.
- Cross off the first few items from the roadmap.
Timeline
March 2025:
- Set up operations and governance structure.
- Identify and re-prioritize key tasks for this quarter.
- Launch a bounty board for community contributions.
- Initial discussions on FrameWorks infrastructure.
April – July 2025:
- Engineering work on Q2 key tasks, explained in the roadmap below.
- Next phase planning: Identifying FTE needs and define the FrameWorks infrastructure roadmap.
Roadmap
We have published a feature board where anyone can request items, vote on priorities, and comment on issues.
The roadmap will be prioritized based on continuous conversations with node operators, as well as the needs of inbound opportunities for our E2E media pipeline.
Initial Q2 goals are:
- Improve documentation for Gateway operators.
- Pull Netint integration over the finish line.
- Pull AV1 codec support over the finish line.
- Add Intel QSV support.
- Smarter session limits & load balancing for transcoders.
This roadmap indicates our short-term goals. Not all of these features might see completion in Q2.
Future Phases
If the pilot phase succeeds future requests may include:
- Expanding the core SPE team to increase engineering capacity.
- Addressing long-term goals and more complex tasks, including transitioning to a streaming workflow or expanding the Transcoding job type with more parameters (for example: allowing non-realtime, high quality transcodes for VoD processing).
- Further development & deployment of the FrameWorks E2E media pipeline.
Budget Breakdown
Funding Period: March – June 2025
Total Ask: 17,000 LPT
Breakdown:
Item | Amount | Explanation |
---|---|---|
March: SPE Kickoff & onboarding | 2000 LPT | Structuring the SPE, setting up communication channels, onboarding contributors, gathering feedback from Gateway & Orchestrator operators, initial design work on the E2E media pipeline. |
April – June: Core Development | 12000 LPT | Managing bounties, active community participation, feature development, testing, and infrastructure work. |
Community Incentives | 3000 LPT | Open-source contributor incentives to drive external contributions. |
Rate Justification
For 4,000 LPT per month, the MistServer team operates the SPE while providing 1 FTE of dedicated engineering work. At $5 per LPT, this equates to $20,000 a month (~$115/hr), which is a reduced bulk rate for long-term commitments. This ensures that developers assigned to the SPE remain fully committed, without being pulled into other commercial projects.
If future proposals require additional engineers, we can use the DDVTech entity to hire freelancers or full-timers. This approach allows us to:
- Offer security & guarantees to SPE hires through an established legal entity, of course with access to our office and team’s expertise for onboarding.
- Provide additional engineering capacity at a lower cost, ensuring efficient use of treasury funds.
We are open to adjusting the LPT request or FTE commitment based on community feedback, but believe the amounts are fair given the technical expertise required and in comparison with common rates in the media industry.
Success Metrics:
Defining success metrics for a broad core-development SPE like this is difficult. We encourage feedback on what we can do to measure impact and ensure accountability.
-
Core Contributions:
- Completed bounties.
- PRs submitted and merged into the Livepeer codebase.
- Increase in test coverage.
-
Feedback & Adoption:
- Positive feedback from Gateway & Orchestrator operators.
- Growth in the number of Gateway operators on the network, onboarded through the FrameWorks SPE.
- Transcoded minutes on the E2E media pipeline.
Transparency and Accountability
Engagement with protocol participants is an important part of this SPE. We will work closely with Gateway & Orchestrator operators to collect issues or requests to put on the feature board. We gather community input through multiple channels:
- Discord threads & forum discussions.
- a Canny task board to track development progress, request items or discuss tasks.
- Titan’s weekly water cooler sessions.
Leftover LPT will roll over into future proposals or return to the treasury if the SPE disbands for any reason.
Reporting:
- Quarterly progress reports will include:
- Amount of LPT spent, staked, or held.
- Progress on any of the success metrics.