Contributing To Cortensor¶
Last updated: 2026-06-28
Cortensor contributors help through development, model work, validation, documentation, infrastructure, testing, community support, governance participation, and ecosystem applications.
Ways To Contribute¶
| Path | Examples |
|---|---|
| Model development | Prepare, test, fine-tune, benchmark, or document models for Cortensor usage. |
| Task validation | Build validators, scoring utilities, fact-check flows, quality review tools, and evidence bundles. |
| Developer tooling | SDKs, wrappers, CLIs, templates, replay tools, test harnesses, and dashboards. |
| Infrastructure | Run nodes, monitor routers/miners/validators, improve uptime visibility, document setup steps. |
| Community engagement | Answer questions, test product flows, report bugs, collect feedback, support new builders. |
| Documentation and tutorials | Setup guides, API examples, diagrams, glossary entries, troubleshooting notes. |
| Governance participation | Discuss proposals, review risks, contribute implementation feedback, and vote when governance is active. |
Good Contribution Shape¶
A useful contribution usually includes:
- a short description of the problem;
- a working demo, script, patch, or reproducible test;
- clear setup instructions;
- screenshots or logs when visual or runtime behavior matters;
- an explanation of how it uses Cortensor;
- known limitations and safety notes.
Builder Support¶
| Resource | Purpose |
|---|---|
| Getting Started | Choose hosted API, router, node, SDK, or agent-builder path. |
| Web2 API Reference | Build apps against hosted or router-style APIs. |
| Web3 SDK Reference | Understand contract-facing integrations. |
| Model Catalog | Pick model IDs and understand capacity behavior. |
| Hackathon Project Ideas | Choose a starter app or agent idea. |
Rewards And Support¶
Builder rewards, grants, staking alignment, or ongoing support should be tied to current announced programs. Historical hackathon prize tables are preserved on their archive pages; active program terms should be confirmed through the current community announcement before a builder relies on them.