AIPG Token Factory: Build Your Own AI Network on Base

The AIPG Token Factory is a toolkit for developers who want to launch their own networks and tokens on top of AIPG. Instead of building AI infrastructure from scratch, you deploy a token that taps into the models AIPG already serves — and build your own product, economy, and community around it.

Your token isn’t just a ticker—it’s designed to be a key to the AIPG network.

The Problem

Launching a token today means:

• Deploying a generic ERC-20 with no utility
• Building your own infrastructure from scratch
• Convincing users your token does something
• No connection to real services or compute

Most tokens ship with a promise and a roadmap. Yours ships with working AI infrastructure.

What You Get

When you deploy through AIPG’s Token Factory, your token is designed to wire into the AIPG network so you can launch your own service on top of it:

Your token becomes a compute credit for real AI services.

How It Works

1. Deploy Your Token

Choose a template and configure:

Token Name:       MyAIToken
Symbol:           MAIT
Supply:           100,000,000
Compute Ratio:    1 MAIT = 0.1 AIPG worth of compute
Revenue Split:    80% to your treasury, 20% to AIPG network

The factory deploys your token with built-in hooks to the AIPG Grid.

2. Users Spend Your Token

When someone uses your token for AI generation:

┌─────────────────────────────────────────────────────────────┐
│  User pays 10 MAIT for image generation                     │
├─────────────────────────────────────────────────────────────┤
│  → MAIT is burned or sent to your treasury (configurable)   │
│  → Grid receives job request with payment proof             │
│  → Worker generates image using registered model            │
│  → Result anchored on-chain with Merkle proof               │
│  → User receives deterministic, verifiable output           │
└─────────────────────────────────────────────────────────────┘

3. Revenue Flows Back

Every job creates value:

• Your Treasury: Receives the MAIT spent (or burn reduces supply)
• GPU Workers: Earn USDC + AIPG for compute work
• AIPG Network: Protocol fee sustains infrastructure
• Your Holders: Token has real utility = real demand

Token Templates

Compute Credit Token

For projects that want a dedicated AI compute currency.

• Users buy your token to access AI features
• Token is burned on use (deflationary)
• Price discovery based on compute demand
• Example: An AI art platform with its own economy

Access Token

For projects that want subscription-style access.

• Holding X tokens unlocks AI features
• No burning—just holding requirement
• Tiered access based on balance
• Example: AI tool suite with membership tiers

Hybrid Token

For projects that want staking + compute.

• Stake tokens to earn compute credits
• Unstaked tokens can pay for compute directly
• Dual utility: passive yield + active use
• Example: AI agent that rewards long-term holders

Agent Token

For autonomous AI agents with on-chain treasuries.

• Agent controls its own wallet
• Earns revenue from services
• Spends on compute to fulfill tasks
• Example: Trading bot, content generator, research agent

Integration Architecture

Your token is designed to plug into AIPG’s on-chain contracts:

┌────────────────────────────────────────────────────────────────────┐
│                        YOUR TOKEN                                  │
│  (ERC-20 deployed via Token Factory)                               │
└─────────────────────────────┬──────────────────────────────────────┘
                              │
                              ▼
┌────────────────────────────────────────────────────────────────────┐
│                     PAYMENT ROUTER                                 │
│  Converts your token → compute credits                             │
│  Handles burns, treasury splits, revenue share                     │
└─────────────────────────────┬──────────────────────────────────────┘
                              │
                              ▼
┌────────────────────────────────────────────────────────────────────┐
│                    AIPG GRID (Diamond Proxy)                       │
│  0x79F39f2a0eA476f53994812e6a8f3C8CFe08c609                        │
├────────────────────────────────────────────────────────────────────┤
│                                                                    │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐  ┌────────────┐ │
│  │ ModelVault  │  │ RecipeVault │  │  JobAnchor  │  │  Worker    │ │
│  │             │  │             │  │             │  │  Registry  │ │
│  │ open models │  │ Workflows   │  │ Merkle      │  │            │ │
│  │ registered  │  │ stored      │  │ proofs      │  │ GPU nodes  │ │
│  └─────────────┘  └─────────────┘  └─────────────┘  └────────────┘ │
│                                                                    │
└────────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌────────────────────────────────────────────────────────────────────┐
│                      GPU WORKER NETWORK                            │
│  GPU nodes running image, video, and LLM models                    │
│  Bonded with AIPG stake, slashable for misbehavior                 │
└────────────────────────────────────────────────────────────────────┘

Technical Details

Token Contract

Factory-deployed tokens include:

interface IFactoryToken {
    // Standard ERC-20
    function transfer(address to, uint256 amount) external returns (bool);
    function approve(address spender, uint256 amount) external returns (bool);
 
    // Compute integration
    function computeBalance(address user) external view returns (uint256);
    function spendForCompute(uint256 amount, bytes32 jobId) external;
 
    // Revenue tracking
    function totalComputeSpent() external view returns (uint256);
    function totalRevenue() external view returns (uint256);
 
    // Factory metadata
    function computeRatio() external view returns (uint256);
    function revenueRecipient() external view returns (address);
}

Payment Flow

When a user spends your token for AI compute:

