Which path is yours?

There are two ways to participate on the supply side of Livepeer. They are independent: you can do either, both, or move between them over time.

​

I have GPUs → Orchestrator

You run hardware and want it to earn. As an orchestrator you install go-livepeer, advertise what your GPU can do, and the network sends you video and AI jobs. You earn ETH for completed work and LPT for participating in the protocol each round. You’ll want: an NVIDIA GPU, a Linux machine with a public IP, some ETH and LPT on Arbitrum One, and a willingness to keep a server online.

​

I have LPT → Delegator

You hold LPT and want it to work without running infrastructure. As a delegator you bond your LPT to an orchestrator you trust. Your tokens stay in your control — they are never handed to the operator — and you share in that orchestrator’s rewards. You’ll want: LPT on Arbitrum One, a small amount of ETH on Arbitrum for gas, and a wallet you can connect to the Livepeer Explorer.

​

I want to build an app → Developer (coming soon)

You want to use the network’s compute — send video or AI jobs from your application — rather than supply it. That’s the demand side, and its docs aren’t here yet: a developer platform, and a Build section of this site, are on the way. Until then, the best place to ask what’s possible today is the Livepeer Discord. If you’re curious how demand reaches the network in the meantime, How the network works shows the full path from application to GPU.

​

Not sure yet?

Both roles share the same economics — read Economics to see how ETH fees and LPT inflation are split between orchestrators and their delegators. That one page explains why each side does what it does.