Files
aitbc/docs/development/7_payments-receipts.md
aitbc 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
feat: add SQLCipher database encryption support and consolidate agent documentation
- 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
2026-05-03 12:00:38 +02:00

4.2 KiB
Raw Permalink Blame History

Payments and Receipts

This guide explains how payments work on the AITBC network and how to understand your receipts.

Payment Flow

Client submits job → Job processed by miner → Receipt generated → Payment settled

Step-by-Step

  1. Job Submission: You submit a job with your prompt and parameters
  2. Miner Selection: The Coordinator assigns your job to an available miner
  3. Processing: The miner executes your job using their GPU
  4. Receipt Creation: A cryptographic receipt is generated proving work completion
  5. Settlement: AITBC tokens are transferred from client to miner

Understanding Receipts

Every completed job generates a receipt containing:

Field Description
receipt_id Unique identifier for this receipt
job_id The job this receipt is for
provider Miner address who processed the job
client Your address (who requested the job)
units Compute units consumed (e.g., GPU seconds)
price Amount paid in AITBC tokens
model AI model used
started_at When processing began
completed_at When processing finished
signature Cryptographic proof of authenticity

Example Receipt

{
  "receipt_id": "rcpt-20260124-001234",
  "job_id": "job-abc123",
  "provider": "ait1miner...",
  "client": "ait1client...",
  "units": 2.5,
  "unit_type": "gpu_seconds",
  "price": 5.0,
  "model": "llama3.2",
  "started_at": 1737730800,
  "completed_at": 1737730803,
  "signature": {
    "alg": "Ed25519",
    "key_id": "miner-ed25519-2026-01",
    "sig": "Fql0..."
  }
}

Viewing Your Receipts

Explorer

Visit Explorer → Receipts to see:

  • All recent receipts on the network
  • Filter by your address to see your history
  • Click any receipt for full details

CLI

# List your receipts
./aitbc-cli.sh receipts

# Get specific receipt
./aitbc-cli.sh receipt <receipt_id>

API

curl https://aitbc.bubuit.net/api/v1/receipts?client=<your_address>

Pricing

How Pricing Works

  • Jobs are priced in compute units (typically GPU seconds)
  • Each model has a base rate per compute unit
  • Final price = units × rate

Current Rates

Model Rate (AITBC/unit) Typical Job Cost
llama3.2 2.0 2-10 AITBC
llama3.2:1b 0.5 0.5-2 AITBC
codellama 2.5 3-15 AITBC
stable-diffusion 5.0 10-50 AITBC

Rates may vary based on network demand and miner availability.

Getting AITBC Tokens

Via Exchange

  1. Visit Trade Exchange
  2. Create an account or connect wallet
  3. Send Bitcoin to your deposit address
  4. Receive AITBC at current exchange rate (1 BTC = 100,000 AITBC)

See Bitcoin Wallet Setup for detailed instructions.

Via Mining

Earn AITBC by providing GPU compute:

Verifying Receipts

Receipts are cryptographically signed to ensure authenticity.

Signature Verification

from aitbc_crypto import verify_receipt

receipt = get_receipt("rcpt-20260124-001234")
is_valid = verify_receipt(receipt)
print(f"Receipt valid: {is_valid}")

On-Chain Verification

Receipts can be anchored on-chain for permanent proof:

Payment Disputes

If you believe a payment was incorrect:

  1. Check the receipt - Verify units and price match expectations
  2. Compare to job output - Ensure you received the expected result
  3. Contact support - If discrepancy exists, report via the platform

Best Practices

  1. Monitor your balance - Check before submitting large jobs
  2. Set spending limits - Use API keys with rate limits
  3. Keep receipts - Download important receipts for records
  4. Verify signatures - For high-value transactions, verify cryptographically

Next Steps