Skip to main content
This step connects the orchestrator to Arbitrum One and registers it on the Livepeer protocol. It requires arbETH for gas and LPT for staking. Asset acquisition often takes hours to days because of exchange availability and bridge confirmation times.
Start this step after arbETH and LPT are already in the orchestrator wallet on Arbitrum One. LPT acquisition on Arbitrum often includes exchange settlement and bridging time, so plan for that lead time.

​
Troubleshooting connection issues

Use curl -k https://YOUR_PUBLIC_IP:8935/status as the main external reachability check while working through these issues.
Verify the -ethUrl endpoint responds to eth_chainId (see Step 1). Check that the API key is active and the Arbitrum network is enabled in the provider dashboard. Switch to the Alchemy public endpoint temporarily to isolate whether the issue is the endpoint or the key.
Test from an external machine: curl -k https://YOUR_PUBLIC_IP:8935/status. If this times out, port 8935 is blocked by a firewall or the address is wrong. Check NAT rules, security group settings (AWS/GCP/Azure), and that the -serviceAddr matches the machine’s public IP. A domain name is more resilient than a bare IP.
Check stake vs current threshold on Explorer. The active set is the top 100 by total stake. Nodes below the threshold are registered but not active - gateways do not route video transcoding to them. Wait up to one full round (22 hours) for the status to update after increasing stake.
Check the ETH balance on Arbitrum. Reward calls use 350,000-450,000 gas; activation uses similar amounts. At typical Arbitrum gas prices, each transaction costs 0.01−0.01-0.05 USD. Keep at least 0.01 ETH on Arbitrum at all times to prevent failed transactions.

​
Next step

Verify your setup

Confirm the node is on-chain, transcoding correctly, running AI inference, and exposing monitoring metrics.
Last modified on March 16, 2026