docs-guide/docs-glossary.md (internal contributors and agents only — not publicly served).A
@livepeer/react
@livepeer/react
livepeer:sdkTabs: communityStatus: currentPages: community/sdks, community/toolsABR (Adaptive Bitrate)
ABR (Adaptive Bitrate)
video:encoding, video:playbackTabs: solutionsExternal: Adaptive bitrate streaming (Wikipedia)Status: currentPages: solutions/transcoding, solutions/playbackAccess Control
Access Control
video:studio, technical:securityTabs: solutionsContext: Livepeer Studio implements access control through playback policies attached to stream or asset objects; viewers must present a valid signed JWT or pass a webhook check before the player will resolve the playback URL.Status: currentPages: solutions/access-control, solutions/apiActive Set
Active Set
livepeer:protocolTabs: about, community, lpt, orchestrators, resourcesContext: Active set membership is determined at round start by ranking orchestrators by total bonded LPT (self-stake plus delegated stake). AI inference routing does not require active set membership — it prioritises capability and price over stake position.Status: currentPages: about/protocol, lpt/protocol, orchestrators/protocol, resources/glossaryActive Set Election
Active Set Election
livepeer:protocolTabs: about, lptStatus: currentPages: about/protocol, lpt/protocolAdvisory Boards
Advisory Boards
livepeer:entity, operational:governance, operational:communityTabs: communityContext: Domain-specific groups that recommend strategic priorities for Livepeer SPE workstreams; created as part of Livepeer’s governance evolution alongside Workstreams.Status: currentPages: community/governanceAES-CBC
AES-CBC
technical:securityTabs: solutionsExternal: Block cipher mode of operation (Wikipedia)Status: currentPages: solutions/access-controlAgent
Agent
ai:conceptTabs: resourcesExternal: Intelligent agent (Wikipedia)Status: currentPages: resources/glossary, resources/aiAgents
Agents
ai:conceptTabs: homeExternal: Intelligent agent (Wikipedia)Also known as: Agent (see also: Agent entry)Status: currentPages: home/agents, home/ai-videoAI (Artificial Intelligence)
AI (Artificial Intelligence)
ai:conceptTabs: resourcesExternal: Artificial intelligence (Wikipedia)Also known as: Artificial IntelligenceStatus: currentPages: resources/glossary, resources/indexAI Gateway API
AI Gateway API
livepeer:product, technical:devTabs: developersContext: The AI Gateway API is the primary integration surface for developers submitting AI pipeline requests — text-to-image, live-video-to-video, LLM chat, etc. — to the decentralised Livepeer network without managing infrastructure directly.Status: draftPages: developers/ai-gateway, developers/apiAI Inference
AI Inference
ai:conceptTabs: lpt, orchestratorsExternal: Inference engine (Wikipedia)Status: currentPages: lpt/protocol, orchestrators/aiAI Pipeline
AI Pipeline
ai:pipelineTabs: homeExternal: Pipelines (Hugging Face)Status: currentPages: home/ai-video, home/pipelinesAI runner (ai-runner)
AI runner (ai-runner)
livepeer:toolTabs: communityContext: The ai-runner is the Livepeer process that loads AI models into GPU memory and serves inference requests dispatched by the orchestrator; it is configured via aiModels.json.Status: currentPages: community/ai, community/toolsAI Runner
AI Runner
aiModels.json and the -aiWorker / -aiModels CLI flags.Tags: livepeer:config, livepeer:deploymentTabs: orchestratorsStatus: currentPages: orchestrators/ai, orchestrators/setupAI subnet
AI subnet
livepeer:protocolTabs: communityContext: The AI subnet operates alongside the transcoding network; orchestrators register supported pipelines via AIServiceRegistry and receive AI inference jobs from AI-capable gateways.Status: currentPages: community/ai, community/networkAI Video
AI Video
ai:applicationTabs: homeStatus: currentPages: home/index, home/ai-videoAI Video SPE
AI Video SPE
livepeer:entityTabs: communityContext: One of several treasury-funded SPEs; focused on AI video pipeline development, including expanding the AI subnet and BYOC deployment patterns.Status: currentPages: community/governance, community/treasuryaiModels.json
aiModels.json
livepeer:configTabs: orchestratorsContext: The primary config file for AI orchestrators. Each entry defines which model to load, at what price, and whether it should be pre-warmed on startup.Status: currentPages: orchestrators/ai, orchestrators/configAIServiceRegistry
AIServiceRegistry
livepeer:contractTabs: orchestratorsContext: Orchestrators optionally advertise their AI pipelines and models on-chain via this contract, enabling capability-based routing by gateways.Status: currentPages: orchestrators/ai, orchestrators/contractsaiWorker
aiWorker
livepeer:configTabs: orchestratorsContext: Enables the orchestrator to offload GPU inference work to a separate subprocess. Multiple aiWorker processes can be connected to a single orchestrator for multi-GPU setups.Status: currentPages: orchestrators/ai, orchestrators/architectureAmbassador Programme
Ambassador Programme
operational:communityTabs: communityContext: Livepeer’s Ambassador Programme designates community representatives who promote adoption, create educational content, and help onboard new participants into the ecosystem.Status: currentPages: community/programs, community/indexAPI Key
API Key
technical:devTabs: solutionsExternal: API key (Wikipedia)Status: currentPages: solutions/api, solutions/quickstartArbitrage
Arbitrage
economic:pricingTabs: gatewaysExternal: Arbitrage (Wikipedia)Status: currentPages: gateways/pricing, gateways/economicsArbitrum
Arbitrum
web3:chainTabs: home, about, developers, gateways, orchestrators, community, lpt, resourcesExternal: Arbitrum documentationAlso known as: Arbitrum OneStatus: currentPages: about/protocol, lpt/bridging, resources/glossaryAsset
Asset
video:studioTabs: solutionsContext: An asset is the Studio object created when a video file is uploaded; it stores transcoded renditions, a playback ID, and optional access-control settings, and is distinct from the live Stream object.Status: currentPages: solutions/vod, solutions/apiAT Protocol
AT Protocol
technical:socialTabs: solutionsExternal: AT Protocol (Wikipedia)Status: currentPages: solutions/integrationsAtomic Execution
Atomic Execution
web3:governanceTabs: lptExternal: Atomic commit (Wikipedia)Status: currentPages: lpt/governance, lpt/contractsAudio-to-Text
Audio-to-Text
ai:pipelineTabs: orchestratorsExternal: Speech recognition (Wikipedia)Status: currentPages: orchestrators/pipelines, orchestrators/aiautonomous agent
autonomous agent
ai:applicationTabs: communityExternal: Autonomous agent (Wikipedia)Status: currentPages: community/ai, community/projectsAvatar
Avatar
ai:applicationTabs: home, solutionsExternal: Avatar — computing (Wikipedia)Status: currentPages: home/ai-video, solutions/aiawesome-livepeer
awesome-livepeer
livepeer:toolTabs: communityContext: A GitHub repository maintained by the community aggregating third-party tools, monitoring dashboards, SDKs, orchestrator utilities, and educational content related to Livepeer.Status: currentPages: community/resources, community/toolsB
B-frames
B-frames
video:encodingTabs: solutionsExternal: Video compression picture types (Wikipedia)Status: currentPages: solutions/encoding, solutions/livestreamingBatch AI / Batch AI Inference
Batch AI / Batch AI Inference
ai:pipeline, ai:conceptTabs: developers, orchestratorsExternal: What is batch inference? (Google Cloud)Status: currentPages: developers/ai-gateway, orchestrators/pipelinesBearer Token
Bearer Token
technical:devTabs: solutionsExternal: Authorization header (MDN)Status: currentPages: solutions/apiBitrate
Bitrate
video:encodingTabs: solutions, resourcesExternal: Bit rate (Wikipedia)Status: currentPages: solutions/encoding, resources/glossaryBLIP
BLIP
ai:modelTabs: orchestratorsExternal: BLIP (Hugging Face)Status: currentPages: orchestrators/pipelines, orchestrators/aiBlock Timestamps
Block Timestamps
web3:identityTabs: resourcesExternal: Ethereum glossary (ethereum.org)Status: draftPages: resources/glossaryBlockchain
Blockchain
web3:conceptTabs: homeExternal: Blockchain (Wikipedia)Status: currentPages: home/network, home/indexBonded Stake
Bonded Stake
web3:tokenomicsTabs: lptContext: Bonded stake is the aggregate input to Livepeer’s economic weight calculations; a higher bonded stake means a higher bonding rate and lower inflation.Status: currentPages: lpt/staking, lpt/protocolBonding
Bonding
web3:tokenomicsTabs: about, community, orchestrators, lptExternal: Livepeer bonding overviewStatus: currentPages: about/staking, community/staking, lpt/stakingBonding Rate (beta)
Bonding Rate (beta)
economic:reward, web3:tokenomicsTabs: lptContext: The current bonding rate (beta) is the live metric compared against the Target Bonding Rate to determine whether inflation should increase or decrease each round.Status: currentPages: lpt/economics, lpt/inflationBondingManager
BondingManager
livepeer:contractTabs: orchestrators, lpt, resourcesContext: The central contract for all LPT stake operations — bonding, unbonding, delegation, reward distribution, and slash execution.Status: currentPages: orchestrators/contracts, lpt/contracts, resources/glossaryBondingVotes
BondingVotes
livepeer:contract, web3:governanceTabs: lpt, resourcesContext: BondingVotes implements the ERC-5805 checkpoint standard and feeds bonded stake data into LivepeerGovernor for on-chain proposal votes.Status: currentPages: lpt/contracts, resources/glossaryBounty
Bounty
economic:treasuryTabs: communityContext: Bounties are posted by the Livepeer Foundation or SPEs for well-defined deliverables such as tooling, documentation, or bug fixes; funded from the on-chain treasury.Status: currentPages: community/treasury, community/programsBridge
Bridge
web3:conceptTabs: lptExternal: Bridges (ethereum.org)Status: currentPages: lpt/bridging, lpt/arbitrumBridging
Bridging
web3:conceptTabs: lpt, resourcesExternal: Blockchain bridge (Ethereum docs)Also known as: BridgeStatus: currentPages: lpt/bridging, resources/glossaryBroadcaster (deprecated)
Broadcaster (deprecated)
livepeer:roleTabs: about, solutions, gateways, resourcesContext: The term “Broadcaster” was used in early Livepeer documentation and the original whitepaper; current documentation uses “Gateway” for this role. The -broadcaster=true CLI flag has been replaced by -gateway.Also known as: Gateway (current term)Status: currentPages: about/protocol, gateways/protocol, resources/glossaryBroadcastSessionsManager
BroadcastSessionsManager
livepeer:protocolTabs: gatewaysContext: The BroadcastSessionsManager tracks session state, handles failover logic, and maintains per-orchestrator session pools within a running gateway node.Status: currentPages: gateways/code, gateways/architectureBYOC (Bring Your Own Compute / Bring Your Own Container)
BYOC (Bring Your Own Compute / Bring Your Own Container)
livepeer:deployment, ai:conceptTabs: home, developers, gateways, orchestrators, community, resourcesContext: Used in Livepeer to let GPU providers and teams run containerized Python workloads for streaming AI pipelines, enabling flexible compute contributions without requiring standard pipeline implementations. BYOC containers must conform to the Livepeer AI worker API specification.Also known as: Bring Your Own Container, Bring Your Own ComputeStatus: currentPages: home/compute, developers/pipelines, orchestrators/ai, resources/glossaryC
C2PA
C2PA
technical:securityTabs: solutionsExternal: C2PA specificationStatus: currentPages: solutions/provenance, solutions/aiCapability
Capability
livepeer:protocolTabs: gateways, resourcesContext: Gateways use capability advertisements to discover which orchestrators support a given AI pipeline and model, enabling targeted routing without manual orchestrator configuration.Status: currentPages: gateways/discovery, resources/glossaryCapability Advertisement
Capability Advertisement
livepeer:protocolTabs: orchestratorsContext: Orchestrators broadcast their capabilities either on-chain via the AIServiceRegistry or off-chain via webhook discovery. Gateways use this data to route inference jobs to capable nodes.Status: currentPages: orchestrators/discovery, orchestrators/aiCapability Matching
Capability Matching
livepeer:protocolTabs: orchestratorsContext: The gateway compares the requested pipeline and model against each orchestrator’s advertised capabilities and selects the best match based on price, performance score, and availability.Status: currentPages: orchestrators/discovery, orchestrators/routingCapital-backed Sybil Resistance
Capital-backed Sybil Resistance
web3:tokenomicsTabs: lptExternal: Proof of stake (ethereum.org)Status: currentPages: lpt/security, lpt/protocolCapital Efficiency
Capital Efficiency
web3:tokenomicsTabs: lptExternal: Cryptoeconomics (Wikipedia)Status: currentPages: lpt/economics, lpt/stakingCascade
Cascade
livepeer:upgradeTabs: home, about, developers, gateways, orchestratorsContext: Cascade is Livepeer’s named strategic phase introducing AI inference as a first-class use case alongside transcoding, activating the AI subnet and GPU orchestrator market.Status: currentPages: about/upgrades, home/network, orchestrators/upgradesCBR (Constant Bitrate)
CBR (Constant Bitrate)
video:encodingTabs: solutionsExternal: Constant bitrate (Wikipedia)Status: currentPages: solutions/encoding, solutions/transcodingCDN (Content Delivery Network)
CDN (Content Delivery Network)
technical:infraTabs: resourcesExternal: Content delivery network (Wikipedia)Also known as: Content Delivery NetworkStatus: currentPages: resources/glossaryCheckpoint
Checkpoint
livepeer:protocolTabs: lptContext: Checkpoints are written each round so that governance votes can reference stake at the block when a proposal was created, preventing manipulation by bonding immediately before a vote.Status: currentPages: lpt/protocol, lpt/contractsClaim Earnings
Claim Earnings
livepeer:protocolTabs: lptContext: Earnings accumulate through pending reward pools and must be explicitly claimed; claiming through the BondingManager updates the delegator’s bonded balance.Status: currentPages: lpt/staking, lpt/delegationClearinghouse
Clearinghouse
economic:payment, livepeer:contractTabs: gateways, orchestratorsContext: In gateway deployments, a clearinghouse is an abstraction over a remote signer that adds commercial services, enabling gateway operators to offer multi-tenant billing without each user needing their own ETH wallet.Status: currentPages: gateways/payments, orchestrators/paymentsCLI (Command-Line Interface)
CLI (Command-Line Interface)
technical:devTabs: orchestrators, resourcesExternal: Command-line interface (Wikipedia)Also known as: Command-Line InterfaceStatus: currentPages: orchestrators/setup, resources/glossaryClip
Clip
video:studioTabs: solutionsContext: Livepeer Studio exposes a Clip API that accepts a stream or session ID and timestamp range; the resulting clip is stored as a new asset with its own playback ID.Status: currentPages: solutions/livestreaming, solutions/clipsCodec (CODEC)
Codec (CODEC)
video:encodingTabs: about, gateways, resourcesExternal: Video codec (Wikipedia)Status: currentPages: about/transcoding, gateways/transcoding, resources/glossaryCold Start
Cold Start
ai:concept, livepeer:configTabs: developers, gateways, orchestrators, resourcesExternal: Cold start latency in private AI inference (OpenMetal)Also known as: Cold modelStatus: currentPages: developers/pipelines, orchestrators/ai, resources/glossaryComfyStream
ComfyStream
livepeer:product, ai:frameworkTabs: home, about, developers, orchestrators, community, resourcesContext: ComfyStream enables orchestrators to expose ComfyUI-based diffusion pipelines as live-video-to-video capabilities on the Livepeer network, allowing real-time AI video transformations to run on network orchestrators.Status: currentPages: home/ai-video, developers/pipelines, orchestrators/ai, resources/glossaryComfyUI
ComfyUI
ai:frameworkTabs: home, developers, orchestratorsExternal: ComfyUI (GitHub)Status: currentPages: home/ai-video, developers/pipelines, orchestrators/aiCommission Rate
Commission Rate
economic:rewardTabs: community, lptContext: Commission Rate in Livepeer encompasses both the reward cut (on inflationary LPT) and fee cut (on ETH fees); orchestrators compete in the marketplace partly on the basis of their commission rates.Status: currentPages: community/staking, lpt/economicsCommunity Arbitrum Node
Community Arbitrum Node
livepeer:toolTabs: communityContext: A shared Arbitrum RPC endpoint funded by the community treasury through LiveInfra, giving ecosystem participants free access to on-chain data without running their own node.Status: currentPages: community/tools, community/networkCommunity Treasury
Community Treasury
economic:treasuryTabs: lptContext: The Community Treasury receives a configurable Treasury Reward Cut Rate of inflation each round and is spent via governance-approved proposals for ecosystem development.Also known as: On-chain TreasuryStatus: currentPages: lpt/treasury, lpt/governanceCompute Marketplace
Compute Marketplace
livepeer:productTabs: homeContext: Livepeer’s mechanism for coordinating supply (GPU operators) and demand (developers and applications) for compute resources, governed by crypto-economic incentives rather than a centralized provider.Status: currentPages: home/network, home/computeConcentration Risk
Concentration Risk
web3:tokenomicsTabs: lptExternal: Proof of stake (Wikipedia)Status: currentPages: lpt/staking, lpt/securityConfiguration Parameters
Configuration Parameters
livepeer:configTabs: resourcesContext: Livepeer node configuration is managed entirely through command-line flags passed to go-livepeer at startup, covering everything from pricePerUnit and MaxPrice to orchSecret and operational mode settings.Status: draftPages: resources/glossary, resources/toolsConfluence
Confluence
livepeer:upgradeTabs: aboutContext: Confluence was a major protocol milestone enabling cheaper, faster on-chain operations by moving the staking and payment contracts to Arbitrum.Status: currentPages: about/upgrades, about/protocolConfluent Upgrade
Confluent Upgrade
livepeer:upgradeTabs: homeContext: The Confluent upgrade (also called Confluence) was a production migration moving Livepeer’s staking and payment contracts from Ethereum L1 to Arbitrum One.Also known as: ConfluenceStatus: currentPages: home/upgradesConventional Commits
Conventional Commits
operational:processTabs: communityExternal: Conventional Commits v1.0.0Status: currentPages: community/development, community/contributingController
Controller
livepeer:contractTabs: about, resourcesContext: The Controller is the central registry through which all other Livepeer smart contracts are discovered and updated during protocol upgrades; it is the single source of truth for which contract address corresponds to each protocol role.Status: currentPages: about/protocol, resources/glossaryControlNet
ControlNet
ai:modelTabs: orchestrators, resourcesExternal: ControlNet (Hugging Face)Status: currentPages: orchestrators/pipelines, resources/glossaryCORS (Cross-Origin Resource Sharing)
CORS (Cross-Origin Resource Sharing)
technical:devTabs: solutionsExternal: CORS (MDN)Status: currentPages: solutions/api, solutions/playerCPU (Central Processing Unit)
CPU (Central Processing Unit)
technical:hardwareTabs: gateways, orchestrators, developers, aboutExternal: Central processing unit (Wikipedia)Status: currentPages: gateways/run-a-gateway/requirements/setup, orchestrators/run-an-orchestrator/requirementsCRF (Constant Rate Factor)
CRF (Constant Rate Factor)
video:encodingTabs: solutionsExternal: CRF guide (slhck.info)Status: currentPages: solutions/encoding, solutions/transcodingCryptoeconomic Primitives
Cryptoeconomic Primitives
web3:conceptTabs: aboutExternal: Cryptoeconomics (Wikipedia)Status: currentPages: about/protocol, about/economicsCUDA (Compute Unified Device Architecture)
CUDA (Compute Unified Device Architecture)
ai:framework, technical:infraTabs: orchestratorsExternal: CUDA (Wikipedia)Status: currentPages: orchestrators/setup, orchestrators/aiD
DAO (Decentralized Autonomous Organization)
DAO (Decentralized Autonomous Organization)
web3:conceptTabs: community, resourcesExternal: Decentralized autonomous organization (Wikipedia)Also known as: Decentralized Autonomous OrganizationStatus: currentPages: community/governance, resources/glossaryDASH (Dynamic Adaptive Streaming over HTTP)
DASH (Dynamic Adaptive Streaming over HTTP)
video:protocolTabs: resourcesExternal: DASH (Wikipedia)Also known as: Dynamic Adaptive Streaming over HTTPStatus: currentPages: resources/glossary, resources/streamingDashboard
Dashboard
video:studioTabs: solutionsContext: The Livepeer Studio Dashboard is the primary no-code interface; developers use it to generate stream keys, copy playback IDs, configure multistream targets, and inspect viewership data without writing API calls.Status: currentPages: solutions/dashboard, solutions/indexDaydream
Daydream
livepeer:productTabs: home, about, solutions, developers, orchestrators, communityContext: A Livepeer product and reference implementation demonstrating real-time interactive AI video generation on the network; showcases the full stack from ingest through AI pipeline to playback.Status: currentPages: home/ai-video, solutions/ai, developers/ai-videoDeAI (Decentralized AI)
DeAI (Decentralized AI)
ai:application, web3:conceptTabs: homeExternal: Distributed artificial intelligence (Wikipedia)Status: currentPages: home/ai-video, home/indexDecentralization
Decentralization
web3:conceptTabs: homeExternal: Decentralization (Wikipedia)Status: currentPages: home/network, home/indexDecentralized GPU Network
Decentralized GPU Network
livepeer:protocolTabs: resourcesContext: Livepeer’s decentralized GPU network is the supply side of the protocol — orchestrators worldwide offer compute capacity that gateways route jobs to based on price, performance, and capability.Status: currentPages: resources/glossary, resources/networkDelegation
Delegation
web3:tokenomicsTabs: about, developers, community, lpt, resourcesExternal: Livepeer delegationStatus: currentPages: about/staking, lpt/delegation, resources/glossaryDelegator
Delegator
livepeer:role, web3:tokenomicsTabs: home, about, developers, orchestrators, community, lpt, resourcesContext: One of the three core protocol roles in Livepeer; delegators do not run infrastructure themselves but allocate stake to orchestrators they trust, receiving a share of inflationary rewards proportional to their contribution.Status: currentPages: about/staking, lpt/delegation, resources/glossaryDelta Upgrade
Delta Upgrade
livepeer:upgradeTabs: homeContext: A named milestone on the Livepeer roadmap introducing on-chain verification mechanisms; represents the end-state of trustless work verification for transcoding and AI jobs.Status: currentPages: home/upgradesDemand Aggregation
Demand Aggregation
operational:processTabs: gatewaysContext: Gateways perform demand aggregation by receiving requests from many clients and batching or routing them to orchestrators, improving utilization and reducing per-request overhead for each end user.Status: currentPages: gateways/architecture, gateways/economicsDePIN (Decentralized Physical Infrastructure Networks)
DePIN (Decentralized Physical Infrastructure Networks)
web3:conceptTabs: resourcesExternal: DePIN (Wikipedia)Also known as: Decentralized Physical Infrastructure NetworksStatus: currentPages: resources/glossary, resources/networkDeposit
Deposit
economic:paymentTabs: gatewaysContext: An on-chain gateway must maintain a deposit on Arbitrum. The deposit covers the expected value of outstanding payment tickets sent to orchestrators. If the deposit is depleted, the reserve acts as backstop.Status: currentPages: gateways/payments, gateways/protocolDev Call
Dev Call
operational:communityTabs: communityContext: The Dev Call is a regular public community call where Livepeer engineers share protocol updates, discuss upcoming LIPs, and take questions from orchestrators and developers.Status: currentPages: community/events, community/developmentDeveloper
Developer
livepeer:roleTabs: resourcesContext: In the Livepeer actor taxonomy, Developers are distinct from Gateway operators: they consume the network’s capabilities through APIs and SDKs rather than submitting jobs directly to the protocol.Status: currentPages: resources/glossary, resources/indexDeveloper Platform
Developer Platform
livepeer:productTabs: resourcesContext: The Developer Platform shields application builders from low-level protocol mechanics while still routing jobs through the decentralized network.Status: currentPages: resources/glossary, resources/toolsDeveloper Stack
Developer Stack
livepeer:productTabs: developersContext: The Developer Stack is Livepeer’s collective offering for builders — encompassing Livepeer Studio, the AI Gateway API, Livepeer.js, and PyTrickle — enabling video and AI features without managing protocol infrastructure.Status: currentPages: developers/index, developers/quickstartDiffusion Models
Diffusion Models
ai:conceptTabs: developers, orchestrators, resourcesExternal: Diffusion model (Wikipedia)Also known as: DiffusionStatus: currentPages: developers/pipelines, orchestrators/ai, resources/glossaryDigital Twin
Digital Twin
ai:applicationTabs: homeExternal: Digital twin (Wikipedia)Status: currentPages: home/ai-video, home/use-casesDilution
Dilution
economic:reward, web3:tokenomicsTabs: lptContext: Delegators and orchestrators avoid dilution by bonding; unbonded LPT holders see their ownership percentage decrease as inflationary rewards are distributed only to active participants.Status: currentPages: lpt/inflation, lpt/economicsDispersal
Dispersal
video:processingTabs: gatewaysContext: When a gateway disperses work, it splits a stream’s segments across multiple orchestrators simultaneously, enabling parallel transcoding and reducing the impact of a single slow or failing node.Status: currentPages: gateways/routing, gateways/architectureDual Gateway / Dual Mode
Dual Gateway / Dual Mode
livepeer:deploymentTabs: gateways, orchestratorsContext: A dual gateway routes RTMP transcoding requests and AI inference requests from the same node instance. The most common production configuration for operators with capable hardware (24 GB+ VRAM).Also known as: Dual modeStatus: currentPages: gateways/architecture, orchestrators/configDune
Dune
operational:monitoringTabs: communityExternal: Dune AnalyticsStatus: currentPages: community/tools, community/analyticsDynamic Inflation
Dynamic Inflation
livepeer:protocol, economic:rewardTabs: aboutContext: Dynamic inflation is Livepeer’s mechanism for incentivizing participation: when fewer than 50% of LPT is bonded, inflation rises to attract more stakers; when above 50%, it falls.Status: currentPages: about/economics, about/protocolE
Economic Weight
Economic Weight
web3:tokenomicsTabs: lptContext: Economic weight is central to Livepeer’s security model — orchestrators with more delegated stake have higher economic weight and receive more work and rewards.Status: currentPages: lpt/economics, lpt/protocolEmbody
Embody
livepeer:product, ai:applicationTabs: solutionsContext: Embody is a Livepeer ecosystem SPE focused on avatar and NPC creation; it extends the network with pipelines that animate virtual characters driven by AI inference, enabling real-time interactive digital embodiment.Status: currentPages: solutions/ai, solutions/use-casesEmbedding
Embedding
ai:conceptTabs: developersExternal: Word embedding (Wikipedia)Status: currentPages: developers/pipelines, developers/ai-gatewayEncrypted Asset
Encrypted Asset
technical:security, video:studioTabs: solutionsContext: In Livepeer Studio, assets can be marked for encryption; the platform stores the file encrypted and gates decryption through the access-control system, requiring a valid playback policy before serving the key to a player.Status: currentPages: solutions/access-control, solutions/vodEncoding Ladder
Encoding Ladder
video:encodingTabs: gatewaysExternal: Encoding ladder (Cloudinary)Status: currentPages: gateways/transcoding, gateways/profilesEndpoint
Endpoint
technical:devTabs: solutions, developersExternal: Web API (Wikipedia)Status: currentPages: solutions/api, developers/apiEphemeral Compute
Ephemeral Compute
technical:infraTabs: aboutExternal: Edge computing (Wikipedia)Status: draftPages: about/ai, about/architectureETH (Ether)
ETH (Ether)
web3:tokenTabs: home, gateways, orchestrators, resourcesExternal: What is Ether (Ethereum.org)Also known as: EtherStatus: currentPages: gateways/payments, orchestrators/payments, resources/glossaryETH Fees
ETH Fees
economic:payment, web3:tokenTabs: about, lptContext: ETH fees are the demand-side revenue stream for orchestrators and their delegators, distinct from inflationary LPT rewards; they represent real market demand for network services.Status: currentPages: about/economics, lpt/economicsEthereum
Ethereum
web3:chainTabs: home, developersExternal: Ethereum (Wikipedia)Status: currentPages: home/network, developers/protocolEthereum Address
Ethereum Address
web3:identityTabs: resourcesExternal: Ethereum accounts (Ethereum docs)Also known as: Wallet Public AddressStatus: draftPages: resources/glossaryExecution Layer
Execution Layer
livepeer:protocolTabs: aboutContext: In Livepeer’s architecture, the execution layer is the off-chain network of orchestrator nodes doing transcoding and AI inference, coordinated by the on-chain protocol layer on Arbitrum.Status: currentPages: about/protocol, about/networkF
Face Value
Face Value
economic:paymentTabs: orchestratorsContext: The face value of tickets is set so that, over many tickets, the expected payout matches the fair cost of the work performed. Orchestrators accept lower-probability, higher-face-value tickets to reduce on-chain redemption frequency.Status: currentPages: orchestrators/payments, orchestrators/protocolFailover
Failover
operational:monitoringTabs: gateways, communityExternal: Failover (Wikipedia)Status: currentPages: gateways/routing, gateways/reliabilityFault Proof
Fault Proof
web3:chainTabs: aboutExternal: Rollups (ethereum.org)Status: currentPages: about/protocol, about/networkFediverse
Fediverse
technical:socialTabs: solutionsExternal: Fediverse (Wikipedia)Status: currentPages: solutions/integrationsFee Cut
Fee Cut
economic:rewardTabs: about, orchestrators, community, lpt, resourcesContext: Fee cut is set independently from reward cut. A lower fee cut sends more ETH earnings to delegators, which can attract more delegation. Both cuts are configured on-chain and visible in the Livepeer Explorer.Also known as: Fee share (the portion passed to delegators is the complement)Status: currentPages: about/staking, orchestrators/staking, lpt/economics, resources/glossaryFee Pool
Fee Pool
economic:rewardTabs: orchestrators, lpt, resourcesContext: ETH earned from winning tickets flows into the fee pool each round. Orchestrators and delegators claim their respective shares according to the orchestrator’s fee cut setting. The fee pool is distinct from the inflationary reward pool; it originates from gateway payments for real work performed.Status: currentPages: orchestrators/staking, lpt/economics, resources/glossaryFee Share
Fee Share
Fee Switch
Fee Switch
economic:treasuryTabs: lptContext: The fee switch is a proposed parameter change subject to on-chain governance; enabling it would direct a portion of ETH fees to the treasury rather than solely to orchestrators and delegators.Status: currentPages: lpt/economics, lpt/governanceFinality
Finality
web3:conceptTabs: aboutExternal: Ethereum glossary — finalityStatus: currentPages: about/protocol, about/networkFoundation
Foundation
livepeer:entityTabs: homeContext: The Livepeer Foundation was established to assume stewardship responsibilities from Livepeer Inc, overseeing ecosystem grants, governance coordination, and protocol direction on behalf of the community.Status: currentPages: home/governance, home/indexFrame Rate
Frame Rate
video:encodingTabs: homeExternal: Frame rate (Wikipedia)Status: currentPages: home/streaming, home/videoFrameProcessor
FrameProcessor
livepeer:sdkTabs: developersContext: FrameProcessor is the Livepeer-defined interface in the PyTrickle SDK that developers implement to apply AI transforms to individual video frames within a live stream pipeline.Status: currentPages: developers/pipelines, developers/ai-videoFrameworks
Frameworks
livepeer:productTabs: solutionsContext: Frameworks is a Livepeer ecosystem product (SPE pilot) that packages MistServer-based infrastructure components into developer-friendly libraries, lowering integration effort for new applications.Status: currentPages: solutions/sdks, solutions/apiG
Gas
Gas
web3:conceptTabs: resourcesExternal: Gas (Ethereum docs)Status: currentPages: resources/glossary, resources/protocolGB (Gigabyte)
GB (Gigabyte)
technical:hardwareTabs: gateways, orchestrators, developersExternal: Gigabyte (Wikipedia)Status: currentPages: gateways/run-a-gateway/requirements/setup, orchestrators/run-an-orchestrator/requirementsGateway
Gateway
livepeer:roleTabs: home, about, solutions, developers, gateways, orchestrators, community, lpt, resourcesContext: Gateways are the demand-side entry point to the network; they receive requests from developers or applications, select orchestrators, handle probabilistic micropayments, and return results. No GPU is required to run a gateway.Status: currentPages: home/network, about/protocol, gateways/index, resources/glossaryGateway-as-a-Service
Gateway-as-a-Service
livepeer:deploymentTabs: gatewaysContext: Gateway-as-a-service offerings (for example, Livepeer Studio, Livepeer Cloud, or Daydream) run gateway nodes on the operator’s behalf. The user pays the service’s rate and receives an API endpoint rather than running go-livepeer directly.Status: currentPages: gateways/modes, gateways/architectureGateway Middleware
Gateway Middleware
livepeer:protocolTabs: gatewaysContext: Gateway middleware lets operators intercept and modify requests or responses at the gateway layer without forking go-livepeer. Middleware is typically configured in code for SDK-based deployments or via hooks in go-livepeer.Status: currentPages: gateways/architecture, gateways/codeGateway operator
Gateway operator
livepeer:roleTabs: communityContext: Gateway operators in Livepeer run nodes that submit transcoding or AI inference jobs to the network, manage payment flows via probabilistic micropayments, and expose protocol services to end applications.Status: currentPages: community/networkGenerative Video
Generative Video
ai:applicationTabs: homeExternal: Text-to-video model (Wikipedia)Status: currentPages: home/ai-video, home/use-casesGenesis Supply
Genesis Supply
economic:rewardTabs: lptContext: The genesis supply was the starting point for LPT tokenomics; total supply has grown from 10M through inflation since the mainnet launch in 2018.Status: currentPages: lpt/tokenomics, lpt/historyGeForce
GeForce
technical:hardwareTabs: gateways, orchestratorsExternal: NVIDIA GeForceStatus: currentPages: gateways/run-a-gateway/requirements/setup, orchestrators/run-an-orchestrator/requirementsgo-livepeer
go-livepeer
livepeer:sdkTabs: developers, orchestratorsContext: The canonical node software for running any Livepeer network role. Orchestrators, gateways, and transcoders all run go-livepeer with different flag combinations.Status: currentPages: developers/protocol, orchestrators/setupGovernance
Governance
operational:governanceTabs: home, community, lpt, resourcesExternal: Livepeer Governance (GitHub wiki)Status: currentPages: home/governance, community/governance, lpt/governance, resources/glossaryGovernance Forum
Governance Forum
operational:communityTabs: community, lptContext: The primary off-chain coordination space for Livepeer governance; where community members post pre-proposals, discuss LIPs, and build consensus before on-chain votes.Status: currentPages: community/governance, lpt/governanceGovernor Contract
Governor Contract
livepeer:contract, web3:governanceTabs: about, lpt, resourcesContext: The Governor contract is Livepeer’s on-chain decision-making mechanism, introduced in LIP-89, enabling token-weighted votes on treasury allocations and protocol changes.Also known as: LivepeerGovernorStatus: currentPages: about/governance, lpt/contracts, resources/glossaryGovWorks
GovWorks
livepeer:entity, operational:governanceTabs: communityContext: GovWorks is the governance coordination workstream and SPE; it administers the proposal process, publishes governance summaries, and was initially chaired by StableLab.Status: currentPages: community/governance, community/treasuryGrafana
Grafana
operational:monitoringTabs: communityExternal: GrafanaStatus: currentPages: community/tools, community/monitoringGrant
Grant
economic:treasuryTabs: communityContext: Grants are awarded through treasury proposals or Foundation programmes to fund tooling, research, education, or infrastructure that benefits the Livepeer ecosystem.Status: currentPages: community/treasury, community/programsgRPC
gRPC
technical:protocolTabs: orchestratorsExternal: gRPC (Wikipedia)Status: currentPages: orchestrators/architecture, orchestrators/codeGroup of Pictures (GOP)
Group of Pictures (GOP)
video:encodingTabs: gatewaysExternal: Group of pictures (Wikipedia)Also known as: GOPStatus: currentPages: gateways/transcoding, gateways/encodingGPU (Graphics Processing Unit)
GPU (Graphics Processing Unit)
technical:infraTabs: home, community, orchestrators, resourcesExternal: Graphics processing unit (Wikipedia)Also known as: Graphics Processing UnitStatus: currentPages: home/network, orchestrators/ai, resources/glossaryGPU Operator
GPU Operator
livepeer:roleTabs: home, developersContext: GPU operators are a specific class of Livepeer network participants who run GPU hardware connected to the network, earning ETH fees by performing compute-intensive tasks such as video transcoding and AI model inference.Status: currentPages: home/compute, developers/nodeGPU Worker
GPU Worker
technical:infra, livepeer:deploymentTabs: gateways, orchestratorsContext: In gateway routing, the gateway selects orchestrators that have available GPU workers capable of handling the requested AI pipeline or transcoding profile. In orchestrator AI or dual-mode deployments, each GPU runs a dedicated AI runner subprocess.Status: currentPages: orchestrators/ai, orchestrators/architectureGTX (NVIDIA GTX)
GTX (NVIDIA GTX)
technical:hardwareTabs: gateways, orchestratorsAlso known as: GeForce GTXExternal: NVIDIA GeForce graphics cardsStatus: currentPages: gateways/run-a-gateway/requirements/setup, orchestrators/run-an-orchestrator/requirementsGWID (Gateway Wizard)
GWID (Gateway Wizard)
livepeer:entityTabs: communityContext: GWID is a Governance Workstream Identification number assigned to the Gateway Wizard SPE; the project delivers simplified gateway setup tooling and is tracked by its GWID identifier on the governance forum.Status: currentPages: community/governance, community/proposalsH
Hard Gate
Hard Gate
livepeer:configTabs: orchestratorsContext: Unlike soft scoring factors, a hard gate is binary — the orchestrator is excluded from consideration entirely if the condition is not met. MaxPrice is the most common hard gate in practice.Status: currentPages: orchestrators/ai, orchestrators/configHLS (HTTP Live Streaming)
HLS (HTTP Live Streaming)
.m3u8) for adaptive bitrate playback over standard HTTP.Tags: video:protocolTabs: about, solutions, developers, gateways, orchestrators, resourcesExternal: HTTP Live Streaming (Wikipedia)Also known as: HTTP Live StreamingStatus: currentPages: about/transcoding, solutions/playback, resources/glossaryHTTP Ingest
HTTP Ingest
video:processingTabs: gatewaysExternal: HTTP (Wikipedia)Status: currentPages: gateways/ingest, gateways/streamingHuggingFace
HuggingFace
ai:platformTabs: gateways, orchestrators, developers, communityAlso known as: Hugging Face, HFExternal: HuggingFaceStatus: currentPages: orchestrators/run-an-orchestrator/ai-models, developers/ai-pipelines/overviewI
ICO (Initial Coin Offering)
ICO (Initial Coin Offering)
web3:concept, economic:businessTabs: resourcesExternal: Initial coin offering (Wikipedia)Also known as: Initial Coin OfferingStatus: draftPages: resources/glossaryImage-to-Image
Image-to-Image
ai:pipelineTabs: developers, orchestratorsExternal: Image translation (Wikipedia)Status: currentPages: developers/pipelines, orchestrators/pipelinesImage-to-Text
Image-to-Text
ai:pipelineTabs: developers, orchestratorsExternal: Image-to-Text task (Hugging Face)Status: currentPages: developers/pipelines, orchestrators/pipelinesImage-to-Video
Image-to-Video
ai:pipelineTabs: developers, orchestratorsExternal: Image-to-Video task (Hugging Face)Status: currentPages: developers/pipelines, orchestrators/pipelinesInference
Inference
ai:conceptTabs: home, developers, gateways, resourcesExternal: Inference engine (Wikipedia)Status: currentPages: home/compute, developers/pipelines, resources/glossaryInflation
Inflation
livepeer:protocol, economic:reward, web3:tokenomicsTabs: orchestrators, lpt, resourcesExternal: Cryptoeconomics (Wikipedia)Status: currentPages: lpt/inflation, resources/glossaryInflation Adjustment (alpha)
Inflation Adjustment (alpha)
web3:tokenomicsTabs: lptContext: The inflation adjustment parameter ensures the system self-corrects: when fewer than 50% of LPT is bonded, inflation rises to attract stakers; when more is bonded, inflation falls.Also known as: alphaStatus: currentPages: lpt/inflation, lpt/economicsInflation Model
Inflation Model
livepeer:protocol, economic:rewardTabs: about, lptContext: The inflation model was designed so the protocol is self-regulating — no manual parameter changes are needed; the Inflation Adjustment (alpha) automatically nudges issuance each round.Status: currentPages: about/economics, lpt/inflationInflation Rate
Inflation Rate
economic:rewardTabs: community, lptContext: Livepeer’s inflation rate starts around 0.00042% per round and decreases by 0.00005% per round when bonding exceeds 50%, and increases otherwise, targeting long-run equilibrium participation.Status: currentPages: lpt/inflation, lpt/economicsInflationary Rewards
Inflationary Rewards
economic:rewardTabs: community, lptContext: Inflationary rewards are the supply-side incentive for participation; orchestrators must call the reward function each round to mint and distribute them, otherwise that round’s allocation is forfeited.Status: currentPages: community/staking, lpt/stakingIngest
Ingest
video:processingTabs: solutions, resourcesExternal: Real-Time Messaging Protocol (Wikipedia)Status: currentPages: solutions/livestreaming, resources/glossaryInteractive Media
Interactive Media
ai:applicationTabs: homeExternal: Interactive media (Wikipedia)Status: currentPages: home/ai-video, home/use-casesInterval-Based Payment
Interval-Based Payment
economic:paymentTabs: gatewaysContext: Interval-based payments reduce per-segment overhead by batching payment obligations into timed intervals. This is an alternative to per-segment ticket issuance in the Livepeer probabilistic micropayment system.Status: currentPages: gateways/payments, gateways/protocolIssuance
Issuance
web3:tokenomicsTabs: lptContext: Total LPT issuance per round equals inflation rate multiplied by current total supply; it flows first to orchestrators who called reward, then to their delegators proportionally.Status: currentPages: lpt/inflation, lpt/economicsJ
JavaScript
JavaScript
technical:languageTabs: developers, communityAlso known as: JSExternal: JavaScript (MDN Web Docs)Status: currentPages: developers/sdks/overview, community/sdksJob
Job
livepeer:protocolTabs: homeContext: Jobs are the atomic work unit in the Livepeer protocol; each job goes through a lifecycle of submission, orchestrator selection, execution, verification, and payment settlement.Status: currentPages: home/network, home/architectureJob Lifecycle
Job Lifecycle
livepeer:protocolTabs: aboutContext: Understanding the job lifecycle is fundamental to Livepeer’s architecture: a gateway submits a job, the network selects an orchestrator, work is performed off-chain, verified, and payment tickets are issued.Status: currentPages: about/protocol, about/architectureJSON (JavaScript Object Notation)
JSON (JavaScript Object Notation)
technical:protocolTabs: solutionsExternal: JSON (Wikipedia)Status: currentPages: solutions/apiJWT (JSON Web Token)
JWT (JSON Web Token)
technical:securityTabs: solutions, developersExternal: JSON Web Token (jwt.io)Status: currentPages: solutions/access-control, developers/access-controlK
Keyframe Interval
Keyframe Interval
video:encodingTabs: solutionsExternal: Group of pictures (Wikipedia)Status: currentPages: solutions/encoding, solutions/livestreamingKYC (Know Your Customer)
KYC (Know Your Customer)
operational:processTabs: developersExternal: Know your customer (Wikipedia)Status: currentPages: developers/access-controlKYO (Know Your Orchestrator)
KYO (Know Your Orchestrator)
operational:communityTabs: communityContext: KYO is a community education initiative run by Live Pioneers that publishes Q&A-format interviews with orchestrator operators, helping delegators make informed staking decisions.Status: currentPages: community/programs, community/eventsL
L1 Escrow
L1 Escrow
livepeer:contract, web3:chainTabs: lptContext: The L1 Escrow pairs with L2LPTGateway to form the canonical LPT bridge; tokens bridged to Arbitrum are locked in L1 Escrow until bridged back.Status: currentPages: lpt/bridging, lpt/arbitrumL2LPTGateway
L2LPTGateway
livepeer:contract, web3:chainTabs: lptContext: L2LPTGateway is the on-chain entry point for bridging LPT to Arbitrum, where Livepeer’s staking and governance contracts live; it pairs with an L1 Escrow contract on Ethereum mainnet.Status: currentPages: lpt/bridging, lpt/arbitrumLatency
Latency
video:playback, technical:infraTabs: home, solutions, gateways, resourcesExternal: Latency (Wikipedia)Status: currentPages: solutions/livestreaming, gateways/routing, resources/glossaryLayer 1
Layer 1
web3:chainTabs: aboutExternal: Layer-1 blockchain (Wikipedia)Status: currentPages: about/protocol, about/networkLayer 2 / Layer-2
Layer 2 / Layer-2
web3:chainTabs: home, about, resourcesExternal: Layer 2 (Ethereum.org)Also known as: Layer-2Status: currentPages: home/network, about/protocol, resources/glossaryLIP (Livepeer Improvement Proposal)
LIP (Livepeer Improvement Proposal)
operational:governance, livepeer:protocolTabs: home, about, developers, community, lptContext: LIPs follow a structured process from pre-proposal discussion on the governance forum through on-chain vote and execution; key examples include LIP-73 (Confluence), LIP-89 (on-chain governance), LIP-91/92 (treasury).Status: currentPages: about/governance, community/governance, lpt/governanceLIP-89
LIP-89
operational:governanceTabs: community, orchestrators, lptContext: LIP-89 was the foundational governance upgrade that established Livepeer’s on-chain voting system, treasury contract, and the delegated stake-weighted voting model currently in use.Status: currentPages: community/governance, lpt/governanceLIP-91
LIP-91
operational:governanceTabs: orchestratorsContext: LIP-91 activated the community treasury by directing a governable percentage of per-round LPT inflation into the on-chain treasury contract.Status: currentPages: orchestrators/protocol, orchestrators/upgradesLIP-92
LIP-92
operational:governanceTabs: orchestratorsContext: LIP-92 specified how orchestrators register AI capabilities on-chain via the AIServiceRegistry, enabling structured capability advertisement and gateway discovery of AI services.Status: currentPages: orchestrators/protocol, orchestrators/upgradesLISAR
LISAR
livepeer:entityTabs: communityContext: LISAR (Livepeer Infrastructure and Services Accountability Report) is the naming convention for the accountability reports published by certain SPEs; also used as the SPE identity for the infrastructure services workstream.Status: currentPages: community/governance, community/proposalsLive AI
Live AI
ai:conceptTabs: gatewaysContext: Live AI on Livepeer routes live stream frames through orchestrator GPU workers running models like StreamDiffusion. The gateway manages session continuity and orchestrator selection to maintain the low-latency budget required for interactive output.Status: currentPages: gateways/pipelines, gateways/routingLive Pioneers
Live Pioneers
operational:communityTabs: communityContext: Live Pioneers is an informal community programme for engaged LPT ecosystem participants; members produce the KYO interview series, publish staking guides, and represent the delegator perspective in governance.Status: currentPages: community/programs, community/indexLive-video-to-video
Live-video-to-video
ai:pipelineTabs: developers, orchestratorsExternal: StreamDiffusion GitHubStatus: currentPages: developers/pipelines, orchestrators/pipelinesLiveInfra
LiveInfra
livepeer:entityTabs: communityContext: LiveInfra is a treasury-funded Special Purpose Entity that operates the Community Arbitrum Node and other shared RPC/infrastructure services that reduce operational friction for ecosystem participants.Status: currentPages: community/projects, community/toolslivepeer-ai-js
livepeer-ai-js
livepeer:sdkTabs: communityContext: livepeer-ai-js is the official JavaScript SDK for integrating with the Livepeer AI Gateway API, exposing pipelines such as text-to-image and live-video-to-video to JS/TS applications.Status: currentPages: community/sdks, community/toolslivepeer-ai-python
livepeer-ai-python
livepeer:sdkTabs: communityContext: livepeer-ai-python is the official Python SDK for the Livepeer AI Gateway, enabling Python applications and ML workflows to dispatch inference jobs to the AI subnet.Status: currentPages: community/sdks, community/toolslivepeer-go
livepeer-go
livepeer:sdkTabs: communityContext: livepeer-go provides Go bindings for Livepeer Studio API operations including stream management, asset upload, and playback ID retrieval, targeting backend Go service integrations.Status: currentPages: community/sdks, community/toolslivepeer-js
livepeer-js
livepeer:sdk, livepeer:productTabs: communityContext: livepeer-js is the primary JavaScript SDK for Livepeer Studio, supporting stream creation, asset management, and playback integration in Node.js and browser environments.Also known as: Livepeer.jsStatus: currentPages: community/sdks, community/toolslivepeer-python-gateway
livepeer-python-gateway
livepeer:sdkTabs: gateways, developersContext: Maintained by the community as a lightweight alternative for developers building Python-native integrations with the Livepeer network.Status: currentPages: gateways/run-a-gateway/overview, developers/sdks/overviewLivepeer Actor
Livepeer Actor
livepeer:roleTabs: resourcesContext: The term “Livepeer Actor” is the broadest participant category, encompassing Protocol Actors (gateways, orchestrators, delegators) as well as ecosystem contributors, developers, and tooling operators.Status: currentPages: resources/glossary, resources/protocolLivepeer Cloud
Livepeer Cloud
livepeer:productTabs: developersContext: Livepeer Cloud is a hosted offering making it easier for developers to access Livepeer’s AI and video infrastructure without self-hosting gateway nodes.Status: currentPages: developers/index, developers/apiLivepeer Ecosystem
Livepeer Ecosystem
livepeer:entityTabs: resourcesContext: The Livepeer Ecosystem is broader than the protocol itself — it includes third-party tooling, community programs, governance participants, and complementary infrastructure providers.Status: currentPages: resources/glossary, resources/indexLivepeer Explorer
Livepeer Explorer
livepeer:toolTabs: community, lpt, resourcesContext: Livepeer Explorer is the primary web interface for delegators and orchestrators; it allows users to browse the active set, stake LPT, view reward histories, and interact with on-chain governance proposals without running node software.Status: currentPages: community/tools, lpt/staking, resources/glossaryLivepeer Foundation
Livepeer Foundation
livepeer:entityTabs: community, lpt, resourcesContext: The Livepeer Foundation is distinct from Livepeer Inc. It is member-governed and acts as a steward rather than a controller, funding SPEs, running the governance forum, and representing the ecosystem externally.Status: currentPages: community/governance, lpt/governance, resources/glossaryLivepeer Inc
Livepeer Inc
livepeer:entityTabs: home, communityContext: Livepeer Inc founded and launched the Livepeer network; following the establishment of the Livepeer Foundation, it transitioned from central steward to one contributor among many in the ecosystem.Status: currentPages: home/index, community/governanceLivepeer Network
Livepeer Network
livepeer:protocolTabs: solutions, resourcesContext: “Livepeer Network” refers to the running infrastructure layer — distinct from the Livepeer Protocol, which is the on-chain rule set. The network is the mesh of machines; the protocol governs their behavior.Status: currentPages: solutions/index, resources/glossaryLivepeer Protocol
Livepeer Protocol
livepeer:protocolTabs: resourcesContext: The Livepeer Protocol is the coordination and incentive layer — it does not perform video or AI compute itself but enforces correct behavior, reward distribution, and economic security for the network.Status: currentPages: resources/glossary, resources/protocolLivepeer Studio
Livepeer Studio
livepeer:productTabs: solutions, developersContext: Livepeer Studio is the primary product entry point for developers; it abstracts network complexity behind REST APIs and a web dashboard, handling stream management, transcoding, access control, analytics, and billing.Status: currentPages: solutions/index, developers/indexLivepeer.js
Livepeer.js
livepeer:sdkTabs: developersContext: Livepeer.js is the official JavaScript/TypeScript SDK for interacting with Livepeer Studio’s REST API, designed for Node.js and browser environments.Status: currentPages: developers/sdks, developers/apiLivepeerGovernor
LivepeerGovernor
livepeer:contract, web3:governanceTabs: lptContext: LivepeerGovernor was introduced in LIP-89 and is the authoritative contract for all binding on-chain governance decisions affecting the Livepeer protocol and treasury.Also known as: GovernorStatus: currentPages: lpt/contracts, lpt/governanceLivepeerNode
LivepeerNode
livepeer:protocolTabs: gatewaysContext: LivepeerNode is the central object in the gateway codebase. Understanding its structure is relevant when building custom gateway middleware or debugging gateway internals.Status: currentPages: gateways/code, gateways/architectureLivestream
Livestream
video:playbackTabs: solutionsExternal: Live streaming (Wikipedia)Status: currentPages: solutions/livestreaming, solutions/indexLLM (Large Language Model)
LLM (Large Language Model)
ai:conceptTabs: developers, orchestratorsExternal: Large language model (Wikipedia)Status: currentPages: developers/pipelines, orchestrators/pipelinesLoki
Loki
operational:monitoringTabs: orchestratorsExternal: Loki (Grafana Labs)Status: currentPages: orchestrators/monitoring, orchestrators/operationsLoRA (Low-Rank Adaptation)
LoRA (Low-Rank Adaptation)
ai:modelTabs: developersExternal: LoRA training (Hugging Face)Status: currentPages: developers/pipelines, developers/ai-gatewayLow-Latency
Low-Latency
video:streamingTabs: solutions, about, developersContext: Critical for interactive AI video applications — high latency breaks the real-time feedback loop between user input and AI-transformed output.Status: currentPages: solutions/ai-video, about/ai-video, developers/ai-pipelines/overviewLPT (Livepeer Token)
LPT (Livepeer Token)
livepeer:protocol, web3:tokenTabs: home, about, developers, orchestrators, community, lpt, resourcesContext: LPT is the foundational cryptoeconomic primitive of the protocol — it serves simultaneously as a staking bond (security), a governance weight (voting power), and an inflation-distributed reward token.Also known as: Livepeer TokenStatus: currentPages: home/staking, lpt/staking, resources/glossaryLPT emissions
LPT emissions
economic:reward, livepeer:protocolTabs: communityContext: LPT emissions are the primary economic incentive for participation; the per-round emission rate adjusts dynamically to push the bonding rate toward 50%, diluting non-staking holders.Status: currentPages: community/treasury, community/economicsLPMS (Livepeer Media Server)
LPMS (Livepeer Media Server)
livepeer:sdkTabs: resourcesContext: LPMS is the core media server component in go-livepeer; orchestrators and gateways use it to handle video stream ingestion, segment processing, and output generation.Also known as: Livepeer Media ServerStatus: currentPages: resources/glossary, resources/toolsM
Mainnet
Mainnet
web3:chainTabs: orchestratorsExternal: Mainnet (ethereum.org)Status: currentPages: orchestrators/protocolMarketplace
Marketplace
livepeer:productTabs: home, gatewaysContext: Orchestrators advertise capabilities and prices, gateways select and route work, and payment flows coordinate supply with demand.Status: currentPages: home/network, gateways/economicsMaxPrice
MaxPrice
livepeer:config, economic:pricingTabs: orchestratorsContext: MaxPrice acts as a hard gate in orchestrator selection. Orchestrators set their own pricePerUnit; gateways set their MaxPrice to filter out orchestrators whose prices exceed the budget.Also known as: MaxPricePerUnitStatus: currentPages: orchestrators/pricing, orchestrators/configMaxPricePerCapability
MaxPricePerCapability
livepeer:config, economic:pricingTabs: gatewaysContext: MaxPricePerCapability lets gateway operators fine-tune spending limits per AI task, for example paying more for a high-quality image-to-video pipeline while capping spend on cheaper text-to-image tasks.Status: currentPages: gateways/pricing, gateways/configMaxPricePerUnit
MaxPricePerUnit
livepeer:config, economic:pricingTabs: gatewaysContext: MaxPricePerUnit acts as a hard gate in orchestrator selection. Setting it too low reduces the available orchestrator pool; too high increases cost. It can be expressed in wei or as a USD-denominated value with automatic conversion.Also known as: MaxPriceStatus: currentPages: gateways/pricing, gateways/configMerkle Mine
Merkle Mine
web3:conceptTabs: community, lpt, resourcesContext: The Merkle Mine was used to distribute genesis supply broadly across the Ethereum community at Livepeer’s 2018 mainnet launch, using a Merkle tree of eligible addresses and on-chain proof verification.Status: currentPages: lpt/tokenomics, resources/glossaryMicropayments
Micropayments
economic:paymentTabs: home, orchestratorsExternal: Micropayment (Wikipedia)Status: currentPages: home/network, orchestrators/paymentsMicropayment Ticket
Micropayment Ticket
economic:paymentTabs: gatewaysContext: Gateways issue micropayment tickets to orchestrators as work is performed. The lottery-based mechanism means only a fraction of tickets result in on-chain transactions, dramatically reducing gas costs while preserving expected-value fairness.Also known as: Payment ticket, probabilistic micropayment ticketStatus: currentPages: gateways/payments, gateways/protocolMilestone-based Grants
Milestone-based Grants
economic:treasuryTabs: communityContext: Milestone-based grants are used by the Livepeer Foundation and treasury to reduce risk; SPEs and grantees receive funding tranches as they hit defined milestones and submit accountability reports.Status: currentPages: community/treasury, community/programsMinter Contract
Minter Contract
livepeer:contractTabs: about, lpt, resourcesContext: The Minter is the on-chain treasury and issuance contract; it releases newly minted LPT to the BondingManager each round and holds gateway ETH deposits until tickets are redeemed. Called by the BondingManager at each reward call to calculate and mint the round’s inflationary LPT allocation.Also known as: MinterStatus: currentPages: about/contracts, lpt/contracts, resources/glossaryMistServer
MistServer
technical:infraTabs: solutions, communityExternal: MistServerStatus: currentPages: solutions/architecture, community/toolsModel
Model
ai:conceptTabs: home, developers, gateways, resourcesExternal: Machine learning (Wikipedia)Status: currentPages: home/ai-video, developers/pipelines, resources/glossaryModel Card
Model Card
ai:conceptTabs: developersExternal: Model Cards (Hugging Face)Status: currentPages: developers/pipelines, developers/ai-gatewayModel ID
Model ID
stabilityai/stable-diffusion-xl-base-1.0.Tags: ai:conceptTabs: developersExternal: Model Cards (Hugging Face)Status: currentPages: developers/pipelines, developers/ai-gatewayModel Warmth
Model Warmth
ai:concept, livepeer:configTabs: orchestratorsContext: Orchestrators typically support one warm model per GPU during the current beta phase. The warmth status of each model is configured in aiModels.json and determines whether a model can serve requests immediately or incurs a cold-start delay.Status: currentPages: orchestrators/ai, orchestrators/performanceMP4
MP4
video:playbackTabs: solutionsExternal: MP4 file format (Wikipedia)Status: currentPages: solutions/vod, solutions/encodingMultimodal
Multimodal
ai:conceptTabs: developersExternal: Multimodal learning (Wikipedia)Status: currentPages: developers/pipelines, developers/ai-gatewayMultistream
Multistream
video:studioTabs: solutionsContext: Livepeer Studio’s Multistream feature lets developers configure multiple target URLs and stream keys on a Stream object; the platform fans out the ingest to all targets automatically.Status: currentPages: solutions/multistream, solutions/livestreamingN
NaaP (Network as a Platform)
NaaP (Network as a Platform)
livepeer:productTabs: developers, gatewaysContext: NaaP enables gateway operators to expose Livepeer infrastructure to third-party developers with managed access control and billing, turning a single gateway deployment into a platform business. Repository: github.com/livepeer/naap.Status: currentPages: developers/architecture, gateways/architectureNetwork Effects
Network Effects
economic:business, web3:tokenomicsTabs: resourcesExternal: Network effect (Wikipedia)Status: currentPages: resources/glossary, resources/economicsNode
Node
technical:infraTabs: home, resourcesExternal: Node networking (Wikipedia)Status: currentPages: home/network, resources/glossaryNon-custodial
Non-custodial
web3:conceptTabs: lptExternal: Proof of stake (ethereum.org)Status: currentPages: lpt/staking, lpt/securityNPC (Non-Player Character)
NPC (Non-Player Character)
ai:applicationTabs: homeExternal: Non-player character (Wikipedia)Status: currentPages: home/ai-video, home/use-casesNVDEC
NVDEC
technical:infraTabs: orchestratorsExternal: NVDEC (Wikipedia)Status: currentPages: orchestrators/transcoding, orchestrators/setupNVENC
NVENC
technical:infraTabs: orchestratorsExternal: NVENC (Wikipedia)Status: currentPages: orchestrators/transcoding, orchestrators/setupO
O-T Split
O-T Split
livepeer:deploymentTabs: orchestratorsContext: Enables security isolation and multi-GPU scaling. The orchestrator process uses the -orchestrator flag; the transcoder uses -transcoder. Authentication between them uses the orchSecret shared secret.Status: currentPages: orchestrators/architecture, orchestrators/configOBS (Open Broadcaster Software)
OBS (Open Broadcaster Software)
video:playbackTabs: solutionsExternal: OBS Studio (Wikipedia)Status: currentPages: solutions/livestreaming, solutions/guidesOff-chain
Off-chain
web3:conceptTabs: about, resourcesExternal: Off-chain (ethereum.org glossary)Status: currentPages: about/protocol, resources/glossaryOff-Chain Gateway
Off-Chain Gateway
livepeer:deploymentTabs: gatewaysContext: Off-chain is a sustainable production mode for gateways (unlike off-chain orchestrators, which are only for testing). An off-chain gateway holds no ETH; a community-hosted remote signer at signer.eliteencoder.net is publicly available and free to use.Status: currentPages: gateways/modesOllama
Ollama
ai:modelTabs: developers, orchestratorsExternal: OllamaStatus: currentPages: developers/pipelines, orchestrators/aiOn-chain
On-chain
web3:conceptTabs: about, resourcesExternal: On-chain (ethereum.org glossary)Status: currentPages: about/protocol, resources/glossaryOn-Chain Gateway
On-Chain Gateway
livepeer:deploymentTabs: gatewaysContext: On-chain gateways require ETH deposited on Arbitrum for the payment deposit and reserve, and use protocol-based orchestrator discovery. This mode provides access to the full registered orchestrator pool but requires crypto-wallet management.Status: currentPages: gateways/modesOn-chain Treasury
On-chain Treasury
livepeer:protocol, economic:treasuryTabs: community, lpt, resourcesContext: The on-chain treasury was established by LIP-89 and LIP-92 and receives a governance-controlled percentage of each round’s LPT inflation (Treasury Reward Cut Rate); it is disbursed via LivepeerGovernor votes to SPEs, grants, and bounties.Also known as: Community TreasuryStatus: currentPages: community/treasury, lpt/treasury, resources/glossaryOpen Source
Open Source
web3:conceptTabs: resourcesExternal: Open-source software (Wikipedia)Status: currentPages: resources/glossary, resources/indexOperational Mode
Operational Mode
livepeer:config, livepeer:deploymentTabs: gatewaysContext: Operational mode is an independent axis from node type and setup type. Both on-chain and off-chain gateways can route video, AI, or dual workloads. Off-chain is a valid production configuration for gateways.Status: currentPages: gateways/modes, gateways/configOperator Market
Operator Market
livepeer:protocolTabs: lptContext: The operator market is Livepeer’s two-sided marketplace dynamic — delegators allocate stake to orchestrators they trust, creating economic incentives for operators to compete on quality and price.Status: currentPages: lpt/staking, lpt/economicsOrchestrator
Orchestrator
livepeer:roleTabs: home, about, solutions, developers, gateways, orchestrators, lpt, community, resourcesContext: Orchestrators are the core supply-side participants in Livepeer. They handle protocol interaction, job routing, payment negotiation, and capability advertisement; may run their own transcoder subprocess or delegate to remote transcoder workers. Their total bonded stake determines active set membership, reward share, and governance voting weight.Status: currentPages: home/network, about/protocol, orchestrators/index, resources/glossaryOrchestrator Discovery
Orchestrator Discovery
-orchAddr flags.Tags: livepeer:protocolTabs: gateways, orchestratorsContext: On-chain gateways use the ServiceRegistry contract on Arbitrum to discover registered orchestrators and their service URIs. Off-chain gateways bypass discovery and connect directly to specified addresses.Status: currentPages: gateways/routing, orchestrators/discoveryOrchestratorInfo
OrchestratorInfo
livepeer:configTabs: orchestratorsContext: OrchestratorInfo is exchanged during gateway-orchestrator negotiation. It includes the orchestrator’s pricePerUnit, supported AI capabilities, ticket parameters, and service URI.Status: currentPages: orchestrators/code, orchestrators/protocolorchSecret
orchSecret
livepeer:configTabs: orchestratorsContext: Set via the -orchSecret CLI flag on both the orchestrator and transcoder. Must match exactly. Prevents unauthorised nodes from connecting to an orchestrator as transcoders.Status: currentPages: orchestrators/config, orchestrators/securityOSI Model
OSI Model
technical:infraTabs: aboutExternal: OSI model (Wikipedia)Status: currentPages: about/architectureOutput Profile
Output Profile
video:encodingTabs: orchestratorsExternal: Advanced Video Coding (Wikipedia)Status: currentPages: orchestrators/transcoding, orchestrators/configOverhead
Overhead
economic:pricing, operational:processTabs: orchestratorsContext: In Livepeer pricing, overhead specifically refers to the estimated ticket redemption cost divided by the face value, expressed as a percentage. The autoAdjustPrice flag incorporates overhead into automatic price calculations.Status: currentPages: orchestrators/performance, orchestrators/economicsP
Passing threshold
Passing threshold
operational:governanceTabs: communityContext: Livepeer governance requires a passing threshold in addition to quorum; if insufficient stake votes in favor, the proposal fails even with high participation.Status: currentPages: community/governancePay-per-Pixel
Pay-per-Pixel
economic:pricingTabs: aboutContext: Pay-per-pixel is the fundamental unit of exchange in Livepeer’s transcoding marketplace; it allows apples-to-apples pricing across different resolutions and bitrates by normalizing to pixels processed.Status: currentPages: about/economicsPayment Channel
Payment Channel
economic:paymentTabs: aboutExternal: State channels (ethereum.org)Status: currentPages: about/payments, about/protocolPayment Ticket
Payment Ticket
economic:payment, livepeer:protocolTabs: about, lpt, resourcesContext: Payment tickets are Livepeer’s mechanism for streaming micropayments without per-segment gas costs; the lottery design means only a statistically appropriate fraction of tickets win, amortizing on-chain fees across many payments.Also known as: TicketStatus: currentPages: about/payments, lpt/payments, resources/glossaryPending Rewards
Pending Rewards
economic:rewardTabs: lptContext: Pending rewards accumulate each round an orchestrator calls reward; delegators do not need to claim every round but must claim before certain actions (such as moving stake) to avoid losing accrued amounts.Status: draftPages: lpt/staking, lpt/delegationPer Pixel (Price Per Pixel)
Per Pixel (Price Per Pixel)
livepeer:economicsTabs: about, gateways, orchestratorsContext: A 4K frame costs more to process than a 720p frame because it contains more pixels; enables pricing that scales with workload complexity.Status: currentPages: about/economics, gateways/pricing, orchestrators/pricingPer-Pixel Pricing
Per-Pixel Pricing
economic:pricingTabs: gatewaysExternal: Pay-per-pixel (Livepeer Forum)Status: currentPages: gateways/pricing, gateways/transcodingPer-Request Pricing
Per-Request Pricing
economic:pricingTabs: gatewaysExternal: Livepeer AI pipelinesStatus: currentPages: gateways/pricing, gateways/pipelinesPer Round
Per Round
livepeer:economicsTabs: about, lpt, orchestratorsContext: Key unit for orchestrator reward calculations, delegator stake checkpoints, and LPT inflation scheduling.Status: currentPages: about/protocol, lpt/staking, orchestrators/stakingPerformance Score
Performance Score
livepeer:protocol, operational:monitoringTabs: orchestratorsContext: Performance score is tracked per-gateway and influences routing decisions. A low score from failed transcodes or high latency reduces the probability of being selected for future jobs.Status: currentPages: orchestrators/discovery, orchestrators/performancePermissionless
Permissionless
web3:conceptTabs: homeExternal: Web3 — permissionless (Ethereum.org)Status: currentPages: home/network, home/indexPixel
Pixel
video:encodingTabs: orchestratorsExternal: Pixel (Wikipedia)Status: currentPages: orchestrators/transcoding, orchestrators/pricingpixelsPerUnit
pixelsPerUnit
livepeer:config, economic:pricingTabs: orchestratorsContext: Used in conjunction with pricePerUnit. Setting a larger pixelsPerUnit value effectively lowers the per-pixel price while keeping the per-unit number manageable. Defaults to 1 pixel per unit.Status: currentPages: orchestrators/pricing, orchestrators/configPipeline
Pipeline
livepeer:protocol, ai:conceptTabs: gateways, resourcesContext: On Livepeer, a pipeline is the combination of a pipeline type (e.g., text-to-image, live-video-to-video) and a specific model ID. Gateways match incoming AI requests to orchestrators advertising the corresponding capability.Status: currentPages: gateways/pipelines, resources/glossaryPlayback ID
Playback ID
video:studioTabs: solutionsContext: Every Stream and Asset in Livepeer Studio is assigned a Playback ID at creation; clients pass this ID to the playback API or embed it in the player to resolve the correct HLS or WebRTC URL.Status: currentPages: solutions/playback, solutions/apiPlayback Policy
Playback Policy
video:studio, technical:securityTabs: solutionsContext: Livepeer Studio playback policies are configured per-stream or per-asset; setting a policy to jwt mode requires every viewer to present a signed JWT from the application’s signing key before the player can retrieve a valid playback URL.Status: currentPages: solutions/access-control, solutions/apiPlayer
Player
video:playbackTabs: solutionsContext: The Livepeer Player is a hosted iframe-embeddable player and a React SDK component (@livepeer/react) that resolves playback from a Playback ID, handles ABR switching, and supports access-controlled streams without custom player configuration.Status: currentPages: solutions/player, solutions/playbackPM (Probabilistic Micropayment)
PM (Probabilistic Micropayment)
economic:paymentTabs: orchestratorsContext: The PM system is the core payment mechanism in Livepeer. Most tickets are non-winning; over time, the expected value of winning tickets equals the fair payment for work performed. Orchestrators batch redemptions to optimise gas costs.Status: currentPages: orchestrators/payments, orchestrators/protocolPool
Pool
livepeer:deploymentTabs: orchestratorsContext: A pool allows orchestrators to scale beyond a single machine. The pool operator runs the on-chain orchestrator node and handles staking, reward calling, and ticket redemption. Pool workers contribute GPU compute and receive off-chain payouts from the operator.Status: currentPages: orchestrators/architecture, orchestrators/operationsPool Operator
Pool Operator
livepeer:deploymentTabs: orchestratorsContext: Pool operators require infrastructure reliability and community trust. They stake LPT to the active set threshold and distribute earnings to pool workers via off-chain agreements.Status: currentPages: orchestrators/architecture, orchestrators/operationsPool Worker
Pool Worker
livepeer:deploymentTabs: orchestratorsContext: Pool workers do not hold LPT or interact with the protocol directly — the pool operator stakes on their behalf. Workers connect to the orchestrator using the -orchAddr and -orchSecret flags.Also known as: Pool nodeStatus: currentPages: orchestrators/architecture, orchestrators/operationsPre-Proposal
Pre-Proposal
operational:governanceTabs: communityContext: Pre-proposals allow the Livepeer community to give early feedback on governance ideas before the author commits to the formal LIP process, reducing wasted effort on unpopular proposals.Status: currentPages: community/governancePrice Feed
Price Feed
livepeer:config, economic:pricingTabs: orchestratorsContext: Orchestrators using USD pricing fetch the current ETH/USD rate from a price feed service to dynamically adjust their wei-denominated pricePerUnit as ETH price fluctuates.Status: currentPages: orchestrators/pricing, orchestrators/configPrice per pixel
Price per pixel
economic:pricingTabs: community, lptContext: Price per pixel is the standard unit of comparison for orchestrator pricing in Livepeer’s transcoding marketplace; orchestrators set their pricePerUnit and pixelsPerUnit to express a per-pixel rate.Status: currentPages: community/economics, lpt/pricingpricePerCapability
pricePerCapability
livepeer:config, economic:pricingTabs: orchestratorsContext: Allows orchestrators to charge different rates for different AI pipelines based on compute intensity. For example, a text-to-image pipeline with a large model can be priced higher than a lightweight audio-to-text pipeline.Status: currentPages: orchestrators/pricing, orchestrators/aipricePerGateway
pricePerGateway
livepeer:config, economic:pricingTabs: orchestratorsContext: Useful for commercial relationships where specific gateways receive preferential pricing. Configured as a JSON map from gateway Ethereum addresses to price overrides.Status: currentPages: orchestrators/pricing, orchestrators/configpricePerUnit
pricePerUnit
livepeer:config, economic:pricingTabs: orchestratorsContext: The primary pricing parameter for video transcoding. Gateways with -maxPricePerUnit below this value will not route work to the orchestrator. Can be set in wei directly or with a USD target using a price feed.Status: currentPages: orchestrators/pricing, orchestrators/configProbabilistic Micropayments
Probabilistic Micropayments
economic:paymentTabs: home, about, gateways, orchestrators, communityExternal: Livepeer payments core conceptsContext: Livepeer’s probabilistic micropayment system lets gateways pay orchestrators per video segment at sub-cent amounts without incurring Ethereum gas fees on every payment; the expected value of tickets matches the service cost.Status: currentPages: home/payments, about/payments, gateways/paymentsProfile
Profile
video:encodingTabs: gatewaysExternal: Advanced Video Coding (Wikipedia)Status: currentPages: gateways/transcoding, gateways/configPrometheus
Prometheus
operational:monitoringTabs: communityExternal: PrometheusStatus: currentPages: community/tools, community/monitoringProof of Utility
Proof of Utility
livepeer:protocol, web3:conceptTabs: home, communityExternal: Livepeer PrimerContext: Livepeer’s proof-of-utility mechanism verifies that orchestrators actually transcoded video or ran AI inference rather than simply holding stake, ensuring that rewards are tied to productive contributions.Status: currentPages: home/network, community/networkProof-of-Stake
Proof-of-Stake
web3:conceptTabs: about, lptExternal: Proof-of-stake (ethereum.org)Status: currentPages: about/protocol, lpt/protocolProposer Bond
Proposer Bond
web3:governance, economic:treasuryTabs: lptContext: The proposer bond deters spam proposals by requiring skin-in-the-game from proposal authors; it does not lock additional tokens — the proposer simply needs at least 100 LPT bonded.Status: currentPages: lpt/governance, lpt/proposalsProtocol Layer
Protocol Layer
livepeer:protocol, web3:chainTabs: developers, gatewaysContext: The Protocol Layer is the blockchain foundation underpinning Livepeer — developers building at the application level interact with it indirectly through the SDK, while protocol developers interact with it directly via smart contracts.Status: currentPages: developers/protocol, gateways/protocolProvenance
Provenance
technical:securityTabs: solutionsExternal: C2PA specificationStatus: currentPages: solutions/provenance, solutions/aiPyTorch
PyTorch
ai:frameworkTabs: developers, orchestratorsExternal: PyTorch (Wikipedia)Also known as: TorchStatus: currentPages: developers/pipelines, orchestrators/aiPyTrickle
PyTrickle
livepeer:sdkTabs: developersContext: PyTrickle is the official Python SDK for developers building real-time AI video applications on Livepeer, providing the FrameProcessor interface for per-frame model inference.Status: currentPages: developers/sdks, developers/streamingQ
Quadratic Funding
Quadratic Funding
economic:treasuryTabs: community, lptExternal: Quadratic voting (Wikipedia)Status: currentPages: community/treasury, lpt/proposalsQuality Ladder
Quality Ladder
video:processingTabs: resourcesExternal: Encoding ladder (Cloudinary glossary)Status: currentPages: resources/glossary, resources/encodingQuorum
Quorum
livepeer:protocol, web3:governance, operational:governanceTabs: about, community, lptContext: Livepeer governance requires a quorum threshold to be met before a proposal outcome is valid; if quorum is not reached, the proposal fails regardless of the for/against split. Introduced as part of LIP-89.Status: currentPages: about/governance, community/governance, lpt/governanceR
Real-time
Real-time
video:playback, ai:conceptTabs: home, developers, community, resourcesExternal: WebRTC (Wikipedia)Also known as: Real-time AI, Real-time video AIStatus: currentPages: home/streaming, developers/pipelines, resources/glossaryRebonding
Rebonding
web3:tokenomicsTabs: about, lptExternal: Livepeer bonding overviewAlso known as: Rebond, RedelegationStatus: currentPages: about/staking, lpt/delegationRebuffer Ratio
Rebuffer Ratio
video:playbackTabs: solutionsExternal: The four elements of video performance (Mux)Status: currentPages: solutions/analytics, solutions/playbackRecording
Recording
video:studioTabs: solutionsContext: Livepeer Studio supports per-stream recording configuration; when enabled, each broadcast session is captured and, upon stream end, made available as a new Asset with its own playback ID.Status: currentPages: solutions/livestreaming, solutions/recordingRedeemer
Redeemer
livepeer:role, economic:paymentTabs: orchestratorsContext: In production deployments, orchestrators typically run an automated redeemer process that monitors for winning tickets and submits them on-chain. Redemption costs gas, so batching is common.Status: currentPages: orchestrators/payments, orchestrators/protocolRedemption
Redemption
economic:paymentTabs: gatewaysContext: Orchestrators (or their redeemer process) submit winning tickets to TicketBroker to claim ETH. The gateway’s deposit and reserve fund these redemptions. High redemption frequency relative to deposit size is a signal to top up.Status: currentPages: gateways/payments, gateways/protocolRemote Signer
Remote Signer
technical:securityTabs: gateways, orchestrators, resourcesContext: In an on-chain gateway, the signer is typically a local keystore file. In an off-chain gateway, signing is delegated to a remote signer service. A community-hosted remote signer at signer.eliteencoder.net is publicly available and free to use.Status: currentPages: gateways/security, resources/glossaryRendition
Rendition
video:processingTabs: solutions, gateways, orchestrators, resourcesExternal: Video rendition (Cloudinary Glossary)Status: currentPages: solutions/transcoding, gateways/transcoding, resources/glossaryReputation
Reputation
livepeer:protocolTabs: resourcesContext: Reputation in Livepeer is not a single on-chain score but a composite of off-chain performance metrics — success rate, latency, and transcode fail rate — that gateways use in their orchestrator selection weighting.Status: currentPages: resources/glossary, resources/protocolReserve
Reserve
economic:paymentTabs: gatewaysContext: An on-chain gateway must fund both a deposit (normal operating balance) and a reserve (safety backstop). The reserve prevents orchestrators from being left unpaid if the deposit runs out between top-ups.Status: currentPages: gateways/paymentsResolution
Resolution
video:encodingTabs: solutionsExternal: Display resolution (Wikipedia)Status: currentPages: solutions/encoding, solutions/transcodingREST (Representational State Transfer)
REST (Representational State Transfer)
technical:protocolTabs: solutionsExternal: REST (Wikipedia)Status: currentPages: solutions/apiRetroactive Funding
Retroactive Funding
economic:treasuryTabs: community, lptStatus: currentPages: community/treasury, lpt/proposalsReward
Reward
economic:rewardTabs: homeContext: Rewards in Livepeer have two components: inflationary LPT minted each round (distributed proportional to stake) and ETH fees from winning micropayment tickets (distributed via fee cut/share parameters set by each orchestrator).Status: currentPages: home/staking, home/networkReward Call
Reward Call
Reward()) that an active orchestrator must submit each round to mint and distribute new LPT inflation rewards to itself and its delegators.Tags: livepeer:protocol, economic:rewardTabs: about, developers, orchestrators, community, lptContext: Reward calls are an orchestrator’s operational responsibility each round; missing reward calls means forfeiting inflationary LPT for that round, which also harms delegators who rely on that income. Gas cost on Arbitrum is approximately 0.12 per call.Status: currentPages: about/staking, orchestrators/staking, lpt/stakingReward Cut
Reward Cut
economic:rewardTabs: about, orchestrators, community, lpt, resourcesContext: Reward cut is a key parameter orchestrators configure to attract delegators; a lower reward cut means orchestrators pass more LPT to stakers, while a higher cut means they keep more for themselves. Separate from fee cut.Status: currentPages: about/staking, orchestrators/staking, resources/glossaryRFP (Request for Proposal)
RFP (Request for Proposal)
operational:governanceTabs: communityContext: RFPs in Livepeer are used to solicit competitive bids for funded ecosystem work such as tooling, infrastructure, or documentation; typically posted in the Treasury Forum with defined scope and budget.Status: currentPages: community/treasury, community/governanceRollups
Rollups
web3:conceptTabs: resourcesExternal: Rollups (Ethereum docs)Status: currentPages: resources/glossary, resources/protocolRoom
Room
video:studioTabs: solutionsContext: The Studio Room API creates and manages multi-party WebRTC sessions; each Room has a unique ID and participant tokens, and Livepeer handles the signaling and media routing infrastructure.Status: currentPages: solutions/webrtc, solutions/apiRound
Round
livepeer:protocolTabs: about, orchestrators, community, lpt, resourcesContext: Rounds are Livepeer’s fundamental time unit for protocol operations; reward calls, active set elections, and inflation adjustments all happen on a per-round basis. Each round is approximately 5,760 Arbitrum blocks.Status: currentPages: about/protocol, lpt/protocol, resources/glossaryRoundsManager
RoundsManager
livepeer:contractTabs: orchestrators, lptContext: RoundsManager is called at the start of each round initialization and interacts with BondingManager and Minter to trigger reward distribution and inflation calculation.Status: currentPages: orchestrators/contracts, lpt/contractsRPC (Remote Procedure Call)
RPC (Remote Procedure Call)
technical:protocolTabs: communityExternal: Remote procedure call (Wikipedia)Status: currentPages: community/tools, community/networkRTMP (Real-Time Messaging Protocol)
RTMP (Real-Time Messaging Protocol)
video:protocolTabs: about, solutions, developers, gateways, orchestrators, resourcesExternal: RTMP (Wikipedia)Status: currentPages: about/transcoding, solutions/livestreaming, resources/glossaryRTMPS
RTMPS
video:protocolTabs: solutionsExternal: RTMP (Wikipedia)Status: currentPages: solutions/livestreaming, solutions/ingestRTX (NVIDIA RTX)
RTX (NVIDIA RTX)
technical:hardwareTabs: gateways, orchestrators, developersAlso known as: GeForce RTXExternal: NVIDIA GeForce graphics cardsStatus: currentPages: gateways/run-a-gateway/requirements/setup, orchestrators/run-an-orchestrator/requirementsS
SAM 2
SAM 2
ai:modelTabs: developersExternal: SAM 2 (Hugging Face)Status: currentPages: developers/pipelines, developers/ai-gatewaySampler
Sampler
ai:conceptTabs: developersExternal: Scheduler features (Hugging Face)Status: currentPages: developers/pipelinesScalability
Scalability
technical:infraTabs: homeExternal: Scalability (Wikipedia)Status: currentPages: home/network, home/indexScaling
Scaling
operational:processTabs: gatewaysExternal: Scalability (Wikipedia)Status: currentPages: gateways/architecture, gateways/operationsSDXL (Stable Diffusion XL)
SDXL (Stable Diffusion XL)
ai:modelTabs: developers, resourcesExternal: SDXL (Hugging Face)Also known as: Stable Diffusion XLStatus: currentPages: developers/pipelines, resources/glossarySDK (Software Development Kit)
SDK (Software Development Kit)
technical:devTabs: solutionsExternal: Software development kit (Wikipedia)Status: currentPages: solutions/sdks, solutions/apiSegment
Segment
livepeer:protocol, video:processingTabs: about, solutions, gateways, orchestrators, resourcesExternal: HTTP Live Streaming (Wikipedia)Status: currentPages: about/transcoding, gateways/transcoding, resources/glossarySegmentation
Segmentation
video:processing, ai:pipelineTabs: solutions, developers, orchestratorsExternal: Image segmentation (Wikipedia)Also known as: Segmentation (AI)Status: currentPages: solutions/transcoding, developers/pipelines, orchestrators/pipelinesSelf-Hosted
Self-Hosted
technical:deploymentTabs: developers, gatewaysExternal: Self-hosting (Wikipedia)Status: currentPages: developers/self-hosted, gateways/run-a-gateway/overviewService Margin
Service Margin
economic:pricingTabs: gatewaysContext: Gateway operators running NaaP or gateway-as-a-service offerings use a service margin to cover infrastructure, development, and operational overhead while remaining price-competitive with direct orchestrator costs.Status: currentPages: gateways/pricing, gateways/economicsService URI
Service URI
livepeer:config, livepeer:protocolTabs: about, orchestratorsContext: The Service URI is how orchestrators advertise their network address; it is registered in the ServiceRegistry smart contract so gateways can look up orchestrators by their on-chain identity and contact them directly. Must be publicly reachable; format is typically https://your-domain:8935.Status: currentPages: about/protocol, orchestrators/configServiceRegistry
ServiceRegistry
livepeer:contractTabs: gateways, orchestratorsContext: The ServiceRegistry is the on-chain source of truth for orchestrator endpoints. On-chain gateways query it at startup and during session establishment; off-chain gateways bypass it entirely by using -orchAddr.Status: currentPages: gateways/protocol, orchestrators/contractsSession
Session
livepeer:protocol, video:studioTabs: about, solutions, gateways, orchestratorsContext: Sessions in Livepeer represent the active working relationship between a gateway and a chosen orchestrator; payment tickets are issued within a session. In Livepeer Studio, each broadcast period on a Stream object creates a new Session with its own metrics, recording, and viewership data.Status: currentPages: about/protocol, gateways/routing, solutions/livestreamingSettlement
Settlement
economic:paymentTabs: gatewaysContext: Settlement occurs when an orchestrator redeems a winning ticket, converting the probabilistic payment into an actual ETH transfer. The gateway’s deposit funds these settlements; the reserve backstops them.Status: currentPages: gateways/paymentsSigning Key
Signing Key
video:studio, technical:securityTabs: solutionsContext: Developers create Signing Keys in the Studio dashboard or via API; the private key signs viewer JWTs server-side, and Livepeer verifies signatures against the registered public key before granting playback access.Status: currentPages: solutions/access-control, solutions/apiSigner
Signer
technical:securityTabs: gatewaysContext: In an on-chain gateway, the signer is typically a local keystore file. In an off-chain gateway, signing is delegated to a remote signer service. The signer never needs to hold large ETH balances in the off-chain model.Status: currentPages: gateways/security, gateways/configSiphon
Siphon
livepeer:deploymentTabs: orchestratorsContext: In orchestrator architecture, the siphon routes incoming jobs between video transcoding and AI inference paths. It can also describe a minimal transcoder deployment that connects to a remote orchestrator to expose local GPU resources.Status: currentPages: orchestrators/architecture, orchestrators/routingSLA (Service Level Agreement)
SLA (Service Level Agreement)
technical:operationsTabs: developers, gatewaysExternal: Service-level agreement (Wikipedia)Status: currentPages: developers/ai-gateway/overview, gateways/run-a-gateway/overviewSLAM (Simultaneous Localization and Mapping)
SLAM (Simultaneous Localization and Mapping)
ai:applicationTabs: homeExternal: Simultaneous localization and mapping (Wikipedia)Status: currentPages: home/ai-video, home/use-casesSlashing
Slashing
livepeer:protocol, web3:tokenomics, economic:rewardTabs: about, orchestrators, community, lpt, resourcesExternal: Livepeer whitepaperContext: Slashing conditions include failing transcoding verification, skipping required verifications, or sustained underperformance. Both the orchestrator’s self-stake and delegated stake are at risk, which incentivizes delegators to select reliable orchestrators.Status: currentPages: about/protocol, orchestrators/protocol, resources/glossarySlashing Conditions
Slashing Conditions
livepeer:protocolTabs: resourcesContext: Slashing Conditions are encoded in the Livepeer whitepaper and protocol contracts. They create economic accountability for orchestrators by making misbehavior financially costly, proportional to their bonded stake.Status: currentPages: resources/glossary, resources/protocolSmart Contract
Smart Contract
web3:conceptTabs: home, developersExternal: Smart contracts (Ethereum.org)Status: currentPages: home/network, developers/protocolSmoke Test
Smoke Test
operational:monitoringTabs: orchestratorsExternal: Smoke testing (Wikipedia)Status: currentPages: orchestrators/ai, orchestrators/testingSnowmelt
Snowmelt
livepeer:upgradeTabs: homeContext: Snowmelt is the first named milestone in Livepeer’s phased roadmap, representing the earliest protocol design and testnet stage before Tributary (beta) and mainnet deployment.Status: currentPages: home/upgradesSolo Operator
Solo Operator
livepeer:deploymentTabs: orchestratorsContext: The standard deployment for most individual orchestrators. Full control and full responsibility for staking, reward calling, ticket redemption, and compute. Can run in video, AI, or dual mode.Status: currentPages: orchestrators/modes, orchestrators/setupSolidity
Solidity
technical:dev, web3:conceptTabs: developersExternal: Solidity (Wikipedia)Status: currentPages: developers/protocol, developers/contractsSPE (Special Purpose Entity)
SPE (Special Purpose Entity)
livepeer:entity, operational:governanceTabs: home, about, solutions, developers, orchestrators, lpt, community, resourcesContext: SPEs are Livepeer’s primary mechanism for directing on-chain treasury funds; each SPE has a specific mandate (e.g., AI compute, gateway tooling, governance coordination) and reports progress to the community via accountability documents (e.g., LISARs).Status: currentPages: community/governance, lpt/treasury, resources/glossaryStable Diffusion
Stable Diffusion
ai:modelTabs: orchestratorsExternal: Stable Diffusion (Wikipedia)Status: currentPages: orchestrators/pipelines, orchestrators/aiStableLab
StableLab
livepeer:entityTabs: communityContext: StableLab is a professional governance consultancy that was appointed as the inaugural GovWorks Chair to establish governance processes, review proposals, and publish governance summaries for the Livepeer community.Status: currentPages: community/governance, community/partnersStake
Stake
web3:tokenomicsTabs: lpt, resourcesContext: Stake is the core unit of participation in Livepeer — all economic weight, voting power, and reward distribution derive from how much LPT is staked to active orchestrators.Also known as: Bonded stakeStatus: currentPages: lpt/staking, resources/glossaryStake Weight
Stake Weight
economic:reward, web3:tokenomicsTabs: orchestratorsContext: Stake weight is the primary factor in active set membership for video transcoding. Higher total bonded LPT means a higher rank and greater share of inflationary rewards.Status: currentPages: orchestrators/staking, orchestrators/protocolStake-for-Access
Stake-for-Access
livepeer:protocol, web3:tokenomicsTabs: resourcesContext: In Livepeer’s stake-for-access design, orchestrators must bond LPT to receive jobs, and the amount staked influences their selection probability. This aligns the interests of compute providers with long-term token value.Also known as: SFAStatus: currentPages: resources/glossary, resources/protocolStake-Weighted
Stake-Weighted
livepeer:governanceTabs: about, lptContext: Used in Livepeer governance votes, orchestrator selection, and reward distribution — delegators with more staked LPT have proportionally greater influence.Status: currentPages: about/governance, lpt/governanceStake-Weighted Voting
Stake-Weighted Voting
livepeer:protocol, web3:governanceTabs: about, community, lptContext: Stake-weighted voting in Livepeer means both orchestrators and delegators can vote on governance proposals, with voting power determined by bonded LPT; delegators can override their orchestrator’s vote with their own stake via vote detachment.Status: currentPages: about/governance, community/governance, lpt/governanceStaking
Staking
economic:reward, web3:tokenomicsTabs: home, community, lpt, resourcesExternal: Proof of stake (Ethereum.org)Status: currentPages: home/staking, lpt/staking, resources/glossaryStream
Stream
video:studioTabs: solutionsContext: A Stream is a persistent Studio resource that persists across broadcast sessions; each time a broadcaster connects using the stream key a new Session is created under it, keeping channel configuration stable between live events.Status: currentPages: solutions/livestreaming, solutions/apiStream Key
Stream Key
video:studioTabs: solutionsContext: Stream Keys are generated per Stream object in Livepeer Studio; they should be kept private and rotated if compromised, as anyone holding the key can broadcast to that stream channel.Status: currentPages: solutions/livestreaming, solutions/apiStreamDiffusion
StreamDiffusion
ai:modelTabs: solutions, developers, orchestratorsExternal: StreamDiffusion (GitHub)Status: currentPages: solutions/ai, developers/pipelines, orchestrators/pipelinesStreamflow
Streamflow
livepeer:upgradeTabs: homeContext: Streamflow was a major protocol upgrade that separated the orchestrator and transcoder roles, introduced probabilistic micropayments, and enabled scalable live streaming on the Livepeer mainnet.Status: currentPages: home/upgrades, home/indexStreaming
Streaming
video:playbackTabs: home, resourcesExternal: Streaming media (Wikipedia)Status: currentPages: home/streaming, resources/glossaryStreamplace
Streamplace
livepeer:productTabs: solutions, developers, communityContext: Streamplace is a Livepeer ecosystem project (SPE) that uses Livepeer’s transcoding and delivery infrastructure to power video for decentralized social applications built on the AT Protocol (Bluesky) stack.Status: currentPages: solutions/use-cases, developers/use-casesStyle Transfer
Style Transfer
ai:applicationTabs: homeExternal: Neural style transfer (Wikipedia)Status: currentPages: home/ai-video, home/pipelinesSub-second Latency
Sub-second Latency
video:playbackTabs: developersExternal: Cloudflare — WebRTC WHIP/WHEPStatus: currentPages: developers/streaming, developers/webrtcSubgraph
Subgraph
web3:conceptTabs: orchestratorsExternal: Subgraphs (The Graph)Status: currentPages: orchestrators/protocol, orchestrators/dataSupply
Supply
web3:tokenomicsTabs: lptContext: Total supply growth is governed by the per-round inflation rate; because inflation is distributed only to active stakers, non-stakers experience dilution as supply increases.Status: currentPages: lpt/economics, lpt/tokenomicsSurge strategy
Surge strategy
economic:treasuryTabs: communityContext: The Surge strategy is a treasury spending philosophy introduced by the Transformation SPE, directing resources toward high-leverage opportunities (e.g. AI video growth) rather than steady-state maintenance funding.Status: currentPages: community/governance, community/treasurySVD (Stable Video Diffusion)
SVD (Stable Video Diffusion)
ai:modelTabs: developersExternal: Stable Video Diffusion (Hugging Face)Status: currentPages: developers/pipelines, developers/ai-gatewaySynthetic Data
Synthetic Data
ai:applicationTabs: homeExternal: Synthetic data (Wikipedia)Status: currentPages: home/ai-video, home/use-casesT
TAM (Total Addressable Market)
TAM (Total Addressable Market)
economic:business, web3:tokenomicsTabs: resourcesExternal: Total addressable market (Wikipedia)Also known as: Total Addressable MarketStatus: currentPages: resources/glossary, resources/economicsTarget Bonding Rate
Target Bonding Rate
web3:tokenomicsTabs: lptContext: The Target Bonding Rate is the equilibrium point of Livepeer’s inflation model — if bonding rate is below 50%, inflation rises to incentivize more staking; if above, inflation falls.Status: currentPages: lpt/economics, lpt/inflationTenderize
Tenderize
livepeer:tool, web3:tokenomicsTabs: communityContext: Tenderize integrates with Livepeer’s bonding system to let LPT holders stake without the 7-round unbonding lockup, issuing liquid derivative tokens representing staked positions.Status: currentPages: community/tools, community/stakingTensorRT
TensorRT
ai:framework, technical:infraTabs: developers, resourcesExternal: NVIDIA TensorRTStatus: currentPages: developers/pipelines, resources/glossaryText-to-Image
Text-to-Image
ai:pipelineTabs: developers, orchestratorsExternal: Text-to-image model (Wikipedia)Status: currentPages: developers/pipelines, orchestrators/pipelinesText-to-Speech
Text-to-Speech
ai:pipelineTabs: developers, orchestratorsExternal: Speech synthesis (Wikipedia)Status: currentPages: developers/pipelines, orchestrators/pipelinesThawing Period
Thawing Period
livepeer:protocolTabs: lptContext: The thawing period is a security mechanism that prevents delegators from immediately withdrawing stake after misbehavior, giving the protocol time to apply any pending slashing.Status: currentPages: lpt/staking, lpt/delegationThumbnail
Thumbnail
video:playbackTabs: solutionsExternal: Thumbnail (Wikipedia)Status: currentPages: solutions/vod, solutions/playbackTicket Broker
Ticket Broker
livepeer:contract, economic:paymentTabs: about, gateways, orchestratorsContext: Gateways fund it via deposit and reserve; orchestrators redeem winning tickets through it. The TicketBroker is the payment settlement layer every on-chain gateway interacts with.Also known as: TicketBrokerStatus: currentPages: about/payments, gateways/payments, orchestrators/paymentsThroughput
Throughput
operational:monitoringTabs: orchestratorsExternal: Throughput (Wikipedia)Status: currentPages: orchestrators/performance, orchestrators/benchmarksTimelock
Timelock
web3:governanceTabs: community, lptContext: The Timelock in LivepeerGovernor gives the community time to review approved changes before they take effect, providing a safety window to react to malicious or erroneous proposals.Status: currentPages: community/governance, lpt/contractsTitan Node
Titan Node
livepeer:toolTabs: orchestratorsContext: Titan Node operates as both a community resource and a hardware supply partner. Their pre-configured nodes are designed to lower the barrier to entry for new orchestrator operators.Status: currentPages: orchestrators/setup, orchestrators/hardwareToken Distribution
Token Distribution
web3:tokenomicsTabs: lptContext: Livepeer’s initial token distribution used a combination of team/investor allocations with vesting and the open Merkle Mine; ongoing distribution occurs through per-round inflation to active stakers.Status: draftPages: lpt/tokenomics, lpt/historyTokenomics
Tokenomics
web3:tokenomicsTabs: community, lpt, resourcesExternal: Cryptoeconomics (Wikipedia)Also known as: Token EconomicsStatus: currentPages: lpt/tokenomics, resources/glossaryTranscode Fail Rate
Transcode Fail Rate
operational:monitoringTabs: orchestratorsContext: A high transcode fail rate lowers an orchestrator’s performance score and reduces the probability of being selected for future jobs. Causes include GPU errors, timeout, software bugs, and capacity overload.Status: currentPages: orchestrators/performance, orchestrators/monitoringTranscoding
Transcoding
video:processingTabs: home, about, solutions, developers, gateways, orchestrators, lpt, community, resourcesExternal: Transcoding (Wikipedia)Status: currentPages: home/network, about/transcoding, resources/glossaryTransformer
Transformer
ai:conceptTabs: resourcesExternal: Transformer (machine learning) (Wikipedia)Status: currentPages: resources/glossary, resources/aiTransformation SPE
Transformation SPE
livepeer:entityTabs: communityContext: The Transformation SPE was established to operationalize the Surge strategy; it introduced Workstreams and Advisory Boards as new governance execution structures for the Livepeer ecosystem.Status: currentPages: community/governance, community/treasuryTreasury
Treasury
economic:treasuryTabs: home, about, developers, orchestrators, lpt, community, resourcesContext: The Livepeer on-chain treasury is funded by a percentage of per-round inflationary LPT (Treasury Reward Cut Rate); allocations are approved via the LivepeerGovernor contract using stake-weighted voting.Status: currentPages: lpt/treasury, community/treasury, resources/glossaryTreasury Allocation
Treasury Allocation
economic:treasuryTabs: lptContext: Treasury allocations are enacted via on-chain proposals that pass through the LivepeerGovernor voting process and execute after the Timelock delay; they typically fund SPEs in milestone tranches.Status: currentPages: lpt/treasury, lpt/governanceTreasury Forum
Treasury Forum
operational:communityTabs: communityContext: The Treasury Forum is the designated category on the Livepeer Forum where SPE pre-proposals, grant requests, RFPs, and budget discussions are posted for community feedback before on-chain votes.Status: currentPages: community/treasury, community/toolsTreasury Governance
Treasury Governance
economic:treasury, web3:governanceTabs: lptContext: Treasury governance uses the LivepeerGovernor contract; proposals require a Proposer Bond, pass through a voting period, meet Quorum, and execute after a Timelock delay.Status: draftPages: lpt/treasury, lpt/governanceTreasury Reward Cut Rate
Treasury Reward Cut Rate
economic:treasuryTabs: community, lptContext: The treasury reward cut rate is set via governance; it determines what share of each round’s LPT emissions flows into the on-chain treasury rather than being distributed to active participants.Status: currentPages: community/treasury, lpt/treasuryTreasury Talk
Treasury Talk
operational:communityTabs: communityContext: Treasury Talk is a regular governance call where active SPEs present progress updates, new funding proposals are introduced, and community members ask questions about treasury spending.Status: currentPages: community/events, community/governanceTributary
Tributary
livepeer:upgradeTabs: homeContext: Tributary represents the second named milestone in Livepeer’s phased roadmap, following Snowmelt’s testnet stage; it culminated in the launch of the Livepeer mainnet with core transcoding and staking functionality.Status: currentPages: home/upgradesTrickle Streaming Protocol
Trickle Streaming Protocol
livepeer:sdkTabs: developersContext: The Trickle Streaming Protocol is the Livepeer-native transport layer underpinning PyTrickle and the live-video-to-video pipeline, enabling sub-segment-level media delivery for real-time AI transforms.Status: currentPages: developers/streaming, developers/architectureTrustless
Trustless
web3:conceptTabs: homeExternal: Web3 — trustless (Ethereum.org)Status: currentPages: home/network, home/indexTTFF (Time to First Frame)
TTFF (Time to First Frame)
video:playbackTabs: solutionsExternal: Time to first frame (SVTA Wiki)Status: currentPages: solutions/analytics, solutions/playbackTUS Upload
TUS Upload
technical:securityTabs: solutionsExternal: TUS protocolStatus: currentPages: solutions/vod, solutions/apiU
Unbonding
Unbonding
web3:tokenomicsTabs: about, lptExternal: Livepeer unbonding introductionContext: Unbonding does not immediately return LPT to the wallet; tokens remain locked for approximately 7 rounds (the thawing period), during which they can still be rebonded but earn no new rewards.Also known as: Unbonding periodStatus: currentPages: about/staking, lpt/delegationUnbonding period
Unbonding period
web3:tokenomicsTabs: communityContext: The unbonding period in Livepeer is 7 protocol rounds; during this time, LPT cannot be transferred or re-staked, serving as a security and commitment mechanism. See also: Unbonding, Thawing Period.Status: currentPages: community/stakingUpscaling
Upscaling
ai:pipelineTabs: home, orchestratorsExternal: Image scaling (Wikipedia)Also known as: UpscaleStatus: currentPages: home/ai-video, orchestrators/pipelinesUSD (United States Dollar)
USD (United States Dollar)
economic:currencyTabs: lpt, community, aboutExternal: United States dollar (Wikipedia)Status: currentPages: lpt/economics, community/treasury, about/economicsUSD Pricing
USD Pricing
economic:pricingTabs: gateways, orchestratorsContext: USD pricing shields gateway and orchestrator operators from ETH price volatility. The gateway or an external price feed integration queries an ETH/USD oracle and adjusts the wei-denominated MaxPrice accordingly.Status: currentPages: gateways/pricing, orchestrators/pricingUSDT (Tether)
USDT (Tether)
web3:tokenTabs: lptAlso known as: TetherExternal: TetherStatus: currentPages: lpt/buying-lptV
veLPT (Voting Escrow LPT)
veLPT (Voting Escrow LPT)
web3:governance, economic:treasuryTabs: community, lptContext: veLPT is a governance proposal (not yet implemented) inspired by Curve Finance’s veToken model; it would give long-term committed holders outsized influence relative to short-term holders. As of 2026 it remains a proposal.Also known as: Vote-Escrowed LPTStatus: draftPages: community/governance, lpt/proposalsVerification Mechanisms
Verification Mechanisms
livepeer:protocolTabs: aboutContext: Verification mechanisms are how Livepeer enforces work quality without requiring every segment to be re-verified; the protocol uses a combination of cryptographic challenges and economic slashing to deter misbehavior.Status: currentPages: about/protocol, about/transcodingVerifier
Verifier
livepeer:protocolTabs: resourcesContext: The Verifier role is part of Livepeer’s fault-proof system: it samples orchestrator outputs and triggers slashing conditions if misbehavior is detected. In the current network, verification uses deterministic checks and spot sampling rather than the originally planned Truebit mechanism.Status: currentPages: resources/glossary, resources/protocolVesting
Vesting
web3:tokenomics, economic:rewardTabs: lptExternal: Vesting (Wikipedia)Status: currentPages: lpt/tokenomics, lpt/historyViewership
Viewership
video:studioTabs: solutionsContext: Livepeer Studio provides a Viewership API returning per-asset or per-stream engagement metrics; data is collected from the Livepeer Player or via the reportPlayback API endpoint in custom players.Status: currentPages: solutions/analytics, solutions/apiVideo on Demand (VOD)
Video on Demand (VOD)
video:deliveryTabs: developers, solutionsAlso known as: VOD, on-demand videoExternal: Video on demand (Wikipedia)Status: currentPages: solutions/vod, developers/video-on-demandVOD (Video on Demand)
VOD (Video on Demand)
video:playbackTabs: home, solutionsExternal: Video on demand (Wikipedia)Status: currentPages: home/streaming, solutions/vodVote detachment
Vote detachment
web3:governance, operational:governanceTabs: community, lptContext: Livepeer’s governance design allows delegators to vote independently from the orchestrator they bonded to; if a delegator casts their own vote, it detaches their stake-weight from the orchestrator’s vote. The orchestrator’s vote applies only to stake whose delegators have not individually voted.Status: currentPages: community/governance, lpt/governanceVoting delay
Voting delay
operational:governanceTabs: communityContext: The voting delay in Livepeer governance gives stakeholders time to review a new proposal before voting opens, preventing snap votes on proposals the community has not had time to analyze.Status: currentPages: community/governanceVoting period
Voting period
operational:governanceTabs: communityContext: The Livepeer voting period lasts 10 protocol rounds; votes cast via LivepeerGovernor are weighted by bonded stake, and delegators may override their orchestrator’s vote during this window.Status: currentPages: community/governanceVoting Power
Voting Power
livepeer:protocol, web3:governanceTabs: community, lptContext: Voting power in Livepeer is stake-weighted, not one-token-one-vote; delegators can override their orchestrator’s vote with their own stake-proportional vote via vote detachment.Status: currentPages: community/governance, lpt/governanceVRAM (Video RAM)
VRAM (Video RAM)
technical:infraTabs: developers, orchestratorsExternal: Video random-access memory (Wikipedia)Status: currentPages: developers/compute, orchestrators/aiW
Warm Model
Warm Model
ai:concept, livepeer:configTabs: about, developers, gateways, orchestrators, resourcesContext: In Livepeer’s AI network, orchestrators can pre-load (“warm”) models in GPU VRAM to guarantee fast response times; warm models are declared in the aiModels.json config and prioritized for latency-sensitive pipelines. During the current beta, orchestrators typically support one warm model per GPU.Status: currentPages: orchestrators/ai, resources/glossaryWater Cooler
Water Cooler
operational:communityTabs: communityContext: The Water Cooler is a recurring Livepeer community call with a lighter format than Treasury Talk or Dev Call; it covers ecosystem news, informal Q&A, and community social discussion.Status: currentPages: community/events, community/socialWebhook
Webhook
technical:devTabs: solutions, developers, gateways, orchestratorsExternal: Webhook (Wikipedia)Status: currentPages: solutions/webhooks, developers/events, orchestrators/discoveryWebhook Discovery
Webhook Discovery
livepeer:protocol, technical:devTabs: orchestratorsContext: Provides a flexible, off-chain channel for capability advertisement. Gateways can call a registered webhook endpoint to retrieve the orchestrator’s current capability set, enabling real-time updates without on-chain transactions.Status: currentPages: orchestrators/discovery, orchestrators/configWebRTC (Web Real-Time Communication)
WebRTC (Web Real-Time Communication)
video:protocol, technical:protocolTabs: solutions, developers, resourcesExternal: WebRTC (Wikipedia)Status: currentPages: solutions/webrtc, developers/webrtc, resources/glossaryWebVTT (Web Video Text Tracks)
WebVTT (Web Video Text Tracks)
video:playbackTabs: solutionsExternal: WebVTT (Wikipedia)Status: currentPages: solutions/vod, solutions/subtitlesWei
Wei
web3:tokenTabs: gateways, orchestrators, lptExternal: Ether denominations (ethereum.org)Status: currentPages: gateways/pricing, orchestrators/pricingWeight Factors
Weight Factors
livepeer:configTabs: gatewaysContext: Weight factors (e.g., selectRandWeight, selectStakeWeight, selectPriceWeight) let gateway operators tune the trade-off between cost, decentralization, and performance in orchestrator selection. Adjusting these requires understanding their interaction with the scoring algorithm.Status: currentPages: gateways/routing, gateways/discoveryWHEP (WebRTC-HTTP Egress Protocol)
WHEP (WebRTC-HTTP Egress Protocol)
video:protocolTabs: solutions, resourcesExternal: WHEP draft (IETF)Also known as: WebRTC-HTTP Egress ProtocolStatus: currentPages: solutions/webrtc, resources/glossaryWHIP (WebRTC-HTTP Ingestion Protocol)
WHIP (WebRTC-HTTP Ingestion Protocol)
video:protocolTabs: solutionsExternal: WHIP (RFC 9725)Status: currentPages: solutions/webrtc, solutions/ingestWhisper
Whisper
ai:modelTabs: developers, orchestratorsExternal: Whisper (Hugging Face)Status: currentPages: developers/pipelines, orchestrators/pipelinesWin Probability
Win Probability
economic:paymentTabs: orchestratorsContext: Win probability is a parameter negotiated between gateway and orchestrator. Lower win probability reduces on-chain redemption frequency (and gas costs) at the expense of larger, less frequent payouts.Status: currentPages: orchestrators/payments, orchestrators/protocolWinning Ticket
Winning Ticket
economic:paymentTabs: about, orchestratorsContext: In Livepeer’s payment system, most tickets are non-winning; only the fraction that statistically win are submitted to the TicketBroker for on-chain redemption, keeping gas costs low while maintaining correct expected payment values.Status: currentPages: about/payments, orchestrators/paymentsWorker
Worker
livepeer:roleTabs: resourcesContext: Workers are the compute leaf nodes in a Livepeer orchestrator pool. An orchestrator can coordinate many workers to scale capacity horizontally; each worker connects via the orchSecret and processes jobs assigned by the orchestrator.Status: currentPages: resources/glossary, resources/protocolWorkload
Workload
operational:processTabs: orchestratorsContext: Workload determines whether an orchestrator is at capacity. The -maxSessions flag caps the maximum concurrent workload. Monitoring workload against capacity helps operators tune pricing and hardware scaling decisions.Status: currentPages: orchestrators/performance, orchestrators/operationsWorkstreams
Workstreams
livepeer:entity, operational:governance, operational:communityTabs: communityContext: Workstreams are the primary execution structure within Livepeer’s post-SPE governance model; each workstream has a defined domain, accountable lead, and milestone timeline funded through the treasury.Status: currentPages: community/governance, community/treasuryWorld Model
World Model
ai:applicationTabs: home, solutions, developers, community, resourcesExternal: Generative artificial intelligence (Wikipedia)Status: currentPages: home/ai-video, solutions/ai, resources/glossaryY
Yield
Yield
economic:rewardTabs: lptContext: Yield for delegators varies by orchestrator commission rates, the current inflation rate, and the total bonded supply; the Livepeer documentation provides yield calculators for delegators.Status: currentPages: lpt/staking, lpt/economicsZ
Zero-to-Hero
Zero-to-Hero
livepeer:product, operational:processTabs: developersContext: Zero-to-Hero is Livepeer’s flagship onboarding tutorial series for new developers, providing step-by-step guides covering SDK setup, stream creation, AI pipeline integration, and protocol fundamentals.Status: currentPages: developers/guides, developers/quickstart