Model Nodes are managed clusters that run participant models and make them callable over the network — without exposing the underlying model code. They solve three problems:Documentation Index
Fetch the complete documentation index at: https://protocol.crunchdao.com/llms.txt
Use this file to discover all available pages before exploring further.
- Remote access — models for a Crunch are callable via gRPC from anywhere
- Intellectual property protection — models are only reachable through an API; no direct code access is provided
- Access control — the protocol defines who can call which model, and under what rules
How it works
Here is what happens when a Cruncher submits a model:On-chain authorization
The Crunch Protocol writes an authorization on-chain, granting the right to run and call that
model remotely.
Deployment
The Model Orchestrator reads the blockchain, detects the new authorization, and reacts by:
- Building an execution environment (e.g., a Docker container) that makes the model callable
- Deploying the container on a cloud platform
- Sharing connection details with the Coordinator
Components
Model Nodes rely on three open-source components maintained by CrunchDAO:| Component | Role | Links |
|---|---|---|
| Model Runner | gRPC server that runs alongside each model, making it callable over the network | Docs · GitHub |
| Model Runner Client | Coordinator-side Python library for calling models concurrently | Docs · GitHub |
| Model Orchestrator | Manages the lifecycle of model containers — starting, stopping, and health monitoring | Docs · GitHub |
Deep dives
Model Runner and Client
How models are made callable and how the Coordinator calls them.
Model Orchestrator
How model containers are deployed, monitored, and kept reachable.
Access Control
The Secure Model Protocol that authenticates communication.