Skip to main content

Livepeer

Livepeer (LPT) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Livepeer — a protocol/network for distributed video transcoding, as well as (per separate Tier‑1 documentation) Livepeer AI (Beta): a set of AI pipelines for requesting inference jobs on the network. The staking token LPT is used for security and work distribution.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a decentralized network of nodes for video processing (transcoding) and AI inference via a set of AI pipelines (Livepeer AI, Beta).
  • Who it’s for: applications/platforms that need to encode/process video; node operators (orchestrators) and delegators who stake.
  • Why onchain/token: Ethereum is used for LPT accounting and the staking/slashing/governance rules; LPT is a staking token for security and work distribution (the whitepaper states that payment for work can be made in ETH, and LPT is not a “medium of exchange”).
  • What you can actually touch: the Tier‑1 AI docs describe pipelines/models and publish a showcase of projects with demo surfaces.

How it works (very briefly)

  1. The user does: an application sends a video stream/tasks to the network via gateway nodes.
  2. The system does: the gateway routes the work to orchestrator/transcoder nodes; they perform the transcoding. For Livepeer AI: applications send inference job requests to the selected AI pipeline.
  3. The user gets: processed video/the compute result.
  4. Where the blockchain is: smart contracts on Ethereum for bonding/delegation, reward issuance, penalties and governance processes.
  5. Token role: LPT is staked/delegated to transcoders; the protocol distributes work and (algorithmically) issues new LPT; slashing is possible in case of violations.

Quick links: AI thesis fit

Project passport

Field Value
Project name Livepeer
Also known as (aliases) LPT, Livepeer Protocol
Logo (logo) ../assets/livepeer_logo.svg
Token symbol (ticker) LPT
Category AI/Compute | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x58b6a8a3302369daec383334672404ee733ab239
Token model (token_type) utility (staking + governance)
Max supply — (inflationary; algorithmic issuance, no fixed cap in the whitepaper)
Issuance inflationary
Tokenomics (tokenomics, brief) staking token; algorithmic issuance; reward distribution via onchain rules
Governance DAO (stake‑based governance)
Admins/keys —
Audit yes
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) video transcoding + Livepeer AI pipelines
Use‑case (use_case) video processing (transcoding)
DecAI Fit — AI thesis fit 6/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 3 / 2 / 3
Last verified 2026-02-03

General project overview

Livepeer is a protocol whose goal is described as a decentralized network for live video streaming, where participants provide compute for video transcoding. The whitepaper describes the economic model of a “delegated stake‑based protocol”: the LPT token is used for bonding/delegation and security (including slashing), while fees for work are paid in ETH.

Separately, the Tier‑1 documentation highlights the product layer Livepeer AI (Beta): a network of AI orchestrators and a set of generative AI pipelines through which applications can submit AI inference jobs. This is not “Livepeer’s own model”, but an infrastructure/platform for executing inference tasks.

Features/modules

  • Orchestrator / Transcoder nodes: perform transcoding and (as described on the website) AI processing tasks.
  • Delegation / bonding: LPT holders delegate stake to transcoders; active transcoders are selected by the amount of delegated stake.
  • Governance proposals: the voting process and protocol parameters are described in the wiki.

Typical scenarios

  • Scenario 1 (compute consumer): an application submits a video processing task → the gateway routes it to an orchestrator → receives the result.
  • Scenario 2 (node operator): an orchestrator provides GPU/compute → receives fees/rewards; delegators stake LPT and receive a share.
  • Scenario 3 (Livepeer AI builder): an application selects a pipeline → submits an inference job → receives the result (sample “demo surfaces” are listed in the Tier‑1 showcase).

Getting started (wallet/network)

  • What you need: an EVM wallet for LPT; infrastructure‑wise — a Livepeer node/operator stack.
  • Network/chain: Ethereum Mainnet (LPT — ERC‑20).
  • Fees: Ethereum fees for onchain actions (bond/unbond/proposals, etc.).

Architecture/tech (non‑AI)

  • Where logic runs: video processing/compute — offchain on the nodes; onchain — stake accounting, reward issuance/rules, protocol parameters and governance.
  • Participant roles: apps/platforms, gateway nodes, orchestrators/transcoders, delegators.

Token/economics (expanded, no forecasts)

  • LPT is not a “payment currency”: the whitepaper states that broadcasters pay in ETH, while LPT is a staking/coordination token.
  • Issuance: the whitepaper describes an inflationary model (inflationary issuance) with parameters that can change algorithmically.
  • Security: bonding/delegation and slashing are used to discipline participants and protect against attacks.

Governance

The wiki describes governance mechanisms (proposals on parameters, decisions on slashed funds/common pool); voting/weight — by delegated stake.

Security and incidents

  • Audits: a public Trail of Bits report (2019) is listed in links_*.
  • Bug bounty: a public bounty on Immunefi is listed.
  • Security advisories: the security page of the wiki repository is listed.

Project status and timeline

  • Current status: mainnet (token and protocol on Ethereum).
  • Key milestones: the whitepaper is dated as originally published in April 2017 (a note in the document).
  • Roadmap: published in the project blog (links_*).

Ecosystem/integrations

  • Explorer: Livepeer Explorer/statistics are available via public interfaces (including the website/ecosystem pages).
  • Development: go-livepeer releases are published on GitHub.

