Documentation Index
Fetch the complete documentation index at: https://na-36-docs-v2.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Mechanism Objectives
Livepeer’s core mechanisms are designed to:- Incentivise honest behaviour among participants (Orchestrators, Delegators, Gateways/Broadcasters)
- Scale supply capacity by rewarding infrastructure providers proportionally
- Secure verification of off-chain video and AI workloads through bonded stake
- Disincentivise dishonest actors via penalties (slashing)
Protocol Features
Core features of the Livepeer Protocol include:Blockchain Attributes
Blockchain Attributes
Blockchain Base
All protocol state (bonds, delegations, votes, job payments, etc.) lives on Arbitrum. The LPT token is ERC-20-based and bridged between L1 and L2.The Arbitrum rollup finalizes via Ethereum; thus the underlying security is Ethereum’s.After Confluence (LIP-73), Ethereum mainnet now mainly serves as a historical source – new stake/votes are on Arbitrum only.Consensus & Finality
Consensus & Finality
Consensus & Finality
Livepeer does not use its own consensus; it relies on Arbitrum’s optimistic rollup. Blocks (called rounds) occur roughly every 24 hrs, and after a ~7-day challenge window the state is finalised on Ethereum.This means trust assumptions are similar to other Ethereum Layer-2s: Arbitrum’s rollup validators and Ethereum miners secure the chain; fraud proofs protect against invalid blocks.Security Model
Security Model
Security Model
Livepeer’s core contracts are on an Ethereum Layer-2 (Arbitrum One), which inherits Ethereum-level security via optimistic rollup.LPT stakers (orchestrators and delegators) provide economic collateral against misbehavior. Protocol rules penalise malfeasance by slashing stake (e.g. Losing part or all delegated tokens).Off-chain video verification and optional arbitration ensure correct transcoding.Node-Level Trust
Node-Level Trust
Node-Level Trust
Gateways/Broadcasters (clients) and orchestrators exchange signed data (video segments, “tickets,” job outcomes).These off-chain interactions can be audited (via perceptual hashes or full verification), so a bad actor’s forged data can be proven on-chain by a dispute mechanism.Orchestrators commit to jobs by staking, and any detected mis-transcoding can trigger an on-chain slashing penalty.Protocol Actors
The Livepeer Protocol defines multiple key actors that participate in the network and perform specific functions.Orchestrators
Orchestrators
Gateways
Gateways
Delegators
Delegators