Relationship with PUAI
Pumpad introduces a dual-token architecture, designed to separate long-term governance power (PUAD) from rapid utility consumption (PUAI). This model ensures transparency, scalability, and balance between growth and sustainability.
Core Role
Utility, permissions, identity, governance
AI engine access, task execution, burn-on-use
Token Nature
Long-term holding, carries governance
Disposable, no voting rights, short-lived
Supply Model
Fixed: 1B PUAD
Elastic: mint-to-burn
Burn Mechanism
Not designed for regular burning
Auto-burned on each AI/task interaction
Pricing Model
Market-based + DAO adjusted
Usage-driven, dynamic pricing
Access Rights
Unlocks features, plugins, identities
Executes real-time AI and mission logic
🔁 Coordinated Interaction
PUAD unlocks access to premium modules, AI plugin dashboards, and mission tooling.
PUAI fuels real-time use — every AI call (text generation, task logic, model activation) consumes PUAI.
Incentives are hybridized — high-volume plugin devs can earn both PUAD (platform rewards) and PUAI (usage revenue).
Future conversion layer between PUAD → PUAI will allow temporary balance top-up without friction.
✅ Model Advantages
Lowers operational friction for AI services
Prevents platform token dilution via high-frequency use
Creates clear economic signaling: PUAD = rights, PUAI = fuel
Enables parallel growth of governance layer and consumption engine
Last updated