Files
aitbc/scripts
AITBC System 1ee2238cc8 feat: implement complete OpenClaw DAO governance system
🏛️ OpenClawDAO Smart Contract Implementation:

Core Governance Contract:
- Enhanced OpenClawDAO with snapshot security and anti-flash-loan protection
- Token-weighted voting with 24-hour TWAS calculation
- Multi-sig protection for critical proposals (emergency/protocol upgrades)
- Agent swarm role integration (Provider/Consumer/Builder/Coordinator)
- Proposal types: Parameter Change, Protocol Upgrade, Treasury, Emergency, Agent Trading, DAO Grants
- Maximum voting power limits (5% per address) and vesting periods

Security Features:
- Snapshot-based voting power capture prevents flash-loan manipulation
- Proposal bonds and challenge mechanisms for proposal validation
- Multi-signature requirements for critical governance actions
- Reputation-based voting weight enhancement for agents
- Emergency pause and recovery mechanisms

Agent Wallet Contract:
- Autonomous agent voting with configurable strategies
- Role-specific voting preferences based on agent type
- Reputation-based voting power bonuses
- Authorized caller management for agent control
- Emergency stop and reactivate functionality
- Autonomous vote execution based on predefined strategies

GPU Staking Contract:
- GPU resource staking with AITBC token collateral
- Reputation-based reward rate calculations
- Utilization-based reward scaling
- Lock period enforcement with flexible durations
- Provider reputation tracking and updates
- Multi-pool support with different reward rates

Deployment & Testing:
- Complete deployment script with system configuration
- Comprehensive test suite covering all major functionality
- Multi-sig setup and initial agent registration
- Snapshot creation and staking pool initialization
- Test report generation with detailed results

🔐 Security Implementation:
- Anti-flash-loan protection through snapshot voting
- Multi-layer security (proposal bonds, challenges, multi-sig)
- Reputation-based access control and voting enhancement
- Emergency mechanisms for system recovery
- Comprehensive input validation and access controls

📊 Governance Features:
- 6 proposal types covering all governance scenarios
- 4 agent swarm roles with specialized voting preferences
- Token-weighted voting with reputation bonuses
- 7-day voting period with 1-day delay
- 4% quorum requirement and 1000 AITBC proposal threshold

🚀 Ready for deployment and integration with AITBC ecosystem
2026-03-18 20:32:44 +01:00
..
```
2026-03-08 12:16:01 +01:00
```
2026-03-08 12:16:01 +01:00
```
2026-03-08 12:16:01 +01:00
```
2026-03-08 12:16:01 +01:00
```
2026-03-08 12:16:01 +01:00
```
2026-03-08 12:16:01 +01:00

AITBC Development Environment Scripts

This directory contains scripts for managing the AITBC development environment, including incus containers and systemd services.

📋 Available Scripts

🔧 start-aitbc-dev.sh

Starts incus containers and AITBC systemd services on localhost.

Features:

  • Starts incus containers: aitbc and aitbc1
  • Starts all local systemd services matching aitbc-*
  • Checks service health and port status
  • Tests health endpoints
  • Provides colored output and status reporting

Usage:

./scripts/start-aitbc-dev.sh

🛑 stop-aitbc-dev.sh

Stops incus containers and AITBC systemd services on localhost.

Features:

  • Stops incus containers: aitbc and aitbc1
  • Stops all local systemd services matching aitbc-*
  • Verifies services are stopped
  • Provides colored output and status reporting

Usage:

./scripts/stop-aitbc-dev.sh

🚀 start-aitbc-full.sh

Comprehensive startup script for the complete AITBC development environment.

Features:

  • Starts incus containers: aitbc and aitbc1
  • Starts services inside containers
  • Starts all local systemd services matching aitbc-*
  • Tests connectivity to container services
  • Provides detailed status reporting
  • Shows container IP addresses
  • Tests health endpoints

Services Started:

  • Local Services: All aitbc-* systemd services
  • Container Services:
    • aitbc-coordinator-api
    • aitbc-wallet-daemon
    • aitbc-blockchain-node

