How the Livepeer Network Extends the Protocol

The Livepeer Network is the off-chain execution layer that turns the Protocol’s rules into a working open marketplace for video and AI compute. This guide explains where the protocol ends, where the network begins, and what the network adds on top.

The protocol-network boundary

The protocol enforces. The network executes. Each side owns a different set of responsibilities, and most operational confusion comes from blurring the line.

The protocol cares only about the things that need cryptographic finality. Everything that needs flexibility, negotiation, or low latency lives on the network.

What the network adds

The protocol’s rules are general. The network is where those rules meet specific workloads, specific topologies, and specific demand patterns.

How a job moves through the network

A typical video or AI job touches the chain only twice: once when the gateway funds its TicketBroker deposit, and once when the orchestrator redeems a winning ticket. Everything in between is the network.

The network does not need to involve the chain to coordinate, dispatch, or deliver. It only needs the chain to hold the active set, the deposit, and the right to redeem.

Where the network goes beyond the original protocol

The original whitepaper described a video transcoding marketplace. The network has since extended itself - usually without changing the protocol - to handle:

• AI inference, sharing the same orchestrator role and economic primitives but with different capability advertisements and pipeline shapes.
• Real-time AI video, over the trickle protocol, with frame-level latency budgets that the round-based protocol layer never needs to know about.
• Bring-Your-Own-Container (BYOC) workloads, where any developer can publish a container that orchestrators run for arbitrary compute-bound tasks. The protocol still settles payment; the network defines the pipeline.
• Special Purpose Entities (SPEs), which build network-layer features (real-time AI, BYOC frameworks, observability tooling) under treasury funding without needing a protocol upgrade.

The pattern is consistent: keep the protocol minimal, extend the network. New workloads, new pipelines, new participants - all added without a protocol change. The on-chain rules stay small. The off-chain marketplace grows.

Where to go next

Canonical reference: network role, design properties, and actor map.

Posted-price market shape, work and value flow, honesty enforcement.

Workload classes, job lifecycle, built-in pipelines, BYOC.

Topology, traffic planes, on-chain anchor contracts, observability.