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
    • Pitch Memo
  • 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
        • Dedicated Ephemeral Node Setup
        • Reverse Proxy Setup
  • 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
    • Developer Ecosystem
    • 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
      • Closed Alpha Testing Phase #4
      • 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
  • Miner Node Workflow
  • Role of Oracle Nodes
  • Future Automation with Chainlink Keepers
  • Why PoUW and Oracle Nodes Matter
  • Conclusion
  1. Technical Architecture
  2. Consensus & Validation
  3. Proof of Useful Work (PoUW) State Machine

Miner & Oracle Nodes in PoUW State Machine

In the Cortensor network, Miner Nodes and Oracle Nodes work together to run the Proof of Useful Work (PoUW) state machine. This system ensures efficient, fair, and reliable execution of AI inference tasks in a decentralized manner. The Miner Nodes perform the AI work across various states, while Oracle Nodes monitor the system's flow to ensure that all tasks are completed on time and that the network progresses smoothly.

Miner Node Workflow

Miner Nodes are responsible for executing tasks across a series of state transitions in the PoUW state machine. These states include:

  1. Request: The network randomly selects a Miner Node to start a session. The selected Miner Node is required to complete and submit AI inference work within a specified period (e.g., 5 seconds). Failure to do so triggers Oracle Nodes to request the network to reassign the task to another Miner.

  2. Create: The selected Miner generates an initial output, such as a set of fields or topics, based on predefined prompts. If the Miner fails to submit the necessary data within the set timeframe, Oracle Nodes request the network to select another Miner.

  3. Prepare: In this state, the output generated in the Create state is expanded upon. The selected Miner uses the initial output to generate further questions or relevant data for the next step. The complexity of the task is higher in this state, and Miners are again monitored by Oracle Nodes to ensure deadlines are met.

  4. Precommit: A set of Miners is selected to perform useful work (e.g., generating answers based on the previous states' output). Miners submit a hash of their work during this stage to prevent dishonest behavior and tampering.

  5. Commit: The Miners reveal their actual work, and it is verified against the hash submitted during the Precommit stage. Once verified, the session progresses to the final state.

  6. End: The session concludes, and the results are finalized. Oracle Nodes request the network to clean up the session and prepare for the next.

Miner Nodes must complete their tasks within the assigned timeframes. Failure to do so can negatively impact their reputation, which affects future network incentives and their ability to receive more tasks.

Role of Oracle Nodes

Oracle Nodes do not assign tasks but play a critical role in ensuring that the PoUW state machine operates smoothly and within the required time constraints. They monitor the state transitions and act as the sole mechanism that requests the network or smart contracts to:

  • Transition from one state to another.

  • Reassign tasks to new Miner Nodes when the current Miners fail to meet the deadlines.

For example, if a Miner Node does not complete the Create state work within the specified period, the Oracle Node will request the network to move the task to another Miner. Oracle Nodes ensure that tasks are completed in a timely fashion and maintain fairness across the network by holding all Miner Nodes to the same standards.

Future Automation with Chainlink Keepers

Currently, Cortensor operates the Oracle Nodes manually to monitor and regulate the state transitions. However, as the network matures, the plan is to transition to using Chainlink’s Automation tool, Keepers Registry. This decentralized network of off-chain nodes will handle registered jobs (upkeeps) in a trust-minimized manner, triggering state transitions based on pre-configured conditions, such as time-based or event-driven actions.

This automation will ensure a fully decentralized, reliable, and scalable mechanism for state transitions, minimizing the need for manual interventions and improving network efficiency. This transition is scheduled for implementation closer to the testnet phase.

Why PoUW and Oracle Nodes Matter

The PoUW state machine, monitored by Oracle Nodes, ensures that the Cortensor network can handle AI inference tasks efficiently and securely. By coordinating Miner Nodes and ensuring timely execution of tasks, Oracle Nodes contribute to the overall quality, fairness, and scalability of the network. This system can also be extended in the future to generate and provide services like synthetic data generation, showcasing the broader potential of the Proof of Useful Work mechanism.

Conclusion

The combined efforts of Miner and Oracle Nodes ensure the integrity and efficiency of Cortensor’s decentralized AI inference network. As the network evolves, Oracle Nodes will play a critical role in ensuring smooth operation and maintaining fairness among Miner Nodes. Their regulation of the PoUW state machine will evolve through automation, further solidifying Cortensor’s commitment to a decentralized, scalable, and high-quality AI service network.

PreviousProof of Useful Work (PoUW) State MachineNextSampling in Large Distributed Systems

Last updated 9 months ago