The previous section covered the off-chain configuration of the AI Orchestrator node. This section details how to connect an AI Orchestrator node to the Livepeer AI network and earn fees for processing AI inference jobs.

​
Prerequisites

  • An established Mainnet Orchestrator within the Top 100 on the Livepeer network
  • A dedicated static IP address or domain name for your AI Orchestrator node
  • An Ethereum wallet funded with enough ETH to cover transaction fees for ticket redemption

​
Ensure you can Redeem Tickets

The Livepeer AI network is currently in Beta but is already integrated into the main go-livepeer software. However, it still uses a separate port for the AI Orchestrator. This means that your Mainnet Transcoding Network Orchestrator is currently unable to directly redeem AI-related tickets. There are two methods to enable your AI Orchestrator node to redeem tickets:

​
Advertising Your AI Service URI

To make your AI Orchestrator node discoverable by AI Gateway nodes on the Livepeer AI network, you need to advertise your AI service URI on-chain. You can do this by registering your service URI with the AIServiceRegistry contract on the Arbitrum Mainnet.

The easiest and recommended method is to use the Foundry smart contract deployment toolchain.

1

Install Foundry Cast

Install Foundry Cast by executing the following commands in your terminal:

curl -L https://foundry.paradigm.xyz | bash
source /home/<USERNAME>/.bashrc
foundryup
2

Set your Service URI

No need to move your Mainnet Transcoding Network Orchestrator wallet. You can run Foundry Cast and register your AI Orchestrator from any machine.

Set your Service URI, ensuring it starts with https://, using the SetServiceURI function on the AIServiceRegistry contract. Use the KeyStore file and password from your Mainnet Transcoding Network Orchestrator wallet:

cast send --keystore '<path to keystore>' --password '<password>' --rpc-url <arbitrum RPC URI> 0x04C0b249740175999E5BF5c9ac1dA92431EF34C5 "setServiceURI(string)" https://<public orch URI>:<public orch port>

After successful execution, the output should look like this:

blockHash:               0x214a65d2dffd1732e971bd3662dcb681663c2eb0c95a33c8918bab0a44e2d3ed
blockNumber:             200370198
3

Verify your Service URI

Verify your Service URI by invoking the getServiceURI function on the AIServiceRegistry contract:

cast call --rpc-url <arbitrum RPC URI> 0x04C0b249740175999E5BF5c9ac1dA92431EF34C5 "getServiceURI(address)" <public wallet key> | xxd -r -p

If successful, the output should be:

https://<public orch URI>:<public orch port>

Congratulations! Your AI Orchestrator node is now discoverable by AI Gateway nodes and ready to execute AI inference tasks on the Livepeer AI network! 🚀

​
Launch your On-chain AI Orchestrator

Once you’ve set your AI service URI on-chain, you can launch your AI Orchestrator node to start processing AI inference jobs on the Livepeer AI network. The commands to start the AI Orchestrator are similar to those for the off-chain Orchestrator, but with additional flags to enable on-chain functionality:

  • -AIServiceRegistry: Ensures that the Orchestrator is connected to the Livepeer AI network.
  • -network=arbitrum-one-mainnet: Connects the AI Orchestrator node to the Arbitrum Mainnet network.
  • -ethUrl=https://arb1.arbitrum.io/rpc: Sets the Arbitrum Mainnet RPC URL. You can replace this with your own RPC URL.
  • -ethKeystorePath=/root/.lpData/arbitrum-one-mainnet/keystore: Sets the path to the AI Orchestrator’s Ethereum keystore file.
  • -ethAcctAddr <AI_ORCH_ETH_ADDRESS>: Sets the Ethereum address of the AI Orchestrator.
  • -ethPassword=/root/.lpData/.eth_secret: Sets the Ethereum keystore password file path.
  • -ethOrchAddr=<MAIN_ORCH_ETH_ADDRESS>: Sets the Ethereum address of the Mainnet Transcoding Network Orchestrator.

Due to current limitations in the Livepeer AI software, the following flag is required:

  • -ticketEV=2999999999999: This flag ensures that the AI Orchestrator doesn’t trigger maximum ticket limits set by the go-livepeer software.

Was this page helpful?

Suggest editsRaise issue