Livepeer (LPT) Price

LPT is the protocol token of the Livepeer network. It coordinates computational-service providers, applications using the network, and holders participating in network security. It is not equity in the Livepeer company; in the protocol, LPT staking is both the basis on which orchestrators qualify to provide services and a way for holders to participate in the network through delegation. Livepeer routes work such as video transcoding and AI inference to orchestrators running GPUs. Orchestrators need to hold LPT themselves or receive delegated LPT in order to potentially enter the active set and take on work; therefore, LPT's protocol role is connected to network services, staking, and participant incentives, rather than ownership of a particular company's profits or assets.

LPT's core role is to provide the staking basis for orchestrators to enter the active set. Orchestrators run GPUs and protocol software and provide computational services; the LPT they own plus LPT delegated to them make up their stake. Only after reaching the competitively determined staking level required for the active set can an orchestrator qualify to take on network work. Delegators delegate LPT to orchestrators; they do not run the orchestrator's hardware in its place. Delegation turns a holder's choice of a reliable service provider into a staking signal; the network uses that signal to coordinate service supply and network security, and orchestrators and their delegators may share participation-related fees and protocol rewards according to the rules.

Yes. Holders can delegate LPT to an orchestrator to support that orchestrator's stake without running a GPU node themselves. Once delegated, the tokens are used in that protocol participation relationship; they are not in the same state as an undelegated balance in a wallet that can be freely used immediately. Delegation returns are not a fixed interest rate. Service fees depend on work actually taken on by the orchestrator and on its fee-sharing settings, while LPT rewards also depend on protocol rules and relative staking participation; the orchestrator's operating performance, fee settings, network usage, and the staking scale of other participants all affect outcomes. Before changing delegation targets or exiting, the then-applicable on-chain unbonding and operational conditions should also be confirmed.

LPT supply is not determined only by buying and selling: the protocol mints new LPT over time and distributes the corresponding rewards to orchestrators and delegators participating in staking relationships. New tokens are one source of protocol rewards, so total supply increases through this minting mechanism. For holders, the key issue is not only whether total supply increases, but also whether they participate in a staking relationship that meets the rules. Protocol rewards are distributed according to participants' relative stake; non-participants do not receive the newly issued rewards from the same round, and their relative share of total supply may be diluted by new tokens received by participants. This mechanism does not mean any specific address is guaranteed to receive rewards.

If LPT was delegated to an orchestrator on Ethereum mainnet before February 14, 2022, that historical delegated position is subject to the official migration process. Migration is not arbitrarily bridging newly purchased LPT; it means using the wallet that made the original delegation to claim the corresponding delegated stake, earned rewards, and fees on Arbitrum. After claiming is completed, the related protocol operations should be carried out on Arbitrum. Official guidance states that Ethereum-mainnet withdrawals were disabled from that date, while inflationary rewards and ETH fees are distributed on Arbitrum; therefore, historical delegators who have not completed migration may be unable to continue claiming related entitlements or withdraw that historical position. Before submitting the claim transaction, the original wallet must also have ETH on Arbitrum to pay Gas.

Protocol fees and inflationary rewards are two different value flows. Protocol fees are consideration paid by developers or applications for actual computational work such as video transcoding and AI inference; after providing services, orchestrators receive fees and share them with delegators according to their settings and the rules. Fees exist only when the network is actually used on a paid basis. Inflationary rewards, by contrast, come from newly minted LPT rather than payment for a particular service. They are distributed to orchestrators and their delegators according to staking relationships to incentivize network security and service supply. Thus, even though both may relate to delegation, fees reflect revenue from actual work and inflationary rewards reflect the protocol's distribution of new tokens; their assets, sources, and determinants of amount differ.

Before delegating LPT, confirm whether the target orchestrator is in the active set and continues to provide services, because only active participation relationships can be connected to network services and related distributions. Its historical service performance, delegation-related fee settings, and delegated stake size should also be reviewed; these indicators help explain its status, but do not guarantee future workload or returns. Two types of risk should also be distinguished: changes in LPT's market price affect asset value, while the orchestrator's operation, fee settings, network demand, and changes to protocol rules affect delegation outcomes. Delegation and later adjustments are on-chain operations, requiring the correct network and sufficient Gas; for historical mainnet delegations, their status should first be confirmed under the migration rules.

Livepeer service costs are jointly affected by the per-unit work price set by orchestrators and on-chain settlement costs. For transcoding pricing, for example, orchestrators can set a base price per pixel; when the on-chain cost of redeeming tickets rises, nodes can increase their public quote in proportion to that cost relative to ticket face value in order to cover higher settlement costs. Therefore, the service cost ultimately seen by users does not depend only on LPT. Work volume, price units, an orchestrator's quoting strategy, and the effect of Gas on settlement can all change the cost; LPT here primarily serves staking and coordination functions, rather than being a fixed quotation unit for each service fee.

Increased network use does not automatically mean an increase in LPT price, but there is an explainable transmission path: greater demand for paid computation may increase service-fee scale and strengthen the economic incentive to run orchestrators and compete for the active set; only if that incentive becomes greater self-staking or delegation demand could it affect the supply and demand of tradable LPT. This path can fail at several points. For example, demand growth may not become sustainable paid work, existing stake may already be sufficient to meet active-set requirements, participants may not increase LPT staking, or newly issued protocol rewards and market selling pressure may offset demand; any of these can cause usage and LPT market performance to diverge.

The difference between operating an orchestrator and simply delegating is that the former actually operates GPUs and node services and competes to enter the active set with owned and delegated LPT; the latter selects and supports an orchestrator but does not undertake node-operation work. Both may participate in reward and fee distribution, but the conditions for receiving them and the responsibilities assumed differ. Orchestrators must also bear the costs of hardware, network connectivity, operations and maintenance, and protocol transactions on Arbitrum. Delegators have a lower operational burden, but their outcomes still depend on whether the selected orchestrator remains active, its actual service performance, and its fee and reward-sharing settings.