Livepeer 2.0 - Introducing Validators

1. General

Proposed By: Doug Petkanics

Proposed On: 30 July 2026

2. What Is The Problem?

The proposal: Livepeer 2.0 splits today's orchestrator role in two. Node operators post a bond, run hardware, compete for work, and earn fees. Validators are elected by delegated stake, perform no work, and score node operators between 0 and 1.0. The median score sets each node's reward multiplier. Validators also carry governance and treasury votes.

The problem: The yield cut runs on a fixed calendar. The fee growth meant to replace that yield does not. Validators and delegators are being asked to give up known income now against modelled income later, with nothing tying the two together.

3. Why Does It Matter To the Livepeer Ecosystem?

What the validator set is for. Under BME, node rewards flow in proportion to fees generated. That creates a direct incentive to manufacture fake fee volume. Model inference has no cheap universal proof the way transcoding did, so someone has to exercise judgment. The validator set is that judgment. Delegated stake is what makes it expensive to capture.

What the cut puts at risk. The proposal removes ~$4M/year of inflation, roughly 9% yield, before demand-driven value capture has shown up. LPT is at 52-week lows after a ~79% drawdown, and yield has been the main thing holding the delegator base through it.

If fees do not scale on schedule:

Delegators lose yield and get no appreciation in return.
Node operators earn issuance worth more than the fees they generate.
Bonded stake leaves the validator set.

The third one is the real exposure. Cutting the yield lowers the cost of capturing the set, so the economics and the security budget move together.

4. What Does Success Look Like?

Emissions decline is gated on the burn/mint ratio rather than a calendar.
Set size and issuance share are modelled against a case where fees scale at half the expected rate.
Bonded validator stake is flat or growing through the transition.
A published sequencing plan shows yield changes tracking actual fee growth.

5. Open Questions

How many validator slots should exist? Keeping today's top 100 is the cleanest migration and asks nothing of delegators. But we may not have 100 operators who want to actively score, and a large set spreads the issuance thin. A smaller set is easier to coordinate and cheaper to fund, and concentrates governance and scoring power. What size, or what mechanism for setting size, makes sense?

How do we stop scoring becoming a popularity contest? Validators score independently by design, competing on judgment rather than copying each other. If the criteria stay opaque, delegators have no basis to choose between validators beyond reputation, and validators have every reason to converge on the median instead of scoring well.

What happens to the existing orchestrator set at migration? The lean is continuity: orchestrators inherit validator slots, every node starts at 1.0, active scoring begins from there. A real election on day one is cleaner in principle but risks interrupting rewards for a delegator base that has never moved quickly.

What penalties exist for poor validation? Today, none beyond losing the slot. The role is meant to be lucrative enough that keeping it is incentive enough, and delegators are meant to move stake away from validators who do nothing. Neither holds with a passive delegator base, and a low bar to entry lets a non-performer buy in and collect.

Livepeer