1. Authorization: User approves PaymentRouter for their tokens
2. Job Submission: User calls submitJob(modelId, recipeId, params, paymentToken, amount)
3. Payment Processing: Router converts token amount to compute units
4. Token Handling: Based on config—burned, sent to treasury, or split
5. Job Execution: Grid assigns job to bonded worker
6. Completion: Worker submits result, anchored via Merkle root
7. Settlement: Worker earns USDC + AIPG, your treasury earns revenue share

Supported Models

Your token holders get access to all registered models:

Models are registered in ModelVault with full metadata: VRAM requirements, supported features, constraints.

Workflows

Recipes stored in RecipeVault define complete ComfyUI pipelines:

• Multi-model compositions
• ControlNet + LoRA stacking
• Post-processing chains
• Deterministic reproduction via stored parameters

Your users can run any public recipe or create private ones.

Economics

For Token Creators

For Token Holders

Revenue Split Example

User pays 100 MYTOKEN for an image generation:

┌─────────────────────────────────────────┐
│ 100 MYTOKEN paid                        │
├─────────────────────────────────────────┤
│ → 80 MYTOKEN to your treasury           │
│ → 10 MYTOKEN burned (supply reduction)  │
│ → 10 MYTOKEN protocol fee (buys AIPG)   │
├─────────────────────────────────────────┤
│ Meanwhile:                              │
│ → GPU worker earns USDC + AIPG for job  │
│ → Job anchored on-chain forever         │
│ → User gets deterministic image         │
└─────────────────────────────────────────┘

Deployment Flow

Step 1: Configure

# Via CLI or web interface
aipg-factory create \
  --name "MyAIToken" \
  --symbol "MAIT" \
  --supply 100000000 \
  --compute-ratio 0.1 \
  --burn-percent 10 \
  --treasury 0xYourAddress \
  --revenue-split 80

Step 2: Deploy

Factory deploys:

• Your ERC-20 token contract
• Payment routing configuration
• Revenue split settings
• Grid access permissions

Step 3: Integrate

import { ethers } from 'ethers';
 
// Connect to your factory token
const token = new ethers.Contract(tokenAddress, factoryABI, signer);
 
// User spends token for AI compute
await token.spendForCompute(
  ethers.parseEther('10'),  // 10 MYTOKEN
  jobId                      // bytes32 job identifier
);
 
// Check job on-chain
const job = await grid.getJob(jobId);
console.log(job.status, job.merkleProof);

For generation via the API, users can also call the Grid Streaming API directly:

curl -N https://api.aipowergrid.io/v1/chat/completions \
  -H "Authorization: Bearer YOUR_KEY" \
  -d '{"model":"gpt-oss-120b","messages":[{"role":"user","content":"Hello"}],"stream":true}'

Step 4: Launch

• Distribute tokens to users
• They can immediately use for AI compute
• Revenue flows to your treasury
• Monitor usage via Grid events

Use Cases

AI Art Platform

Launch a token for your generative art community:

• Artists pay with your token to create
• NFT minting with on-chain provenance
• Deflationary tokenomics via burn-on-mint
• Revenue funds community grants

AI Agent Network

Deploy tokens for autonomous agents:

• Each agent has its own token treasury
• Agents earn by providing services
• Spend tokens on compute to fulfill tasks
• Transparent on-chain economics

AI Tool Suite

Subscription access to AI tools:

• Hold tokens for tiered access
• No per-use fees for holders
• Staking unlocks premium features
• Token buybacks from revenue

Game Economy

In-game currency with AI generation:

• Generate game assets with tokens
• Verifiable scarcity via on-chain anchoring
• Player-owned economy
• AI NPCs powered by compute spending

Security

Inherited from AIPG

Your token benefits from AIPG’s production infrastructure:

• Audited Contracts: Core Grid contracts reviewed
• Access Control: Role-based permissions throughout
• Reentrancy Guards: All state changes protected
• Pausable: Emergency stops on all contracts
• Bonded Workers: GPU nodes stake AIPG, slashable

Factory-Specific

• Immutable Config: Core parameters locked at deploy
• Revenue Routing: Splits handled by smart contracts (trust-minimized; see roadmap for status)
• Rate Limits: Configurable spam protection
• Allowlists: Optional restricted access

Roadmap

Get Started

The Token Factory is under active development. To get early access or discuss your project:

• Discord: Join the community
• GitHub: github.com/aipowergrid
• Twitter: @aipowergrid

FAQ

Q: Do I need AIPG to launch a token? A: No. You deploy your own token. AIPG is used internally for worker rewards, but your users only interact with your token.

Q: What chains are supported? A: Base (mainnet) initially. Other L2s may be added based on demand.

Q: Can I migrate an existing token? A: Yes. We can add compute hooks to existing ERC-20s via wrapper contracts.

Q: What’s the cost to deploy? A: Gas costs on Base (~$1-5) plus a one-time factory fee (TBD, likely small AIPG amount).

Q: How do workers get paid? A: Workers receive USDC + AIPG (~50/50 target). The payment router handles conversion from your token.

Q: Can I run my own workers? A: Yes. Register your GPUs in WorkerRegistry, bond AIPG, and earn from jobs paid in any factory token.