# Product Demo Video Contest (Testnet Phase #2) **Status:** Announced – **Submission Window: Jan 26 → Feb 23, 2026**\ **Scope:** Testnet-0 Dashboard · Product Demo Videos (1–2 minutes)\ **Dashboard:** [https://dashboard-testnet1a.cortensor.network/](https://dashboard-testnet0.cortensor.network/) *** #### Overview With **Testnet Phase #1 completed** and the **Testnet-1a dashboard** now refined for end-to-end flows, this is a good moment to showcase Cortensor from a **product** point of view — not just from infra or code. To do that, we’re running a **Product Demo Video Contest** during **Testnet Phase #2**, focused on: * How the **Testnet-1a dashboard actually behaves in practice** * How node operators, developers, and observers experience Cortensor day to day * Collecting feedback on what still feels confusing or missing This is lighter-weight than a hackathon: you’re not building a new app, you’re **telling the story** of the product as it exists today. *** #### What We’re Looking For Short, **story-style product demos**, not just UI fly-throughs. **Video length:** * \~**1–2 minutes** per submission **Suggested perspectives (pick one or mix):** * **Node Operator View** * How you see capacity, rewards, and performance * What matters on the dashboard (uptime, precommit, rankings, node status, etc.) * **Developer View** * How you trigger and monitor sessions & tasks * How you use long-context, model selection, and parameters * How you’d explain the dashboard to another developer integrating Cortensor * **Observer / Ecosystem View** * “What is Cortensor?” explained *through* the dashboard * How Testnet-1a behaves under load or during live testing * How nodes, sessions, tasks, and payments fit together visually **Accessibility:** * Please **include captions or on-screen text** so the video is understandable without sound. *** #### Why Now We’ve just completed a round of **UI/UX refinements** around: * Testnet-1a **dashboard flows** * End-to-end **task execution and monitoring** * **Node/operator visibility** and basic metrics The contest helps us: * **Showcase** the dashboard in real usage, not just static screenshots * **Collect feedback** on what’s confusing, missing, or hard to discover * **Highlight community perspectives** on how Cortensor feels as a product *** #### Submission Guidelines **Content** * Must primarily feature the **Testnet-1a dashboard**\ * Focus on a **clear narrative**: * Who you are (operator / dev / observer) * What you’re showing * Why it matters for Cortensor * Realistic flows only – no fake data or misleading claims **Format** * 16:9 or vertical is fine; UI elements must be clearly readable * **1–2 minutes** total runtime * Captions or readable on-screen annotations required **How to Submit (Important)** To make sure your entry is counted, please follow **all three** steps: 1. **Quote-post** the official contest announcement on X with your **product demo video** attached. 2. In your quote post, include both tags: * `#Cortensor` * `#CortensorProductVideo` 3. After posting on X, **share the X link** in our Discord **#social-posts** channel:\ Only entries that complete **all three steps** (quote post + tags + Discord link) will be considered for judging and prizes. **Who Can Participate** * Open to **Cortensor community members** who are: * Building on or running nodes against the **Testnet-1a dashboard** during Phase #2 * Actively using the dashboard in a realistic way (operators, devs, ecosystem contributors) *** #### Judging & Awarding Policy Placements **aren’t automatic or first-come** — they’re decided by the Cortensor team based on **quality, clarity, and usefulness** of the demo (how well it explains the dashboard and flows). **Quality over rank** Prizes are **not** awarded strictly by “first to submit,” view count, or any numerical leaderboard. Cortensor will judge qualified demo videos based on: * **Overall quality and clarity** * How clearly the video explains what’s happening on the **Testnet-1a dashboard**\ () * Pacing, structure, and how easy it is to follow (with captions/on-screen text). * **Impact and storytelling** * How well the demo tells a story: *who* is using Cortensor, *what* they’re doing, and *why it matters*. * Does a new viewer “get” Cortensor in 1–2 minutes? * **Technical accuracy and depth** * Are the flows shown (sessions, tasks, node views, rewards, etc.) **technically correct** for Testnet-1a? * No unrealistic claims or invented behavior; demos should reflect how the dashboard actually works. * **Usability and product explanation** * How well the demo explains *how to use* the dashboard: * Where to click * What key metrics mean * How to interpret results or task runs * Could a new node operator or developer watch this and feel more confident using the product? * **Alignment with Cortensor’s roadmap and positioning** * Does the video portray Cortensor as **decentralized AI infrastructure** (miners, router, sessions, validation), not just “another UI”? * Bonus if it connects naturally to Testnet phases, decentralized inference, or verifiable AI — without over-promising. **Discretionary placement** * Judges may award a prize to **any qualified entry** at a given place. * Example: a later submission that’s clearly higher quality may receive 1st or 2nd place. **No guarantee to fill all places** * Cortensor may **withhold or reallocate** any prize tier if submissions do not meet the expected quality bar. **Internal decision** * Final decisions are made **internally by the Cortensor team** and are not subject to appeal. *** #### Prize Pool (in $COR equivalent) Updated prize pool for this contest: * **1st place:** $150 * **2nd place:** $100 * **3rd place:** $50 * **4th–5th place:** $25 each These are **thank-you rewards** for high-quality demos that help explain Cortensor to future users, node operators, and developers. *** #### Timeline * **Submission Window:**\ **Jan 26 → Feb 23, 2026** * **Who’s Eligible:**\ Anyone **building on or running against** the **Testnet-0 dashboard** during **Testnet Phase #2**. * **Details & Reminders:** * Ongoing reminders and updates will be posted via: * Telegram / Discord * X ([@Cortensor](https://x.com/Cortensor)) * Docs updates You can already start planning your walkthrough — the goal is to **show how the Testnet-1a dashboard works in real usage** and help the next wave of operators and developers onboard faster. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cortensor.network/community-and-ecosystem/contests/product-demo-video-contest-testnet-phase-2.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.