Node Runtime
Last updated: 2026-06-28
The node runtime is distributed as the cortensord binary. Setup guides use the binary interface only.
cortensord ~/.cortensor/.env <role>
Roles
| Role |
Purpose |
routerv1 |
API coordinator for completions, delegate, validate, factcheck, MCP/A2A, x402, privacy, and off-chain flows. |
minerv4 |
Inference worker that accepts assignments and commits results. |
oraclev3 |
Lifecycle coordinator/watcher role. |
validatorv1 |
Network task-level checker/regulator with cognitive-level and node-level validation. |
validatorv2 |
Post-result quantitative validator for network task results. |
validatorv3 |
Post-result qualitative validator for network task results. |
poolv1 |
Pool management role. |
qualityv1 |
User task quality sampling oracle with heartbeat-style sampling behavior. |
tool |
Key, registration, verification, migration, and maintenance commands. |
Runtime Capabilities
- Flask REST APIs and route modules.
- WebSocket router/miner communication.
- MCP stream/SSE support.
- A2A discovery through agent cards.
- x402 payment-gated endpoints and trial quotas.
- off-chain payload storage and signed result writes.
- privacy policy and encryption checks.
- task/session watchers and contract wrappers.
System Context
| Area |
Runtime context |
| Platforms |
Linux, macOS, and Windows are supported platforms. |
| Runtime dependencies |
Docker is used for model/runtime isolation; storage-related flows may use off-chain storage such as IPFS-style providers. |
| Hardware |
CPU and GPU execution are both in scope; quantized models broaden participation beyond high-end GPUs. |
| Models |
Both quantized and non-quantized model paths exist through llamafile and Ollama-style workers. |
| Node setup |
Operators generate node/API/encryption keys, configure .env, register/verify where required, then run the role. |
| Service management |
Packaged service behavior is documented in setup guides when a role has a supported service workflow. |
Operator Reference Areas