Livepeer

Livepeer staking diagnostics trace rewards back to delegation records

Livepeer staking links an LPT holder's bonded position to one orchestrator, so a reward mismatch is best diagnosed from the delegation record, the operator's active status, its reward-call history, and the commission terms applied for the relevant round. Lower-than-expected earnings may reflect a stale interface, an unconfirmed transaction, a missed reward call, a changed reward cut, or simply an absence of service fees. Start with the wallet and transaction, then compare round-specific state instead of relying on an annualized rate. Wait when a transaction remains pending or confirmed contract state matches. Correct a failed transaction before submitting another.

Last updated:

A stale display and an incomplete delegation leave different evidence

A stale interface can show an old balance after a successful transaction, while an incomplete delegation leaves no confirmed state change. Those symptoms look similar on one screen, but their records differ. A successful receipt for the intended bond call, sent by the connected address to the protocol contract on Arbitrum One, means the delegation transaction executed. A pending, dropped, or reverted transaction means the intended bond has not completed.

The transaction hash is the first dividing line. Looking it up reveals the sending account, destination contract, status, block, and submitted call without exposing a seed phrase or private key.

After success, compare the same wallet's delegate address, bonded amount, and start round. An indexing delay may leave the Explorer behind the chain for a while. Refreshing the same account or waiting for its indexer is reasonable when the confirmed transaction and contract state agree.

Without a successful transaction, reward diagnostics are premature. A wallet can display an approval, signature request, or pending submission even though no delegation state was recorded. Don't submit duplicates while one transaction remains pending; first determine whether it reaches a terminal status.

Delegation status sets the first reward boundary

A bonded position points to one orchestrator, and that attribution determines which pool can allocate LPT rewards and ETH fees to the delegator. The orchestrator can't spend the delegator's LPT. The protocol's Minter contract holds the bonded LPT, while the account owner authorizes later claims, redelegation, unbonding, and withdrawal.

Eligibility also depends on the selected orchestrator being active. Stake bonded to an inactive operator remains bonded, yet it doesn't earn round rewards until that operator becomes active again or the stake moves. Read the position's delegate and start round beside the operator's status. A wallet balance alone can't show whether the position belonged to an eligible pool in the round under review.

Reward cut changes the LPT split

The reward cut is the percentage of an orchestrator pool's newly minted LPT the operator keeps. Delegators divide the remainder according to their stake in that pool. Lower reward cut therefore leaves a larger pool for delegators, but it doesn't establish the pool's total issuance or prove a reward call occurred.

Round-level diagnosis needs the cut applied in the affected round, not only the value displayed now. Commission settings can change, and a current profile may not explain an older balance movement. Compare like with like: the pool reward, the historical reward cut, and the delegator's share of pool stake for the same round. That relationship explains LPT allocation without turning a changing protocol rate into a permanent yield promise.

Fee share only divides fees the operator earned

Fee share runs in the opposite direction from reward cut. It is the percentage of an orchestrator's ETH service fees passed to delegators, so a higher fee share sends more of an existing fee pool to them. Some summaries call this a fee cut, so confirm whether the displayed number means the delegator share or the operator's retained share.

Fee share only divides fees the operator earned: Fee share runs in the opposite direction from reward cut. It is the percentage of an orchestrator's ETH service fees passed to delegators, so a higher fee share sends more of an existing fee pool to them.; Some summaries call this a fee cut, so confirm whether the displayed number means the delegator share or the operator's retained share.
Fee share only divides fees the operator earned.

View full-size image

A generous fee share can still produce no ETH for a period. Service fees originate from compute work and probabilistic payment tickets, so the amount depends on work volume, pricing, successful service, and ticket redemption. Delegation doesn't manufacture a fee pool. Diagnose a missing fee by checking whether the operator recorded fees for the relevant round before examining how those fees were divided.

Reward-call history explains an abrupt LPT gap

An active orchestrator must call reward during a round for its pool to receive that round's newly minted LPT. If the call is absent, claiming later won't recreate the forfeited allocation.

Compare the last reward round with the round whose earnings appear missing. A continuous history points away from an operator-side call failure and back toward eligibility, commission, stake share, or display timing. A gap aligned with the missing earnings is stronger evidence than a current percentage. The cause of the missed call may be downtime, automation failure, or insufficient gas, but a delegator usually needs the on-chain outcome to make the next decision.

Total stake changes each delegator's proportion

A delegator's LPT reward isn't determined by the personal bonded amount in isolation. The operator's pool first receives an allocation related to its share of active bonded stake, then the delegator receives a share of the delegator portion. More outside stake can increase the operator's network share while reducing one delegator's percentage of that pool.

This interaction can make a displayed annualized estimate move even when the wallet, operator, and commission settings stay unchanged. Treat that estimate as a projection built from live inputs, not an account statement. For an affected round, compare the wallet's stake with the pool's total stake, then keep the reward cut and successful reward call in the same calculation. No single input explains every change.

Performance matters differently for LPT and ETH

Operational performance reaches the two earning streams through different paths. Reliable reward calls determine whether an active pool receives round issuance. Service availability, accepted pricing, completed work, and redeemed winning tickets affect whether a fee pool exists. A large delegated stake may support active-set status, but it doesn't prove the operator completed compute work or earned ETH fees.

A pool may receive LPT while recording little or no service-fee activity. An attractive commission setting also can't repair repeated missed calls. Review performance for the earning stream being diagnosed instead of treating one broad operator score as a guaranteed return.

A mismatched display with a hypothetical 137 LPT

