> ## Documentation Index
> Fetch the complete documentation index at: https://na-36-changelog-go-livepeer-2026-05-18.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Explorer Operations

> A walkthrough of every metric on your Livepeer Explorer orchestrator page – what each number means, what healthy looks like, and what to do when something is wrong.

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:**

```text icon="terminal" title="Explorer orchestrator profile URL" theme={null}
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](https://tools.livepeer.cloud/ai/network-capabilities))
* 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.

> **Self-stake vs delegated stake**
>
> 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](/v2/Orchestrators/guides/staking-and-rewards/delegate-operations).

> **How stake affects job routing**
>
> 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 vs current stake**
>
> 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.

<table>
  <tr>
    Parameter

    What it means

    Who it affects
  </tr>

  <tr>
    **Reward Cut**

    Percentage of LPT inflation you keep. The rest goes to Delegators proportional to their stake.

    Your income + Delegator attraction
  </tr>

  <tr>
    **Fee share**

    Percentage of ETH transcoding fees you share with Delegators.

    Delegator yield
  </tr>
</table>

**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.

> [!WARNING]
>
> 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.

```icon="terminal" theme={null}
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 calling disabled**
>
> `-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.

> **Check your ETH balance for gas**
>
> 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.

> **Check node uptime at round boundaries**
>
> 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.

> **Using OrchestratorSiphon**
>
> If missed rewards are a recurrent problem, consider the [split setup](/v2/Orchestrators/guides/deployment-details/siphon-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](https://explorer.livepeer.org/orchestrators) 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](https://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:

```icon="terminal" theme={null}
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

<table>
  <tr>
    What you see

    What it means

    What to do
  </tr>

  <tr>
    Active Set rank dropping week-over-week

    Relative stake declining vs competitors

    Attract Delegators or increase self-stake
  </tr>

  <tr>
    Missed reward rounds

    Reward calling failing

    Check ETH balance, `-reward` flag, consider Siphon
  </tr>

  <tr>
    Zero fee earnings despite active status

    Not receiving work

    Check pricing, reachability, capabilities
  </tr>

  <tr>
    Delegator count falling

    Delegators unbonding

    Check reward call rate, review Reward Cut competitiveness
  </tr>

  <tr>
    Service URI mismatch warning at startup

    On-chain URI doesn't match node IP

    Update `-serviceAddr` or update on-chain URI
  </tr>
</table>

> **[Metrics and Monitoring](/v2/orchestrators/guides/monitoring-and-tooling/metrics-and-alerting)**
>
> Set up Prometheus and Grafana for live node health monitoring.

> **[Getting Delegates](/v2/orchestrators/guides/staking-and-rewards/delegate-operations)**
>
> How to attract LPT Delegators and grow your stake.

> **[Reward Calling Guide](/v2/orchestrators/guides/staking-and-rewards/reward-mechanics)**
>
> Reward calling mechanics, gas costs, and automation.

> **[Troubleshooting](/v2/orchestrators/guides/monitoring-and-tooling/troubleshooting)**
>
> Common errors and how to resolve them.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.