Community Programs¶

Last updated: 2026-07-13

Community programs are the participation layer around Cortensor: testing campaigns, product demos, builder contests, Discord recognition, governance participation, and historical token-operation records. The active setup guides remain in Getting Started; community program pages explain why those guides exist and how earlier phases shaped the current network.

Program Lifecycle¶

flowchart LR
  Test["Test<br/>alpha, DevNet, testnets"]
  Build["Build<br/>hackathons, sprints, tools"]
  Demo["Demo<br/>dashboard and product flows"]
  Recognize["Recognize<br/>builders and operators"]
  Improve["Improve<br/>docs, setup, launch readiness"]

  Test --> Build
  Build --> Demo
  Demo --> Recognize
  Recognize --> Improve
  Improve --> Test

Test

Closed alpha, DevNet, Testnet-0, and Testnet-1A campaigns surface operator, dashboard, model, and network-readiness feedback.

Build

Hackathons and mini sprints turn network capabilities into apps, agents, SDKs, dashboards, and public-good tooling.

Demo

Product demos explain real dashboard, node, session, task, model, reward, and developer flows in a way the community can inspect.

Recognize

Contributor roles, grants, and profiles preserve useful work without replacing the active terms of each campaign.

Program Map¶

Program area	What it covers	Continue with
Testing campaigns	Closed alpha, DevNet, Testnet-0, Testnet-1A, dashboard feedback, node-operation feedback, and launch-readiness exercises.	Launch Timeline, Infra And Ops
Builder programs	Hackathons, mini sprints, agent-app briefs, project ideas, and public-good tooling.	Hackathons And Builders, Project Ideas
Product demos	Short demos that explain dashboard, node, session, task, reward, and developer flows from a product point of view.	Dashboard, Use Cases
Builder and operator recognition	Discord roles, operator participation, community support paths, and public contribution signals.	Hackathons And Builders, Mini Builder Sprint
Governance and compliance	Token-holder participation, proposal direction, security controls, privacy expectations, KYC/AML where required, and restricted-address handling.	Terms Of Use, Safety And Restricted Addresses
Token operations	Historical buybacks, liquidity support, staking reserves, incentive allocation, and safe-wallet management.	Tokenomics, Staking

Testing History¶

The community-testing archive contains several overlapping phases. This structure keeps the useful history while separating it from live setup instructions.

Historical phase	Purpose	Current use
Closed Alpha phases 1-6	Early community testing, role assignment, mining feedback, and operator learning.	Participation history and background for how the operator program evolved.
DevNet mapping and module notes	Pre-testnet contract/module mapping, parameters, and migration notes.	Architecture background; live commands use the current contract and deployment tables.
Testnet-0	Arbitrum Sepolia-oriented public testing with gas, operator, dashboard, and stress-test focus.	Current shared-L2 test environment when the guide names Testnet-0.
Testnet-1A	COR-gas L3-oriented testing with its own dashboard, RPC, explorer, and router pools.	Current L3 test environment when the guide names Testnet-1A.
Testnet phase memos	Planning notes for validation, privacy, payments, rewards, SDKs, x402, ERC-8004, and mainnet preparation.	Roadmap context; active launch claims belong in 2026 Network Launch.

Current Testnet Links¶

Environment	Dashboard	RPC	Explorer
Testnet-0	dashboard-testnet0.cortensor.network	arb-sepolia-rpc.cortensor.org	sepolia.arbiscan.io
Testnet-1A	dashboard-testnet1a.cortensor.network	testnet1a-rpc.cortensor.org	testnet1a-explorer.cortensor.network

Keep each environment label with its matching RPC, explorer, router hosts, session IDs, and contract deployments. Do not combine Testnet-0 and Testnet-1A values in the same command, transaction check, or dashboard interpretation.

Product Demo Contests¶

Product demo video contests focus on showing how Cortensor behaves in real usage rather than asking builders to create a new app. The Testnet Phase #2 demo contest ran as an archived community format from January 26 to February 23, 2026, focused on short dashboard walkthroughs and product explanations.

