Cortensor
  • Home
  • Abstract
    • Value Proposition
    • Whitepaper
      • Page 1: Introduction and Vision
      • Page 2: Architecture and Technical Overview
      • Page 3: Incentive Structure and Tokenomics
      • Page4: Development Roadmap and Phases
      • Page5: Summary
  • Introduction
    • What is Cortensor?
    • Key Features & Benefits
    • Vision & Mission
    • Team
  • Getting Started
    • Quick Start Guide
    • System Requirements
    • Installation & Setup
      • Getting Test ETH
      • Setup Own RPC Endpoint
      • Router Node Setup
        • Router API Reference
  • Core Concepts
    • Decentralized AI Inference
      • Community-Powered Network
      • Gamification and Quality Control
      • Incentive Structure
    • Universal AI Accessibility
    • Multi-layer Blockchain Architecture
  • Technical Architecture
    • Design Principles
    • Node Roles
    • Node Lifecycle
      • Ephemeral Node State
    • Node Reputation
    • Network & Flow
    • Type of Services
    • Coordination & Orchestration
      • Multi-Oracle Node Reliability & Leadership Rotation
    • AI Inference
      • Open Source Models
        • Centralized vs Decentralized Models
      • Quantization
      • Performance and Scalability
    • Consensus & Validation
      • Proof of Inference (PoI) & Proof of Useful Work (PoUW
      • aka Mining
      • Proof of Useful Work (PoUW)
      • Proof of Useful Work (PoUW) State Machine
        • Miner & Oracle Nodes in PoUW State Machine
      • Sampling in Large Distributed Systems
      • Parallel Processing
      • Embedding Vector Distance
    • Multi-Layered Blockchain Architecture
    • Modular Architecture and Smart Contract Interactions
      • Session Queue
      • Node Pool
      • Session Payment
    • Mining Overview
    • User Interaction & Node Communication
      • Session, Session Queue, Router, and Miner in Cortensor
    • Data Management
      • IPFS Integration
    • Security & Privacy
    • Dashboard
    • Development Previews
      • Multiple Miners Collaboration with Oracle Node
      • Web3 SDK Client & Session/Session Queue Interaction
    • Technical Threads
      • AI Agents and Cortensor's Decentralized AI Inference
    • Infographic Archive
  • Community & Ecosystem
    • Tokenomics
      • Network Incentive Allocation
      • Token Allocations & Safe Wallet Management
    • Staking Pool Overview
    • Contributing to Cortensor
    • Incentives & Reward System
    • Governance & Compliance
    • Safety Measures and Restricted Addresses
    • Buyback Program
    • Liquidity Additions
    • Partnerships
      • Partnership Offering for Demand-Side Partnerships
    • Community Testing
      • Closed Alpha Testing Phase #1
        • Closed Alpha Testing Phase #1 Contest: Closing & Winners Announcement
      • Closed Alpha Testing Phase #2
      • Closed Alpha Testing Phase #3
      • Discord Roles & Mainnet Privileges
      • DevNet Mapping
      • DevNet Modules & Parameters
    • Jobs
      • Technical Writer
      • Communication & Social Media Manager
      • Web3 Frontend Developer
      • Distributed Systems Engineer
  • Integration Guide
    • Web2
      • REST API
      • WebSocket
      • Client SDK
    • Web3
      • Web3 SDK
  • Use Cases
  • Roadmap
    • Technical Roadmap: Launch to Next 365 Days Breakdown
    • Long-term Vision: Beyond Inference
  • Glossary
  • Legal
    • Terms of Use
    • Privacy Policy
    • Disclaimer
    • Agreement for Sale of Tokens
Powered by GitBook
On this page
  • Router Nodes
  • Miner Nodes
  • Clients/Users
  • Oracle/Master Guard Nodes
  1. Technical Architecture

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.

PreviousDesign PrinciplesNextNode Lifecycle

Last updated 9 months ago