1ee2238cc8
🏛️ 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
Coordinator API
Purpose & Scope
FastAPI service that accepts client compute jobs, matches miners, and tracks job lifecycle for the AITBC network.
Marketplace Extensions
Stage 2 introduces public marketplace endpoints exposed under /v1/marketplace:
GET /v1/marketplace/offers– list available provider offers (filterable by status).GET /v1/marketplace/stats– aggregated supply/demand metrics surfaced in the marketplace web dashboard.POST /v1/marketplace/bids– accept bid submissions for matching (mock-friendly; returns202 Accepted).
These endpoints serve the apps/marketplace-web/ dashboard via VITE_MARKETPLACE_DATA_MODE=live.
Explorer Endpoints
The coordinator now exposes read-only explorer data under /v1/explorer for apps/explorer-web/ live mode:
GET /v1/explorer/blocks– block summaries derived from recent job activity.GET /v1/explorer/transactions– transaction-like records for coordinator jobs.GET /v1/explorer/addresses– aggregated address activity and balances.GET /v1/explorer/receipts– latest job receipts (filterable byjob_id).
Set VITE_DATA_MODE=live and VITE_COORDINATOR_API in the explorer web app to consume these APIs.
Development Setup
- Create a virtual environment in
apps/coordinator-api/.venv. - Install dependencies listed in
pyproject.tomlonce added. - Run the FastAPI app via
uvicorn app.main:app --reload.
Configuration
Expects environment variables defined in .env (see docs/bootstrap/coordinator_api.md).
Signed receipts (optional)
- Generate an Ed25519 key:
python - <<'PY' from nacl.signing import SigningKey sk = SigningKey.generate() print(sk.encode().hex()) PY - Set
RECEIPT_SIGNING_KEY_HEXin the.envfile to the printed hex string to enable signed receipts returned by/v1/miners/{job_id}/resultand retrievable via/v1/jobs/{job_id}/receipt. - Receipt history is available at
/v1/jobs/{job_id}/receipts(requires client API key) and returns all stored signed payloads. - To enable coordinator attestations, set
RECEIPT_ATTESTATION_KEY_HEXto a separate Ed25519 private key; responses include anattestationsarray alongside the miner signature. - Clients can verify
signatureobjects using theaitbc_cryptopackage (seeprotocols/receipts/spec.md).
Systemd
Service name: aitbc-coordinator-api (to be defined under configs/systemd/).