19d415a235
Some checks failed
Blockchain Synchronization Verification / sync-verification (push) Failing after 3s
CLI Tests / test-cli (push) Failing after 3s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Successful in 2s
Cross-Chain Functionality Tests / test-cross-chain-transactions (push) Successful in 3s
Cross-Chain Functionality Tests / test-cross-chain-bridge (push) Has been skipped
Cross-Chain Functionality Tests / test-multi-chain-consensus (push) Successful in 2s
Cross-Chain Functionality Tests / aggregate-results (push) Has been skipped
Deploy to Testnet / deploy-testnet (push) Successful in 1m12s
Documentation Validation / validate-docs (push) Failing after 8s
Documentation Validation / validate-policies-strict (push) Successful in 3s
Integration Tests / test-service-integration (push) Successful in 2m6s
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Successful in 2s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 4s
P2P Network Verification / p2p-verification (push) Successful in 4s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 32s
Package Tests / Python package - aitbc-core (push) Successful in 14s
Package Tests / Python package - aitbc-crypto (push) Successful in 12s
Package Tests / Python package - aitbc-sdk (push) Successful in 9s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 8s
Package Tests / JavaScript package - aitbc-token (push) Successful in 17s
Python Tests / test-python (push) Successful in 15s
Security Scanning / security-scan (push) Successful in 27s
Node Failover Simulation / failover-test (push) Successful in 7s
Multi-Node Stress Testing / stress-test (push) Successful in 6s
Cross-Node Transaction Testing / transaction-test (push) Successful in 4s
- Add SQLCipher encryption for ait-mainnet database with configurable flag - Add db_encryption_enabled and db_encryption_key_path config settings - Implement encryption key loading and PRAGMA key setup via connection events - Add shutdown_db function for proper database cleanup - Export middleware classes in aitbc/__init__.py - Fix import path in sync.py for settings - Remove duplicate agent documentation from docs
2.2 KiB
2.2 KiB
title, summary
| title | summary |
|---|---|
| GPU Monetization Guide | How to register GPUs, set pricing, and receive payouts on AITBC. |
GPU Monetization Guide
Overview
This guide walks providers through registering GPUs, choosing pricing strategies, and understanding the payout flow for AITBC marketplace earnings.
Prerequisites
- AITBC CLI installed locally:
pip install -e ./cli - Account initialized:
aitbc init - Network connectivity to the coordinator API
- GPU details ready (model, memory, CUDA version, base price)
Step 1: Register Your GPU
aitbc marketplace gpu register \
--name "My-GPU" \
--memory 24 \
--cuda-version 12.1 \
--base-price 0.05
- Use
--regionto target a specific market (e.g.,--region us-west). - Verify registration:
aitbc marketplace gpu list --region us-west.
Step 2: Choose Pricing Strategy
- Market Balance (default): Stable earnings with demand-based adjustments.
- Peak Maximizer: Higher rates during peak hours/regions.
- Utilization Guard: Keeps GPU booked; lowers price when idle.
- Update pricing strategy:
aitbc marketplace gpu update --gpu-id <id> --strategy <name>.
Step 3: Monitor & Optimize
aitbc marketplace earnings --gpu-id <id>
aitbc marketplace status --gpu-id <id>
- Track utilization, bookings, and realized rates.
- Adjust
--base-priceor strategy based on demand.
Payout Flow (Mermaid)
sequenceDiagram
participant Provider
participant CLI
participant Coordinator
participant Escrow
participant Wallet
Provider->>CLI: Register GPU + pricing
CLI->>Coordinator: Submit registration & terms
Coordinator->>Escrow: Hold booking funds
Provider->>Coordinator: Deliver compute
Coordinator->>Escrow: Confirm completion
Escrow->>Wallet: Release payout to provider
Best Practices
- Start with Market Balance; adjust after 48h of data.
- Set
--regionto match your lowest-latency buyers. - Update CLI regularly for the latest pricing features.
- Keep GPUs online during peak windows (local 9 AM – 9 PM) for higher fill rates.
Troubleshooting
- No bookings? Lower
--base-priceor switch to Utilization Guard. - Low earnings? Check latency/region alignment and ensure GPU is online.
- Command help:
aitbc marketplace gpu --help.