Usage:

./scripts/start-aitbc-full.sh

🎯 Prerequisites

Required Commands:

  • incus - Container management
  • systemctl - Systemd service management
  • curl - Health endpoint testing
  • netstat - Port checking

Required Containers:

The scripts expect these incus containers to exist:

  • aitbc
  • aitbc1

Required Services:

The scripts look for systemd services matching the pattern aitbc-*.

📊 Service Ports

Port Service Description
8001 Coordinator API Main API service
8002 Wallet Daemon Wallet management
8003 Blockchain RPC Blockchain node RPC
8000 Coordinator API (alt) Alternative API
8081 Blockchain Node 1 Blockchain instance
8082 Blockchain Node 2 Blockchain instance
8006 Coordinator API (dev) Development API

🔍 Health Endpoints

The scripts test these health endpoints:

  • http://localhost:8001/health - Coordinator API
  • http://localhost:8002/health - Wallet Daemon
  • http://localhost:8003/health - Blockchain RPC

📝 Output Examples

Success Output:

[INFO] Starting AITBC Development Environment...
[INFO] Starting incus containers...
[SUCCESS] Container aitbc started successfully
[SUCCESS] Container aitbc1 started successfully
[INFO] Starting AITBC systemd services on localhost...
[SUCCESS] Service aitbc-coordinator-api started successfully
[SUCCESS] Service aitbc-wallet-daemon started successfully
[INFO] Checking service status...
[SUCCESS] aitbc-coordinator-api: RUNNING
[SUCCESS] aitbc-wallet-daemon: RUNNING
[SUCCESS] AITBC Development Environment startup complete!

Service Status:

[INFO] Checking AITBC service ports...
[SUCCESS] Coordinator API (port 8001): RUNNING
[SUCCESS] Wallet Daemon (port 8002): RUNNING
[WARNING] Blockchain RPC (port 8003): NOT RUNNING

🛠️ Troubleshooting

Common Issues:

  1. Container not found:

    [ERROR] Container aitbc not found. Please create it first.
    

    Solution: Create the incus containers first:

    incus launch images:ubuntu/22.04 aitbc
    incus launch images:ubuntu/22.04 aitbc1
    
  2. Service not found:

    [WARNING] No AITBC services found on localhost
    

    Solution: Install AITBC services or check if they're named correctly.

  3. Port already in use:

    [WARNING] Service aitbc-coordinator-api is already running
    

    Solution: This is normal - the script detects already running services.

  4. Permission denied:

    [ERROR] Failed to start service aitbc-coordinator-api
    

    Solution: Run with sudo or check user permissions.

Debug Commands:

# Check all AITBC services
systemctl list-units | grep aitbc-

# Check container status
incus list

# View service logs
journalctl -f -u aitbc-coordinator-api

# View container logs
incus exec aitbc -- journalctl -f -u aitbc-coordinator-api

# Check port usage
netstat -tlnp | grep :800

🔄 Workflow

Development Setup:

  1. Create incus containers (if not exists)
  2. Install AITBC services in containers
  3. Install AITBC systemd services locally
  4. Run ./scripts/start-aitbc-full.sh

Daily Development:

  1. ./scripts/start-aitbc-full.sh - Start everything
  2. Work on AITBC development
  3. ./scripts/stop-aitbc-dev.sh - Stop when done

Testing:

  1. Start services with scripts
  2. Test health endpoints
  3. Check logs for issues
  4. Stop services when finished

📚 Additional Information

  • Container IPs: Scripts show container IP addresses for direct access
  • Health Checks: Automatic health endpoint testing
  • Service Status: Real-time status reporting
  • Error Handling: Graceful error handling with informative messages

🎯 Best Practices

  1. Use the full script for complete environment setup
  2. Check the output for any warnings or errors
  3. Monitor logs when troubleshooting issues
  4. Stop services when not in use to conserve resources
  5. Run scripts from the project root for proper path resolution