Skip to content

Latest commit

Β 

History

35 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

🌐 CIRO Network

Decentralized Compute Layer for Starknet

Cairo 1.0 Rust Starknet BSL 1.1 License Future Apache License

Transform idle GPUs into a decentralized AI powerhouse on Starknet


πŸš€ Overview

CIRO Network is a Starknet-native marketplace that connects GPU owners with AI applications, creating a decentralized compute layer for the next generation of dApps. Built with Cairo smart contracts and Rust infrastructure, it provides low-latency, verifiable compute while feeding CIRO's real-time context engine.

Key Features

  • πŸ”— Starknet Native: Built specifically for Starknet's proving infrastructure
  • ⚑ Low Latency: <100ms response times for real-time applications
  • πŸ›‘οΈ Verifiable Compute: ZK-ML proofs ensure computation integrity
  • πŸ’° Economic Security: Stake/slash mechanisms protect against malicious actors
  • πŸ–₯️ Cross-Platform: Worker nodes run on Windows, macOS, and Linux
  • πŸ”„ CIRO Integration: Seamless connection to existing analytics platform

πŸ—οΈ Architecture

CIRO Network is transitioning from a centralized coordinator model to a fully decentralized P2P architecture:

Current Architecture (Centralized)

Job Clients β†’ HTTP API β†’ Coordinator β†’ Database β†’ HTTP API β†’ Workers
     ↓                        ↓                        ↓
[REST API]            [In-Memory Pool]           [Registration]
                      [Task Queue]               [Capability Match]

Target P2P Architecture (Decentralized)

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                    CIRO P2P Network                             β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                                                 β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”         β”‚
β”‚  β”‚  Worker A   │◄──►│  Worker B   │◄──►│  Worker C   β”‚         β”‚
β”‚  β”‚  (libp2p)   β”‚    β”‚  (libp2p)   β”‚    β”‚  (libp2p)   β”‚         β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜         β”‚
β”‚         β”‚                 β”‚                 β”‚                  β”‚
β”‚         β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜                  β”‚
β”‚                           β”‚                                    β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”‚
β”‚  β”‚              Gossip Protocol                             β”‚  β”‚
β”‚  β”‚  β€’ Job Distribution    β”‚  β€’ Capability Broadcasting      β”‚  β”‚
β”‚  β”‚  β€’ Result Collection   β”‚  β€’ Reputation Updates           β”‚  β”‚
β”‚  β”‚  β€’ Network Health      β”‚  β€’ Blockchain State Sync       β”‚  β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚
β”‚                           β”‚                                    β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”‚
β”‚  β”‚                DHT-Based Discovery                       β”‚  β”‚
β”‚  β”‚  β€’ Peer Finding        β”‚  β€’ Capability Indexing         β”‚  β”‚
β”‚  β”‚  β€’ Bootstrap Nodes     β”‚  β€’ Network Topology            β”‚  β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚
β”‚                                                                 β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”‚
β”‚  β”‚                 Starknet Integration                       β”‚  β”‚
β”‚  β”‚  β€’ Job Contracts      β”‚  β€’ Payment Settlement           β”‚  β”‚
β”‚  β”‚  β€’ Worker Staking     β”‚  β€’ Reputation Storage           β”‚  β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ“– Full P2P Architecture Documentation


πŸ“ Project Structure

ciro-network/
β”œβ”€β”€ cairo-contracts/          # Starknet smart contracts
β”‚   β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ tests/
β”‚   └── scripts/
β”œβ”€β”€ rust-node/               # Worker node implementation
β”‚   β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ docker/
β”‚   β”œβ”€β”€ config/
β”‚   β”œβ”€β”€ demo_script.sh        # AI capabilities demo
β”‚   └── demo_p2p.sh           # P2P networking demo
β”œβ”€β”€ tauri-app/               # Cross-platform desktop app
β”‚   β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ src-tauri/
β”‚   └── dist/
β”œβ”€β”€ backend/                 # Backend services & APIs
β”‚   β”œβ”€β”€ api/
β”‚   β”œβ”€β”€ services/
β”‚   └── db/
β”œβ”€β”€ docs/                    # Documentation
β”‚   β”œβ”€β”€ P2P_ARCHITECTURE.md  # P2P networking architecture
β”‚   β”œβ”€β”€ architecture/
β”‚   β”œβ”€β”€ user-guides/
β”‚   └── api-reference/
└── .taskmaster/            # Project management
    β”œβ”€β”€ tasks/
    └── docs/

πŸ› οΈ Technology Stack

Smart Contracts

  • Cairo 1.0: Starknet-native smart contracts
  • Scarb: Package manager and build tool
  • Starknet Foundry: Testing framework

Worker Nodes

  • Rust: High-performance system programming
  • Docker: Containerized compute environments
  • libp2p: Peer-to-peer networking
  • Tokio: Async runtime

Desktop Application

  • Tauri: Cross-platform desktop framework
  • React/TypeScript: Modern web technologies
  • Tailwind CSS: Utility-first styling

Backend Services

  • Rust/Axum: High-performance web framework
  • PostgreSQL: Primary database
  • Redis: Caching and session management
  • Apache Kafka: Event streaming

πŸš€ Quick Start

Prerequisites

Development Setup

  1. Clone the repository

    git clone https://github.com/Ciro-AI-Labs/ciro-network.git
    cd ciro-network
  2. Install dependencies

    # Install Rust dependencies
    cargo build
    
    # Install Node.js dependencies
    cd tauri-app && npm install
  3. Run the development environment

    # Start the backend services
    docker-compose up -d
    
    # Run the desktop application
    cd tauri-app && npm run tauri dev

πŸ“š Documentation


🀝 Contributing

We welcome contributions! Please see our Contributing Guide for details.

Development Workflow

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

πŸ”’ Security

Security is paramount in decentralized systems. Please review our Security Policy and report vulnerabilities to security@ciro.network.


πŸ“„ License

CIRO Network uses a dual licensing strategy to balance IP protection with our commitment to open source:

πŸ“‹ License Summary

Component License Details
Core Smart Contracts BSL 1.1 β†’ Apache 2.0 See WHY_BSL_FOR_CIRO.md
SDKs & Developer Tools Apache 2.0 Immediate open source
Client Libraries MIT Maximum compatibility

πŸ—“οΈ Timeline

  • Today: Core contracts protected under BSL 1.1
  • January 1, 2029: All code automatically becomes Apache 2.0

Why BSL? We believe in open source but need time-boxed IP protection to build our competitive moat. See our complete explanation: WHY_BSL_FOR_CIRO.md

For full licensing details, see LICENSE.


πŸ”— Links


Built with ❀️ by the CIRO Labs team

Transforming idle compute into decentralized AI infrastructure

About

No description, website, or topics provided.

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages