Keyboard shortcuts

Press โ† or โ†’ to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

๐Ÿค Contribute & Participate: Build Ciro Network Together

From Factory Floor to Open Source: Ciro is Community-Powered

Ciro Network is more than codeโ€”it's a movement. Whether you're a developer, researcher, writer, tester, or just curious, you belong here. Every contribution, big or small, helps shape the future of decentralized compute.


๐ŸŒŸ Ways to Contribute

  • Code: Smart contracts, node software, desktop apps, backend services
  • Documentation: Guides, tutorials, API docs, technical specs
  • Testing: Try new features, report bugs, improve reliability
  • Research: Distributed systems, DePIN, GPU optimization
  • Community: Answer questions, welcome newcomers, share ideas

๐Ÿš€ Getting Started

  1. Fork & Clone:
    • Fork the repo on GitHub, then clone your fork
    • Add the original repo as upstream for updates
  2. Set Up Dev Environment:
    • Use DevContainers or follow our setup guide
  3. Create a Feature Branch:
    • Use clear, descriptive branch names (e.g., feature/your-feature)

๐Ÿ› ๏ธ Contribution Workflow

  • Code Standards: Follow our Code Standards for Rust, Cairo, JS/TS, etc.
  • Security: Review our Security Guidelines. Validate inputs, avoid secrets, handle errors, audit dependencies.
  • Testing: Include unit, integration, and security tests. See our Testing Guide.
  • Documentation: Update READMEs, add inline docs, and keep user guides current. See Documentation Standards.
  • Pull Requests:
    • Use our PR template
    • Clear, descriptive commit messages (Conventional Commits)
    • Link related issues, provide screenshots for UI changes
    • All PRs require review and must pass CI/CD

๐Ÿ› Reporting Bugs & Requesting Features

  • Bugs: Use our Bug Report Guide. Include environment, steps, expected/actual behavior, and logs/screenshots.
  • Features: Use our Feature Request Guide. Explain the problem, your solution, and alternatives.
  • Security: For vulnerabilities, email security@ciro.ai (do not open a public issue).

๐Ÿ’ฌ Community Guidelines

  • Be welcoming: We value every contributor, regardless of background or experience.
  • Respectful collaboration: Disagree constructively, help others, and celebrate wins together.
  • Code of Conduct: See our Community Guidelines.

๐Ÿ“š Learn More & Dive Deeper


Ciro Network is built by people like you. Your ideas, your code, your questionsโ€”they all matter. Welcome to the team!