Assume a hypothetical starting balance of 137 LPT, a hypothetical selected orchestrator, a hypothetical ETH balance for gas, and hypothetical network conditions. The expected state is a recorded 137 LPT bond attributed to that operator, with a start round showing when its bonded status begins. The visible symptom is different: the wallet submission appeared complete, but the account view still shows the LPT as available and no delegate.

The recovery boundary comes before another transaction. Record the non-sensitive transaction hash, connected wallet address, chain, and intended delegate, then inspect the receipt. If it succeeded, compare the contract's bonded amount and delegate with the account view. A confirmed 137 LPT bond, matching delegate, and recorded start round establish the concrete result; the stale view can be allowed time to update.

In the edge case, a reverted or dropped transaction leaves the starting balance unbonded, so there is no staking reward to diagnose yet. Identify the failed prerequisite, such as insufficient gas or a rejected wallet confirmation, correct it, and submit once. Stop while the replacement remains pending. Escalate only if a successful receipt and a fresh contract read disagree, preserving the hash, block, address, and observed fields.

Claiming separates accrual from checkpointing

Pending earnings can update as the orchestrator earns them; a delegator doesn't need to claim every round for accrual to exist. Claiming checkpoints pending LPT rewards into the stored bonded amount and pending ETH fees into the fee balance. Unclaimed LPT rewards already count in later reward calculations, so manual claims aren't required for compounding.

Claiming separates accrual from checkpointing: A claim doesn't call reward on behalf of the orchestrator, restore a missed round, or create service fees. Separate the orchestrator's reward call from the delegator action that claims earnings when reading history; a claim can be standalone or run automatically during another protocol action. If pending earnings appear but the bonded balance has not changed, the difference may be an unclaimed checkpoint rather than missing income. The relevant fields are pending stake, pending fees, bonded amount, and last claim round.

View full-size image

A claim doesn't call reward on behalf of the orchestrator, restore a missed round, or create service fees. Separate the orchestrator's reward call from the delegator action that claims earnings when reading history; a claim can be standalone or run automatically during another protocol action. If pending earnings appear but the bonded balance has not changed, the difference may be an unclaimed checkpoint rather than missing income. The relevant fields are pending stake, pending fees, bonded amount, and last claim round.

Unbonding records explain delayed liquidity

Unbonding moves part or all of a bonded position into a lock instead of returning LPT immediately. Each lock records an amount and a withdrawal round. The unbonding period is a configurable protocol parameter, so check its current value in rounds and the lock's withdrawal round instead of relying on an old day estimate.

Before the withdrawal round, a missing wallet balance is expected because the tokens remain in the unbonding state. After that boundary, withdrawal is a separate action. Partial unbonding leaves the remainder bonded, while rebonding can cancel an unfinished exit and return the locked amount to bonded status. These states explain liquidity timing, but they don't retroactively change rewards already attributed to earlier eligible rounds.

Unbonding records explain delayed liquidity: Unbonding moves part or all of a bonded position into a lock instead of returning LPT immediately. Each lock records an amount and a withdrawal round.; The unbonding period is a configurable protocol parameter, so check its current value in rounds and the lock's withdrawal round instead of relying on an old day estimate.
Illustration: Unbonding records explain delayed liquidity.

View full-size image

The final check keeps every value on the same round

A reliable diagnosis finishes by aligning identity, state, and time. Screenshots of a headline yield are weak evidence because they omit the wallet, round, commission history, and underlying transactions. Preserve non-sensitive identifiers and compare records from one round before deciding the protocol underpaid or the interface is wrong.

  • Confirm the connected wallet and Arbitrum One, then match the transaction sender.
  • Record the delegation transaction status, block, delegate address, bonded amount, and start round.
  • Check whether the orchestrator was active in the affected round.
  • Compare that round's reward call, reward cut, fee share, and total pool stake.
  • Separate LPT issuance from ETH fees and confirm whether a fee pool existed.
  • Reconcile pending stake, pending fees, bonded balance, and last claim round.

If those records agree, a local display delay is the likely remaining explanation and another transaction isn't warranted. If a confirmed contract read conflicts with the indexed account record beyond a reasonable update window, stop changing the position and retain the transaction hash, block, wallet address, delegate, and mismatched fields for escalation.

Livepeer staking - common questions

Can one wallet divide delegated LPT among several orchestrators?

One account address's bonded position can point to only one orchestrator at a time. Splitting LPT across several operators requires separate account addresses, each with its own delegation record and ETH for gas; one wallet application may manage those addresses. A later redelegation changes the single operator attached to that address's bonded position.

Is there a protocol-enforced minimum delegation amount?

An initial delegation must be greater than zero, but the contract sets no higher minimum. The practical lower boundary comes from whether an amount justifies transaction gas and ongoing attention, not an eligibility floor. A small position follows the same bonding, reward, claim, and unbonding mechanics as a larger one.

How much ETH should remain available for delegation maintenance?

Keep enough ETH on Arbitrum One for the transactions you may actually make, including delegation, claiming, redelegation, unbonding, and withdrawal. Gas prices and action frequency change, so a fixed dollar figure would age badly. The relevant failure signal is an estimate or transaction failing for insufficient gas.

When is the safest point in a round to claim earnings?

Manual claims aren't needed just to compound LPT rewards. If the selected orchestrator is active and a claim is necessary, don't submit it before the orchestrator has called reward for the current round. An earlier claim can advance the account's last claim round before the reward record exists and skip that round's LPT earnings. Because fee updates can occur separately, the reward call is a minimum boundary rather than proof all round activity is complete.

Does redelegation require waiting through the full unbonding period?

No. Redelegation can move a bonded position to another orchestrator without waiting through the full unbonding period. Timing still matters: moving before the current operator calls reward for the round can skip that round. Check the call first, then confirm the new delegate after the transaction succeeds.