573aae065b
Some checks failed
API Endpoint Tests / test-api-endpoints (push) Successful in 56s
Blockchain Synchronization Verification / sync-verification (push) Failing after 3s
CLI Tests / test-cli (push) Failing after 5s
Coverage Phase 1 (70% Target) / test-coverage-70 (push) Failing after 19s
Coverage Phase 2 (85% Target) / test-coverage-85 (push) Failing after 18s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Successful in 3s
Cross-Chain Functionality Tests / test-cross-chain-transactions (push) Successful in 4s
Cross-Chain Functionality Tests / test-multi-chain-consensus (push) Successful in 5s
Deploy to Testnet / deploy-testnet (push) Failing after 21s
Documentation Validation / validate-docs (push) Failing after 13s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Integration Tests / test-service-integration (push) Failing after 2s
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Successful in 4s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 14s
Node Failover Simulation / failover-test (push) Successful in 9s
P2P Network Verification / p2p-verification (push) Successful in 5s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 51s
Package Tests / Python package - aitbc-core (push) Failing after 3s
Package Tests / Python package - aitbc-crypto (push) Successful in 22s
Package Tests / Python package - aitbc-sdk (push) Successful in 16s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 21s
Package Tests / JavaScript package - aitbc-token (push) Failing after 18s
Production Tests / Production Integration Tests (push) Failing after 1m9s
Python Tests / test-python (push) Failing after 3s
Security Scanning / security-scan (push) Failing after 41s
Smart Contract Tests / test-solidity (map[name:aitbc-contracts path:contracts]) (push) Failing after 6s
Smart Contract Tests / test-solidity (map[name:aitbc-token path:packages/solidity/aitbc-token]) (push) Failing after 7s
Smart Contract Tests / test-foundry (push) Failing after 20s
Smart Contract Tests / lint-solidity (push) Failing after 4s
Smart Contract Tests / deploy-contracts (push) Failing after 5s
Cross-Chain Functionality Tests / aggregate-results (push) Successful in 2s
Multi-Node Stress Testing / stress-test (push) Successful in 2s
Cross-Node Transaction Testing / transaction-test (push) Successful in 3s
Phase 1: Security fixes - Added CORSMiddleware to marketplace-service with specific origins - Fixed blockchain-node auth to fail closed on JWT errors - Added security regression tests (test_cors_configuration.py, test_dispute_auth.py) Phase 2: Repository cleanup - Removed 51 fix/backup/legacy files - Deleted marketplace-service-debug directory Phase 3.1: Python version constraints - Updated aitbc-crypto and aitbc-sdk with requires-python >=3.13 - Added explicit [tool.poetry].packages declarations Phase 3.2: Agent service DI architecture - Created aitbc-agent-core package with protocols and shared service - Implemented adapters for agent-management and coordinator-api - Created factory functions for gradual migration - Added migration comments to existing integration files Phase 4.1: Auth/utils extraction - Created auth.py module with JWT validation and security utilities - Created utils.py module with common helpers Phase 4.2: Router decomposition - Decomposed router.py into 10 domain modules (58 endpoints) - Created route table snapshot for verification - Preserved router_old.py as reference Phase 5: App shell classification - Documented app shell patterns across services Phase 6: Quality gates - Verified mypy type checking (75% error reduction) - Analyzed logging inconsistencies with structlog migration plan - Removed unused orjson dependency Documentation: - Created comprehensive remediation report - Added architecture documentation for DI pattern - Added quality analysis documents
AITBC Infrastructure Documentation
Last Updated: 2026-03-29
Version: 3.2 (Infrastructure Optimization)
Overview
This section documents the AITBC infrastructure components, runtime architecture, and system management following the latest infrastructure optimization.
🏗️ Recent Infrastructure Updates (March 29, 2026)
✅ Completed Optimizations
-
Runtime Directories: Implemented standard Linux directory structure
/var/lib/aitbc/keystore/- Secure blockchain key storage/var/lib/aitbc/data/- Database files and application data/var/lib/aitbc/logs/- Application logs/etc/aitbc/- Configuration files
-
SystemD Services: Fixed 34+ services with system Python3
- Replaced non-existent venv paths with
/usr/bin/python3 - Updated WorkingDirectory paths to correct locations
- Created missing environment files
- Fixed PYTHONPATH configurations
- Replaced non-existent venv paths with
-
Service Consolidation: Standardized agent services
- Consolidated into
/opt/aitbc/apps/agent-services/ - Consistent hyphenated naming (
agent-*) - Removed duplicate services
- Updated systemd service paths
- Consolidated into
🔧 Infrastructure Components
Core Services
- Coordinator API: Central orchestration (Port 8011)
- Blockchain Node: Core blockchain (Port 8545)
- Exchange API: Trading services (Port 8001)
- Wallet Service: Wallet management (Port 8003)
Agent Services
- Agent Registry: Service discovery and registration
- Agent Coordinator: Task coordination and management
- Agent Protocols: Communication and messaging
- Agent Bridge: Service integration layer
- Agent Compliance: Regulatory monitoring
- Agent Trading: Automated trading
Supporting Services
- GPU Services: Multimodal processing
- Marketplace Services: Enhanced marketplace
- Load Balancer: Geographic distribution
- Explorer: Blockchain explorer
📁 Documentation Structure
Core Infrastructure Files
- Runtime Directories Guide - Standard directory structure
- SystemD Services Guide - Service management
- Security Hardening Guide - Security best practices
Analysis Documents
Deployment Guides
- Codebase Update Summary - Service standardization
- Multimodal Services Deployment - GPU services
🔒 Security Architecture
Keystore Security
- Location:
/var/lib/aitbc/keystore/ - Permissions: 700 (root/aitbc user only)
- Isolation: Separate from application code
- Backup: Included in system backup strategy
Service Security
- User Isolation: Services run with minimal privileges
- Path Security: Sensitive paths properly secured
- Environment Security: Configuration files protected
🚀 Setup and Deployment
Automated Setup
# Complete infrastructure setup
sudo bash <(curl -sSL https://raw.githubusercontent.com/oib/aitbc/main/setup.sh)
Manual Setup
# Clone and setup manually
sudo git clone https://github.com/aitbc/aitbc.git /opt/aitbc
cd /opt/aitbc
sudo ./setup.sh
📊 Service Management
Health Monitoring
# Check all services
/opt/aitbc/scripts/monitoring/health_check.sh
# View logs (new locations)
tail -f /var/lib/aitbc/logs/aitbc-*.log
# SystemD control
systemctl status aitbc-*
systemctl restart aitbc-coordinator-api
Runtime Directory Access
# Check keystore
ls -la /var/lib/aitbc/keystore/
# Check data directory
ls -la /var/lib/aitbc/data/
# Check logs
ls -la /var/lib/aitbc/logs/
🔄 Maintenance Procedures
Regular Tasks
- Log Rotation: Automatic via logrotate
- Service Updates: Controlled systemd updates
- Security Patches: Regular system updates
- Backup Verification: Validate keystore backups
Troubleshooting
- Service Failures: Check journalctl logs
- Path Issues: Verify runtime directories exist
- Permission Issues: Check directory permissions
- Dependency Issues: Verify Python3 packages
Next Steps: Review individual service documentation for specific configuration details.
Category Overview
This section contains all documentation related to infrastructure documentation. The documented files have been automatically converted from completed planning analysis files.
Auto-generated index