AI component of the project

  • What is real AI here? The Tier‑1 docs describe the Livepeer AI layer: generative AI pipelines and the execution of inference jobs on the network (Beta). This is not proof of “model quality”, but it is a description of a real AI component (pipelines/models).
  • What is truly onchain? Bonding/delegation, reward issuance and governance processes are enforced via the smart‑contract layer on Ethereum (per the whitepaper).
  • Why is a token needed? LPT is a staking/coordination token that distributes the “right to work” and ensures security via slashing; governance is described in the wiki as stake‑based.
  • Red flags (based on the information found): the absence in Tier‑1 of formal quality metrics/benchmarks for the pipelines; it is necessary to check which models are actually “warm”/available, and where the boundary lies between the onchain protocol (staking/slashing) and offchain AI execution.

DecAI Fit component summary

  • DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity high 3
Token necessity medium 2
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 3.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Livepeer AI describes a network for executing AI inference jobs via a set of generative AI pipelines (beta).
  • Evidence: Tier‑1 — https://docs.livepeer.org/ai/builders/get-started, https://docs.livepeer.org/ai/pipelines/overview
  • Why sufficient / why not (one line): the Tier‑1 docs directly describe AI pipelines and the use of the network for inference jobs (without model quality metrics).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The Tier‑1 documentation publishes a showcase of projects and demo surfaces built on Livepeer AI pipelines.
  • Evidence: Tier‑1 — https://docs.livepeer.org/ai/builders/showcase
  • Why sufficient / why not (one line): the showcase gives concrete examples to “try/compare” the operation of AI pipelines (without formal metrics → AI_3 remains 0).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.livepeer.org/lpt
  • Why sufficient / why not (one line): the source contains no quantitative quality metrics for the AI subsystem.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): The Tier‑1 docs describe the set of AI pipelines, the beta mode, warm models and the model layer based on Diffusers/HuggingFace.
  • Evidence: Tier‑1 — https://docs.livepeer.org/ai/pipelines/overview
  • Why sufficient / why not (one line): this is a technical description of the AI component (pipelines/models), albeit without “quality/benchmarks”.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum Mainnet
  • Addresses/identifiers: LPT ERC‑20: 0x58b6a8a3302369daec383334672404ee733ab239
  • Evidence: Tier‑1 — https://etherscan.io/token/0x58b6a8a3302369daec383334672404ee733ab239
  • Why sufficient / why not (one line): there is a verifiable onchain token contract on Ethereum.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the whitepaper describes the Livepeer Smart Contract for jobs/deposits/claimwork/reward and governance parameters.
  • Evidence: Tier‑1 — https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md?plain=1
  • Why sufficient / why not (one line): the source explicitly identifies the protocol’s smart‑contract layer on Ethereum.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, trustless staking/slashing and the accounting of reward distribution/participation rules, which the whitepaper places in the smart‑contract layer, break down.
  • Evidence: Tier‑1 — https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md?plain=1
  • Why sufficient / why not (one line): the protocol economics and security are formally tied to onchain rules and slashing.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, LPT (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x58b6a8a3302369daec383334672404ee733ab239
  • Why sufficient / why not (one line): Etherscan records the token and its supply.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): the whitepaper states that payment for work (fees) is made in ETH, not in LPT.
  • Evidence: Tier‑1 — https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md?plain=1
  • Why sufficient / why not (one line): in the whitepaper, LPT is described as a staking token, and ETH as the means of payment for broadcasters.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): bonding/delegation and slashing are described as key elements of security and incentives.
  • Evidence: Tier‑1 — https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md?plain=1
  • Why sufficient / why not (one line): the whitepaper directly describes bonding/unbonding and slashing conditions.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): governance mechanisms and voting by bonded nodes are described in the wiki.
  • Evidence: Tier‑1 — https://github.com/livepeer/wiki/wiki/Governance
  • Why sufficient / why not (one line): the document describes proposals and voting inspired by stake‑based governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): a strict conclusion on the replaceability of LPT (without loss of meaning of the DPoS mechanics) is not given in Tier‑1 sources.
  • Evidence: Tier‑1 — https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md?plain=1
  • Why sufficient / why not (one line): the whitepaper describes LPT as the protocol’s specific staking token, but does not perform a “replaceable/irreplaceable” test.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://github.com/livepeer/wiki/blob/master/WHITEPAPER.md?plain=1 the Livepeer protocol, participant roles, staking/bonding, issuance and slashing; LPT as a staking token, fees in ETH
Tier‑1 https://www.livepeer.org/lpt a high‑level description of the roles (gateway/orchestrator/delegators) and the statement about “AI processing jobs”
Tier‑1 https://docs.livepeer.org/ai/builders/get-started Livepeer AI (Beta) as a working network; the entry point for builders, links to SDK/API/pipelines.
Tier‑1 https://docs.livepeer.org/ai/pipelines/overview A description of the AI pipelines and models (Diffusers/HuggingFace), warm models, beta mode.
Tier‑1 https://docs.livepeer.org/ai/builders/showcase Examples/a showcase of applications and demo surfaces built on Livepeer AI pipelines.
Tier‑1 https://etherscan.io/token/0x58b6a8a3302369daec383334672404ee733ab239 onchain confirmation of the LPT ERC‑20 contract and its supply
Tier‑1 https://github.com/livepeer/wiki/wiki/Governance a description of governance proposals and voting by bonded nodes
Tier‑1 https://immunefi.com/bounty/livepeer/ the existence of a bug bounty (Tier‑1 link)

No comments to display

Back to top