Skip to main content
Use the Livepeer Explorer to read the public state of your orchestrator: stake, cuts, reward calls, fee earnings, and service URI. Every number here comes from on-chain data indexed from Arbitrum, so the page is best used to confirm protocol state, compare your settings with peers, and spot drift between what you intended and what the network sees. Your orchestrator profile:
Explorer orchestrator profile URL
https://explorer.livepeer.org/accounts/<your-address>/orchestrating

​
Explorer scope

Before diving into metrics, understanding the Explorer’s scope avoids confusion. What it shows:
  • On-chain state as written to Arbitrum — stake, cuts, reward calls, fee earnings
  • Protocol-level data: your registered service URI, your active/inactive status
  • Your delegators and their individual stake amounts
What it leaves out:
  • Live node health or uptime (use Prometheus for this)
  • Off-chain pool worker contributions (pool workers are invisible to the protocol)
  • AI model warm status or per-pipeline job counts (use tools.livepeer.cloud)
  • Which gateways are currently routing work to you (use the Loki gateway API)

​
Active Set status

The active set is the top 100 orchestrators by total stake at each round boundary. Only active set members receive transcoding work.
What to watch:
  • Your rank among all orchestrators
  • Whether you are currently active or inactive
  • Your trend over the past 30 days
Outside the active set: Your stake (self-stake plus delegated stake) is insufficient to rank in the top 100. The gap between your stake and the 100th-place orchestrator is the amount you need to close. Your options are to increase your self-stake directly, or to attract more delegators.

​
Total stake

This is the sum of your self-stake and all delegated stake. It is the single most important variable for your active set ranking, and for the proportion of video transcoding work routed to you by stake-weighted gateways.
Your self-stake is the LPT you bonded to yourself. Delegated stake comes from LPT holders who chose to delegate to you.Increase your self-stake directly by bonding more LPT. Attracting delegators requires competitive reward cut and fee share settings plus a strong performance track record — see Getting Delegates.
For video transcoding, stake weighting affects selection probability. Higher stake means you are more likely to be selected by stake-weighted gateways. For AI inference, routing is primarily capability-based (does your node support the requested model?) and price-based (is your price within the gateway’s limit?). Stake plays a smaller role in AI job routing.
Pending stake refers to delegations and undelegations that have been submitted but have not yet taken effect. Changes to stake take effect at the next round boundary.

​
Reward cut and fee share

These two parameters are your public service terms, visible to any potential delegator evaluating your orchestrator. What competitive looks like: Check the top 20 active orchestrators on the Explorer and compare your settings. Reward cut of 5–15% and fee share of 0–10% is typical for competitive operators. Very high reward cuts (above 30%) make delegation unattractive; delegators earn less per LPT staked than they would on a lower-cut orchestrator. Changing these parameters requires an on-chain transaction and takes effect at the next round boundary. You can update them via livepeer_cli or directly in the Explorer interface if your wallet is connected.
Changes to reward cut and fee share are publicly visible to delegators and affect their yield. Frequent large changes can reduce delegator confidence. Communicate changes in advance if your delegator base is large.

​
Reward call history

This is the most operationally important metric to monitor regularly. Each round (~22 hours on Arbitrum), your node must call reward() to claim that round’s LPT inflation. The Explorer shows your call history round by round. 
Round 4021 ✓ reward called
Round 4022 ✓ reward called
Round 4023 ✗ missed
Round 4024 ✓ reward called
What a missed round costs: When you miss a round, that round’s LPT inflation that would have been minted to your address is permanently lost. You and your delegators both miss their share. This compounds over time — delegators whose yield is consistently reduced by missed rounds will unbond and move their stake elsewhere. Target: 100% call rate. Diagnosing missed rounds:
-reward=false disables reward calling. In split setups where the orchestrator and transcoder run as separate processes, keep the flag state consistent across every launch command. A common mistake is disabling reward on the orchestrator while a second process still owns the wallet.
Reward calls require ETH on Arbitrum for gas. A dry wallet causes reward calls to fail silently. Check your orchestrator address ETH balance on Arbiscan and keep at least 0.02–0.05 ETH in the wallet as a buffer.
A node offline at the round boundary misses the reward call. The Arbitrum round length is approximately 22 hours. Compare regular maintenance windows against round boundaries before you dismiss the gap as random.
If missed rewards are a recurrent problem, consider the split setup. OrchestratorSiphon runs reward calling on a separate, stable machine independently of your GPU workload machine.

​
Fees earned

Cumulative ETH earned from video transcoding and AI inference fees. This is separate from LPT inflation rewards. How to read it: A low or zero fee balance despite being in the active set usually means one of three things:
  1. Price is too high — your -pricePerUnit exceeds what gateways are willing to pay. Check Livepeer Explorer to compare your price to other active orchestrators. Most gateways have a maximum price they will pay, and any orchestrator above that ceiling receives no work.
  2. Node is unreachable — gateways cannot connect to your service URI. Test reachability from outside your network: curl -v https://<your-service-uri>:8935/status. Port 8935 must be accessible from the public internet.
  3. Capabilities not registered — for AI workloads, your aiModels.json configuration must match what gateways are requesting. Check tools.livepeer.cloud/ai/network-capabilities to confirm your pipelines appear.

​
Delegator list

Your delegators are LPT holders who have staked to your orchestrator. Their stake contributes to your total and increases your routing probability. What to watch:
  • Delegators with unbonding status — they are in the process of leaving. This reduces your stake at the next round.
  • New delegations — incoming stake increasing your rank.
  • Large single-delegator dependence can destabilise your active set position. One delegator holding most of your stake can move you sharply when they leave.
Why delegators leave: Delegators evaluate your orchestrator on reward cut, fee share, reward call rate, and general reputation. Missed reward calls reduce their yield directly and are the most common reason for unbonding.

​
Service URI

Your registered service URI is what gateways use to connect to your node. It must:
  • Resolve to your current node’s IP or hostname
  • Have port 8935 publicly accessible
  • Match what your node is actually serving on
If there is a mismatch between what is on-chain and where your node is actually running, you will see this error at startup: 
Service address https://127.0.0.1:4433 did not match discovered address https://121.5.10.8:8935;
set the correct address in livepeer_cli or use -serviceAddr
Fix by setting -serviceAddr <public-ip>:8935 to match what is on-chain, or update the on-chain service URI via livepeer_cli.

​
Rounds active

A simple counter of how long your orchestrator has been registered. This is a soft trust signal for delegators — longer operation with consistent reward calling suggests stability.

​
Common patterns to act on

Metrics and Monitoring

Set up Prometheus and Grafana for live node health monitoring.

Getting Delegates

How to attract LPT delegators and grow your stake.

Reward Calling Guide

Reward calling mechanics, gas costs, and automation.

Troubleshooting

Common errors and how to resolve them.
Last modified on March 16, 2026