Contributor Profiles¶
Last updated: 2026-06-28
Cortensor is built by a core technical team and a wider contributor community across infrastructure, operations, tooling, testing, content, and community support.
Background¶
The founding and contributor base includes experience in distributed systems, blockchain infrastructure, AI platforms, DePIN, cloud infrastructure, gaming backends, fintech, operations, and community-led node programs.
Contributor Areas¶
| Area | What contributors do |
|---|---|
| Engineering and infrastructure | Architecture, distributed systems, protocol/runtime design, network reliability. |
| Operations and community | Telegram, Discord, X, support flows, validator coordination, node onboarding. |
| Infrastructure and DevOps | RPC infrastructure, server setup, uptime, monitoring, validator and node operations. |
| Infrastructure tooling | Watchdogs, monitoring utilities, operator tooling, reliability dashboards. |
| Product testing | Sessions, tasks, dashboards, model selection, parameter flows, user feedback. |
| Education and content | Tutorials, social posts, community explanations, setup walkthroughs. |
Community Contributors¶
| Contributor | Area | Public contact |
|---|---|---|
| Shelby | Operations and community coordination. | Telegram, X |
| Agnc | RPC infrastructure, node onboarding, validator uptime. | Telegram, X |
| Scerb | RPC infrastructure, tooling, watchdog systems, node support. | Telegram: Bo, X |
| Beran | Node operations, monitoring/app tooling, community participation. | Telegram: @beranalpagion, X: @beranalpagion |
| Bahadir | Validator operations, product testing, educational/community content. | Telegram: @bahadir69, X: @bozdemir5269 |
| Qbert | Node monitoring, operator visibility, health metrics, alerts. | Telegram, X |
| Tyrell | Product testing, dashboard workflows, community support and feedback. | Telegram: @tyrell060, X: @crtyptyrelll |
Profile Maintenance¶
Contributor profiles should stay concise and consent-based:
- keep role and contribution area current;
- include public links only when the contributor wants them listed;
- avoid overstating current employment or active responsibility;
- move inactive roles to historical context when needed.