Requirement	Meaning
Demo length	Short, clear videos around one to two minutes.
Primary surface	The named testnet dashboard, especially node, session, task, reward, model, and metrics flows.
Perspectives	Node operator, developer, or ecosystem observer.
Accessibility	Captions or readable on-screen annotations so the demo works without audio.
Judging focus	Clarity, technical accuracy, realistic flows, product explanation, and alignment with decentralized AI infrastructure.
Submission pattern	X post with the demo, community hashtags, and a Discord share link for tracking.

Archived Testnet Phase #2 field	Value
Window	January 26 to February 23, 2026.
Format	One-to-two minute product demo video.
Suggested perspectives	Node operator, developer, observer, or ecosystem explainer.
Submission pattern	Quote-post the official X announcement with `#Cortensor` and `#CortensorProductVideo`, then share the post in Discord `#social-posts`.
Prize structure	First place $150, second $100, third $50, fourth and fifth $25.
Review criteria	Clear story, technical accuracy, product explanation, useful walkthrough, and realistic dashboard behavior.

The same standards apply to future demos: show real behavior, explain what the viewer is seeing, avoid invented data, and connect the product surface back to routers, sessions, miners, validators, payments, and dashboard state.

Every demo needs the exact dashboard environment being shown. Testnet-0 and Testnet-1A have different dashboards, RPC URLs, explorers, contracts, and gas context; a useful video makes that environment visible before explaining sessions, tasks, rewards, models, or node metrics.

Demo Review Rubric¶

Criterion	Strong demo signal
Environment clarity	Names Testnet-0 or Testnet-1A and shows the matching dashboard or explorer context.
Product story	Explains why the flow matters, not just which buttons were clicked.
Technical accuracy	Uses real sessions, tasks, models, rewards, nodes, or routes and avoids mixing environments.
Viewer usefulness	Helps another operator, builder, or community member understand what to do next.
Accessibility	Captions, readable labels, or narration make the demo understandable without guessing.

Contributor Recognition¶

Community roles and recognition are used to identify participants who help test, operate, explain, and improve the network.

Recognition area	What it can represent
Testing roles	Participation across closed alpha, testnet phases, and operator feedback rounds.
Operator contributions	Running nodes, reporting failures, sharing reproducible setup notes, and improving reliability.
Builder contributions	Apps, agents, SDK helpers, dashboard explainers, integrations, documentation, and support tooling.
Community support	Helping other participants understand setup, dashboards, safety practices, and realistic network behavior.

Recognition and rewards follow the active campaign terms for the relevant phase. Historical role names and previous eligibility notes do not replace current participation rules.

Governance And Compliance¶

Cortensor governance and compliance material centers on transparent participation, token-holder alignment, security, and legal controls.

Area	How it appears in the ecosystem
Governance participation	Describe proposal, voting, staking, and community input direction without promising a specific live governance process until it is published.
Security and privacy	Connect privacy, encryption, restricted-address policy, and user-data handling to Privacy Policy and Private Inference.
KYC/AML and restrictions	State that certain roles, features, rewards, jurisdictions, addresses, or users may be restricted where required.
Misuse prevention	Tie abuse, sanctions, fraud, and prohibited-use language to Safety And Restricted Addresses.

Token Operation Records¶

Historical token-operation pages include buyback activity, liquidity support, incentive allocation, safe-wallet management, and staking reserve planning. The useful public summary belongs in tokenomics and staking; transaction-level logs should be treated as historical records unless the team publishes a current operations ledger.

Topic	Main page
`$COR` purpose, utility, supply, allocation, and token addresses	Tokenomics
Staking pools, APR schedule, staking contracts, and refill operations	Staking
Safe wallets, liquidity reserves, incentives, and operational cautions	Tokenomics
Legal and market-risk treatment	Disclaimer And Legal Safety

If you need...	Continue with
Current setup instructions	Getting Started
Live environment URLs	Infra And Ops, Dashboard
Builder and hackathon material	Hackathons And Builders
Token and staking context	Economics Overview, Tokenomics, Staking
Historical roadmap context	Historical Roadmaps