- Remove executable permissions from configuration files (.editorconfig, .env.example, .gitignore) - Remove executable permissions from documentation files (README.md, LICENSE, SECURITY.md) - Remove executable permissions from web assets (HTML, CSS, JS files) - Remove executable permissions from data files (JSON, SQL, YAML, requirements.txt) - Remove executable permissions from source code files across all apps - Add executable permissions to Python
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.