# Closed Alpha Testing Phase #4

## **Stress, Scale, and Stability**

Phase #4 marks a critical milestone in the Cortensor Closed Alpha Testing series, designed to push the decentralized AI infrastructure through intensive real-world validation. With major modules now live across DevNet5, this phase will focus on system-wide coordination, stress testing, and scalability verification. Participants who contribute to this critical evaluation will be rewarded in $COR based on performance, uptime, and participation metrics.

### Contest Rules

#### Stake Requirement

* **New Participants**: Stake 4,000 $COR per node (Pool 3) to qualify for Phase #4.

#### Node Uptime

Maintain active, responsive nodes over a 30–45 day window to qualify for full rewards.

#### Bug Reporting

Participants are expected to:

* Report bugs, issues, or feedback directly to Cortensor admins
* Participate in testing discussions and issue reproduction if requested
* Non-participation in reporting may lead to disqualification

#### Disqualification Rights

Cortensor may disqualify any participant for:

* Misrepresenting node performance or system behavior
* Abusing staking or reward rules
* Actions detrimental to network integrity

***

### Rewards

#### Base Reward

* $20/month per active node with qualifying uptime

#### Multi-Node Bonus (one-time)

* 3+ nodes → 10% bonus
* 5+ nodes → 20% bonus

#### Role-Based Bonus

* Discord Roles : Additional 5% for each role
* **Note**: Total bonuses are capped at 30% for fairness.

### Prizes

#### Performance-Based Prizes

Each node that meets **both** of the following conditions will receive:

* 📊 **Total Score ≥ 50%**
* 🔁 **Precommit Score ≥ 60%**

**Reward: $5 per eligible node**

<https://dashboard-devnet5.cortensor.network/stats/heatmap/rank/table>

This shift rewards reliable, consistent performance across the board — not just the top ranks — and ensures that quality contributions are fairly recognized.

***

### Testing Focus

This phase emphasizes end-to-end load handling, real-time routing, and validation under pressure:

#### 🔹 Network Task Shuffling Logic

Live via `NodeUtils` – Enables dynamic, swappable node selection for the **Precommit** phase, enhancing redundancy and response.

#### 🔹 User Task Flow Stress Tests

Full-path validation: **Node Pool ➝ Session Queue ➝ Stats ➝ Reputation** under simulated and community-generated traffic.

#### 🔹 Router Node API Testing

* Open to third-party users for real traffic testing
* Aligned with OpenAI-compatible endpoints
* Reverse proxy setup for production-style integration

#### 🔹 Session UI Iteration

* Improved orchestration visibility
* Real-time feedback from stress tests used to refine UX

#### 🔹 Payment Module Kickoff

* COR-based billing system in development
* Leveraging Sepolia Testnet COR for validation

***

### Key Outcomes

* Confirm dynamic shuffling and session stability under load
* Refine performance-based node reputation scoring
* Validate real-world inference requests through OpenAI-style APIs
* Prove cross-platform desktop app robustness under high activity

***

### Join the Contest

Become a builder in the next evolution of decentralized AI.\
👉 [Join Cortensor Discord](https://discord.gg/cortensor)

Let’s pressure test the future of decentralized AI — together.


---

# 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/community-testing/closed-alpha-testing-phase-4.md?ask=<question>
```

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.
