> For the complete documentation index, see [llms.txt](https://docs.cortensor.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortensor.network/technical-architecture/node/node-roles.md).

# Node Roles

Cortensor's decentralized AI ecosystem relies on a network of interconnected nodes, each with specific roles to ensure seamless operation and efficiency. This overview details the key roles within the Cortensor network:

### Router Nodes

**Primary Function**: Bridge users and miner nodes, managing task allocation and communication.

**Key Responsibilities**:

* Allocate AI inference tasks to appropriate miner nodes based on their capabilities.
* Ensure secure, encrypted communication between users and miners.
* Manage user sessions, including payment verification and resource allocation.
* Provide interfaces compatible with both Web2 (REST API) and Web3 (SDK).

**Critical Tasks**:

* Optimize task distribution for maximum efficiency.
* Manage session lifecycles and user interactions.
* Maintain data security and privacy through encryption.

### Miner Nodes

**Primary Function**: Execute AI inference tasks and participate in network validation.

**Key Responsibilities**:

* Perform AI inference using various models on diverse hardware (from low-end devices to high-end GPUs).
* Collaborate in task execution and result validation.
* Participate in proof of inference processes.
* Stake tokens and earn rewards based on contributions and performance.

**Critical Tasks**:

* Execute AI inference tasks efficiently.
* Validate results and ensure network accuracy.
* Build and maintain performance-based reputation.

### Clients/Users

**Primary Function**: Initiate and manage AI inference requests.

**Key Responsibilities**:

* Create and manage sessions by depositing tokens (calculated in LLM tokens).
* Submit AI inference requests via smart contracts or REST API.
* Retrieve inference results through secure channels.
* Configure validation requirements for tasks.

**Critical Tasks**:

* Manage AI inference sessions.
* Submit tasks and securely receive results.
* Balance cost and accuracy through validation configuration.

### Oracle/Master Guard Nodes

**Primary Function**: Maintain network timing and oversee block production.

**Key Responsibilities**:

* Track time and manage virtual block production.
* Ensure consistency in network operations and task execution.
* Potentially incorporate high-stakes mining responsibilities.

**Current Status and Future Plans**:

* Initially hosted by the Cortensor team.
* Plans to transition to a permissionless model or integrate with high-stake miner nodes.
* Final implementation details are still to be determined.

**Critical Tasks**:

* Maintain network synchronization.
* Oversee block timing and production.
* Contribute to network stability and reliability.

**Note**: The exact implementation of oracle/master guard nodes is subject to change as the Cortensor network evolves. The team is exploring options to further decentralize this role, potentially by integrating it with existing miner nodes or creating a new class of high-stake nodes with additional responsibilities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.cortensor.network/technical-architecture/node/node-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.