Run Network
Infrastructure

Orchestrators coordinate transfers and manage worker pools. Stake-based participation with emission rewards.

Requires: 100+ TAO stake

The Role

Orchestrators are the coordination layer. You receive transfer assignments, distribute work to your pool, and submit proofs to validators.

Responsibilities

  1. 1.Receive transfer assignments from the network
  2. 2.Route chunks to workers in your pool
  3. 3.Collect and submit proofs
  4. 4.Get emissions proportional to verified throughput

How You Earn

Emissions flow to orchestrators based on verified throughput. You keep emissions minus what you pay your workers.

Subnet 75 Emissions
Weight Assignment (based on verified bandwidth)
Your Emissions
You - Worker Payments = Net

What You Need

Stake

100+ TAO

More stake = higher slot priority

Infrastructure

  • 4+ CPU cores
  • 8+ GB memory
  • 100+ Mbps network

Operations

  • 24/7 availability
  • SLA score affects weight assignment

256 Slots

Orchestrator slots are competitive. Higher stake gets priority. If someone stakes more than you, they can take your slot at epoch boundary.

How Weight Works

Weight = SLA Score × Stake Factor

SLA Score (0.0 - 1.0)

  • - Uptime
  • - Task completion rate
  • - Proof submission reliability

Stake Factor

  • - min((stake/100)^0.5, 3.0)
  • - Logarithmic scaling
  • - 10,000 TAO = 3× vs 100 TAO baseline

Performance matters. A well-run 100 TAO orchestrator can outweigh a poorly-run 1,000 TAO one.

Setup

  1. 1

    Deploy infrastructure

    4+ cores, 8+ GB RAM, 100+ Mbps

  2. 2

    Stake 100+ TAO

  3. 3

    Register via protocol endpoint

  4. 4

    Build your worker pool

  5. 5

    Monitor via dashboard

Management Interface

Orchestrator Dashboard[UID #47]

Workers

47

Capacity

2.4 Tbps

SLA

0.87

Stake

142 TAO

Recent: xfer-x7z9 ✓ · xfer-y8a0 ✓ · xfer-z9b1 ⏳