For Developers

Build on AITBC

Join our developer community and help build the future of decentralized AI

Technology Stack

AITBC is built with modern technologies focused on performance and security.

Rust
Go
Python
TypeScript
React
PostgreSQL
Docker
Kubernetes

Getting Started

Ready to contribute? Here's how to get started with AITBC development.

Development Environment Setup

1

Fork & Clone

# Fork the repository on Gitea git clone https://gitea.bubuit.net/YOUR_USERNAME/aitbc.git cd aitbc # Add upstream remote git remote add upstream https://gitea.bubuit.net/oib/aitbc.git
2

Install Dependencies

# Install development dependencies ./scripts/install-dev-deps.sh # Setup pre-commit hooks pre-commit install
3

Build & Run

# Build all components make build # Start development environment make dev-up # Run tests make test
4

Create Your Branch

# Create feature branch git checkout -b feature/your-feature-name # Make your changes... # Commit with proper message git commit -m "feat: add your feature description"
5

Submit PR

# Push to your fork git push origin feature/your-feature-name # Create pull request on Gitea # Fill PR template and submit

Contribution Areas

There are many ways to contribute to AITBC. Find the area that matches your skills!

Core Protocol

  • Consensus mechanism improvements
  • Cryptographic implementations
  • Performance optimizations
  • Security enhancements
  • Sharding implementations

Skills: Rust, Go, Cryptography, Distributed Systems

AI/ML Integration

  • Model optimization
  • ZK proof generation
  • Secure enclaves
  • Privacy-preserving ML
  • Autonomous agents

Skills: Python, TensorFlow, PyTorch, ZK-SNARKs

Developer Tools

  • SDK development
  • CLI tools
  • Testing frameworks
  • Documentation
  • IDE plugins

Skills: TypeScript, Python, Go, Documentation

Frontend & UI

  • Marketplace interface
  • Wallet UI
  • Developer dashboard
  • Mobile apps
  • Design system

Skills: React, TypeScript, CSS, Design

Security

  • Security audits
  • Penetration testing
  • Bug bounty
  • Security tools
  • Threat modeling

Skills: Security, Auditing, Cryptography

Documentation

  • Technical guides
  • Tutorials
  • API docs
  • Blog posts
  • Translations

Skills: Writing, Technical Communication

Development Guidelines

Code Standards

  • Follow language-specific style guides (rustfmt, gofmt, PEP8)
  • Write comprehensive tests for new features
  • Document all public APIs and complex logic
  • Keep pull requests focused and small
  • Use clear and descriptive commit messages

Testing Requirements

# Run all tests make test # Run with coverage make test-coverage # Run integration tests make test-integration # Run benchmarks make benchmark

Code Review Process

  • All changes require review
  • At least one approval needed
  • CI must pass
  • Documentation updated
  • Tests added/updated
Pro Tip: Join our Discord #dev channel for real-time help and discussions!

Bounties & Grants

Get paid to contribute to AITBC!

Open Bounties

  • $500 - Implement REST API rate limiting
  • $750 - Add Python async SDK support
  • $1000 - Optimize ZK proof generation
  • $1500 - Implement cross-chain bridge
  • $2000 - Build mobile wallet app

Research Grants

  • $5000 - Novel consensus mechanisms
  • $7500 - Privacy-preserving ML
  • $10000 - Quantum-resistant cryptography

How to Apply

  1. Check open issues on Gitea
  2. Comment on the issue you want to work on
  3. Submit your solution
  4. Get reviewed by core team
  5. Receive payment in AITBC tokens
New Contributor Bonus: First-time contributors get a 20% bonus on their first bounty!

Join the Community

Developer Channels

  • Discord #dev - General development discussion
  • Discord #core-dev - Core protocol discussions
  • Discord #bounties - Bounty program updates
  • Discord #research - Research discussions

Events & Programs

  • Weekly Dev Calls - Every Tuesday 14:00 UTC
  • Hackathons - Quarterly with prizes
  • Office Hours - Meet the core team
  • Mentorship Program - Learn from experienced devs
  • Top contributors featured on website
  • Monthly contributor rewards
  • Special Discord roles
  • Annual developer summit invitation
  • Swag and merchandise

Developer Resources

Documentation

Tools & SDKs

Development Environment

Learning Resources

Example: Adding a New API Endpoint

// File: coordinator-api/internal/handler/new_endpoint.go package handler import ( "net/http" "github.com/gin-gonic/gin" ) // NewEndpoint handles new feature requests func (h *Handler) NewEndpoint(c *gin.Context) { var req NewEndpointRequest if err := c.ShouldBindJSON(&req); err != nil { c.JSON(http.StatusBadRequest, gin.H{"error": err.Error()}) return } // Validate request if err := req.Validate(); err != nil { c.JSON(http.StatusBadRequest, gin.H{"error": err.Error()}) return } // Process request result, err := h.service.ProcessNewEndpoint(req) if err != nil { c.JSON(http.StatusInternalServerError, gin.H{"error": err.Error()}) return } c.JSON(http.StatusOK, result) }

Test Your Changes

// File: coordinator-api/internal/handler/new_endpoint_test.go package handler import ( "encoding/json" "net/http" "net/http/httptest" "testing" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" ) func TestNewEndpoint(t *testing.T) { // Setup h := setupTestHandler(t) // Test request req := NewEndpointRequest{ Field1: "test", Field2: 123, } // Create HTTP request body, _ := json.Marshal(req) w := httptest.NewRecorder() r := httptest.NewRequest("POST", "/api/v1/new-endpoint", bytes.NewReader(body)) // Execute h.NewEndpoint(w, r) // Assert require.Equal(t, http.StatusOK, w.Code) var response NewEndpointResponse err := json.Unmarshal(w.Body.Bytes(), &response) require.NoError(t, err) assert.Equal(t, "expected_value", response.Result) }

Frequently Asked Questions

General

  • How do I start contributing? - Check our "Getting Started" guide and pick an issue that interests you.
  • Do I need to sign anything? - Yes, you'll need to sign our CLA (Contributor License Agreement).
  • Can I be paid for contributions? - Yes! Check our bounty program or apply for grants.

Technical

  • What's the tech stack? - Rust for blockchain, Go for services, Python for AI, TypeScript for frontend.
  • How do I run tests? - Use `make test` or check specific component documentation.
  • Where can I ask questions? - Discord #dev channel is the best place.

Process

  • How long does PR review take? - Usually 1-3 business days.
  • Can I work on multiple issues? - Yes, but keep PRs focused on single features.
  • What if my PR is rejected? - We'll provide feedback and guidance for resubmission.