8.3 Roadmap & Known Limitations
Development Phases
| Phase | Timeline | Target |
|---|---|---|
| 1 — Bootstrap | Months 1–6 | 30–50 miners, 5–10 validators, 1K+ workflows/day |
| 2 — Developer Adoption | Months 6–12 | 10+ apps, 10K+ workflows/day |
| 3 — Revenue Model | Months 12–24 | Gateway fee launch; ~$540K/month |
| 4 — Ecosystem Standard | 24+ months | Trustless fee R&D; BERTScore upgrade |
Known Limitations and Upgrade Path
| Limitation | v1 Approach | Upgrade Path |
|---|---|---|
| No on-chain execution receipts | Off-chain logs + Yuma consensus | Sub-subnet with receipts (Phase 4) |
| No protocol-level fee collection | Gateway-level (centralised) | Trustless billing if Subtensor adds EVM |
| ROUGE-L only for RAG quality | Deterministic, reproducible | Local BERTScore (v2) |
| Manual Execution Support Pool | Owner transfers each tempo | Multi-sig governance (Phase 4) |
| No on-chain slashing | Economic + governance penalties | If added to Bittensor protocol |
| Social scoring upgrade protocol | ≥67% stake vote | Automated governance module (Phase 3+) |
Rapid Iteration Principle
Following the fail-fast approach, C-SWON uses Docker Watchtower and Git hooks so validators auto-update when the incentive mechanism changes on main. Testnet is not a staging buffer — it is a live experiment.
Navigation
| ← Previous | 8.2 Go-to-Market Strategy |
| → Next | 9.1 Contributing Guide |
| Index | Documentation Index |