USDAI
  • Introduction
  • Why Compute-Backed?
  • Vision & Purpose
  • GPU.NET Ecosystem
    • What is GPU.NET?
    • Key Components of GPU.NET
    • GPU.NET’s Mission
    • USDAI’s Role in the Ecosystem
  • USDAI Mechanics
    • How USDAI Works
    • Pegging Mechanism
    • Collateralization
    • Issuance and Redemption
    • Stability Mechanisms
    • Why It Works
  • USDAI Architecture
    • Architecture
    • Supported Blockchains
    • Interoperability
    • Smart Contracts
    • Security Features
  • Use Cases
    • USDAI Applications
    • AI/ML Workload Payments
    • DeFi Integrations
    • Compute Reservations
    • Broader Implications
  • Acquiring USDAI
    • How to Acquire USDAI
    • Using USDAI
    • Developer Integration
  • Governance and Community
    • Governance
    • Roadmap
    • FAQ
    • Support & Community
Powered by GitBook
On this page
  1. USDAI Mechanics

Stability Mechanisms

USDAI’s $1 compute peg is maintained through three interlocking stability mechanisms, ensuring reliability even under volatile conditions.

1. Dynamic Pricing Oracles

  • Role: These oracles provide real-time feeds from GPU.NET’s marketplace, tracking the cost of GPU compute across providers. They incorporate factors like GPU performance, energy costs, and regional availability.

  • Implementation: Oracles are decentralized, pulling data from multiple sources (e.g., Dapp.gpu.net, external compute markets) and aggregating it via a median-based consensus to prevent manipulation.

  • Impact: If compute costs rise to $1.10/hour, oracles signal smart contracts to adjust USDAI’s backing, maintaining the peg by recalibrating the collateral ratio.

2. Algorithmic Supply Adjustments

  • Role: Smart contracts automatically mint or burn USDAI to balance supply with demand, preventing deviations from the peg.

  • Process:

    • If USDAI trades above $1 (e.g., $1.05), excess demand triggers minting to increase supply, pushing the price down.

    • If USDAI falls below $1 (e.g., $0.95), excess supply triggers burning to reduce circulation, lifting the price back to $1.

  • Example: During an AI boom, demand for USDAI surges. The system mints 10,000 additional USDAI, backed by newly contributed computecredits, stabilizing the market.

3. Proof-of-Compute (PoC)

  • Role: Validators on Grid.gpu.net use PoC to confirm compute availability, ensuring USDAI is never over-issued or under-collateralized.

  • Mechanism: Providers submit cryptographic proofs of their GPU capacity (e.g., benchmark results, uptime logs), which validators verify before credits are tokenized. This prevents fraudulent collateral claims.

  • Impact: PoC ties USDAI’s supply to real, usable compute power, reinforcing trust in its backing and preventing systemic risks.

PreviousIssuance and RedemptionNextWhy It Works

Last updated 3 months ago