⚠️ IMPORTANT: This project is still under active development. Currently, you can only run the protocol locally - connecting to public RPCs is not yet supported. Please check back later for updates. See our FAQ for details.
Prime Network is a peer-to-peer compute and intelligence network that enables decentralized AI development at scale. This repository contains the core infrastructure for contributing compute resources to the network, including workers, validators, and the coordination layer.
- System Architecture
- Getting Started
- Documentation
- Frequently Asked Questions
- Community
- Contributing
- Security
- License
The Prime Protocol follows a modular architecture designed for decentralized AI compute:
- Smart Contracts: Ethereum-based contracts manage the protocol's economic layer
- Discovery Service: Enables secure peer discovery and metadata sharing
- Orchestrator: Coordinates compute jobs across worker nodes
- Validator Network: Ensures quality through random challenges
- Worker Nodes: Execute AI workloads in secure containers
- Linux operating system
- CUDA-capable GPU(s) for worker operations
- Docker Desktop and Git installed
For complete setup instructions, refer to our Development Setup Guide.
You can install the latest worker CLI using:
curl -sSL https://raw.githubusercontent.com/PrimeIntellect-ai/protocol/develop/worker/scripts/install.sh | bash
For the latest dev build use:
curl -sSL https://raw.githubusercontent.com/PrimeIntellect-ai/protocol/develop/worker/scripts/install.sh | bash -s -- --dev
- Development Setup Guide - Detailed installation and environment setup instructions
- Usage Guide - Instructions for dispatching tasks, monitoring, and system management
A: Prime Protocol is a peer-to-peer compute and intelligence network that enables decentralized AI development at scale. It provides infrastructure for contributing compute resources to the network through workers, validators, and a coordination layer.
A: No, Prime Protocol is still under active development. Currently, you can only run the protocol locally.
A: We have provided an .env.example file with the required variables.
A: We're actively developing our security practices for private key management.
A: We will be providing detailed documentation on how to secure workers with firewalls for ingress / egress
A: For the current development phase, minimal testnet ETH is sufficient. Detailed information on setting up the worker will follow.
We welcome contributions! Please see our Contributing Guidelines.
See SECURITY.md for security policies and reporting vulnerabilities.