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
        • 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
  • Overview
  • Prerequisites
  • Key Differences from Standard Miner Setup
  • How to Start
  • Use Case
  • What’s Next
  1. Getting Started
  2. Installation & Setup
  3. Router Node Setup

Dedicated Ephemeral Node Setup

PreviousRouter API ReferenceNextReverse Proxy Setup

Last updated 2 days ago

Overview

A Dedicated Ephemeral Node allows a user to directly assign their own miner (inference node) to a session they have created. This setup is ideal for private use cases or testing, where task routing bypasses automatic node selection logic.

This mechanism is similar to regular ephemeral miners but introduces manual pairing of node and session by the user.

⚠️ Note: No authentication is enforced yet. Access control and auth mechanisms will be introduced in upcoming updates.


Prerequisites

Before you begin, ensure you have followed the general installation instructions:

📖

This includes:

  • Installing cortensord

  • IPFS setup

  • Environment configuration

  • Docker installation


Key Differences from Standard Miner Setup

Component
Regular Miner
Dedicated Ephemeral Node

Startup Command

minerv4 or default

minerv3

Session Assignment

Automatically selected via router & reputation logic

Manually assigned to session you control

Authorization

Session, Session Queue & Session Auth

N/A (auth coming soon)


How to Start

  1. Update .env File Ensure your environment file is configured with the correct values, especially:

    CONTRACT_ADDRESS_RUNTIME=<runtime_contract_address>
  2. Start as Dedicated Ephemeral Miner Use the following startup command:

    cortensord ~/.cortensor/.env minerv3 1 docker
  3. Use the "Dedicated Nodes" interface to input your node’s address (i.e., the address your miner is registered with).


Use Case

Dedicated Ephemeral Nodes are useful when:

  • You want complete control over which node handles your inference.

  • You’re testing or debugging inference performance privately.

  • You’re building custom integrations with known node-session bindings.


What’s Next

  • Authentication & validation will be added soon to prevent misuse.

Installation and Setup Guide