Transcoder Campaign: Open Orchestrator

Hey all,

This is open-orchestrator.eth - we’ve just launched our official campaign! Excited to officially join the community.

We run a globally distributed orchestrator which is completely open source - we built our stack on Kubernetes (a popular solution for managing complex software architectures) and open sourced the entire codebase for the community.

Our orchestrator will be managed using “OIPs” - whenever a protocol-level change is being considered (e.g. reward/fee cuts), or significant change to the off-chain orchestrator parameters (e.g. price per pixel, max face value for tickets, etc), an Orchestrator Improvement Proposal (OIP) must be submitted by the maintainer(s) or by a delegator. This will consist of a PR similar to OIP-1 which outlines the proposed changes and the reasoning for the change. The community will be given seven (7) days to leave comments on the PR before it is merged and executed. If you are a delegator, please turn notifications on for PRs, so you can participate in these discussions. We want complete transparency with our delegators to make sure we maintain the ideals of this great ecosystem.

I also work at Livepeer on the protocol design and web3 initiatives in the company. This is a personal project (not sponsored by Livepeer) built so that it can give back to the community by giving an open source example of one way a globally performant orchestrator can be set up. You’ll see me in the Discord channels as 0xcadams.

Feel free to reach out to me on Discord, I’m always available to help set up new orchestrators, especially using Helm/Kubernetes!

Cheers!

7 Likes

Welcome to the Public Network, Chase!

1 Like

An update for delegators:

The open orchestrator experienced a temporary outage from Nov 16th at 21:50:30 UTC to the following morning at 9:15:00 UTC. During this time, the Arbitrum nginx proxy got into an unrecoverable state on all clusters, despite the upstream Arbitrum failover nginx continuing to respond appropriately. This was likely due to a temporary outage in the community Arbitrum node (as has been seen in the past), which triggers the nginx pod to cache/continue to return a bad response code.

There has been a bug filed in the repo and it will be fixed ASAP. Please subscribe to the Github issue for updates.