The orchestration layer for Bittensor
Orchestra is the orchestration layer for Bittensor. Submit a high-level objective — market research, competitive analysis, data aggregation — and Orchestra handles the rest: decomposing the task, routing to optimal subnets, executing with hash-locked proofs, and delivering structured, validated results.
The subnet also maintains the Subnet Ledger, a shared registry of every subnet's capabilities, schemas, and endpoints. Miners update the Ledger during orchestration work; validators verify against live subnets. External developers and agent frameworks can query the Ledger via paid API.
Two products, one flywheel: orchestration improves the Ledger, and the Ledger enables better orchestration.
Concept: Complete
Dual-product model defined (orchestration + Ledger)
60/40 emission split between orchestration and Ledger contributions
Demand-driven Ledger coverage model
Documentation: Complete
README with worked example
Incentive mechanism with scoring formulas
Miner architecture and operations guide
Validator architecture and audit logic
Business rationale and revenue model
Go-to-market strategy
Design Decisions:
Ledger is shared network resource, not per-miner cache
Miners propose updates during orchestration work
Validators verify against live subnet probes
External Ledger API as separate revenue stream
Hash-locked proofs for orchestration verification
Next Steps:
Technical specification for synapse formats
Prototype miner implementation
Ledger data model and storage design
External API specification
Nil