---
name: jic-burn-protocol
description: Explains the JIC-burn protocol (consume, positive-sum payment, flywheel, AIMS/earn). Use when users ask about JIC burn, consume, positive-sum payment, Agent earn, earn.jic.io.
metadata:
  { "openclaw": { "emoji": "🔥" } }
---
# JIC-burn protocol

**One line:** When payment uses **consume** (burn JIC without withdrawing reserves), circulating supply drops, USDC stays in the pool, and **unit price rises for all holders** — **positive-sum payment**, not a zero-sum transfer.

Official page: **https://earn.jic.io**

## Relation to JIC / AIMS

- **AIMS**: math linking reserves and JIC (mint / redeem / consume); JIC-burn highlights **consume** — **supply contraction + reserves retained**.
- **earn.jic.io**: narrative and integration for agents and creators (holding value, services increasing network burn velocity).

## Core formulas (verify on-chain)

```
price = poolBalance(USDC) / totalSupply(JIC)

mint(usdc)   → USDC enters pool, JIC minted (fees may remain in pool)
redeem(jic)  → JIC burned, USDC withdrawn proportionally
consume(jic) → JIC burned, USDC stays in pool → supply down, pool unchanged → unit price up
```

**Intuition:** clients **burn** JIC to pay for your service; they do not **transfer** tokens to you. Your JIC can appreciate via **higher unit price** (not the same as receiving N tokens as payment).

## Flywheel (why burn velocity matters)

- More **consume** for content and services → more supply destroyed → higher unit value for holders.
- Downside floor: if there is no community consume, **redeem** may still apply per contract parameters; upside scales with burn velocity.

## On-chain facts (verify before citing)

- Network: **Base** (chainId `8453`); USDC and vault addresses from official docs / BaseScan.
- Use **deployed, verified** contracts such as `JICVault`; do not invent addresses — point users to **earn.jic.io** or published deployments.

## Boundaries

- This is **mechanism**, not investment advice; price also reflects markets, liquidity, expectations.
- APIs or registration flows not published on earn.jic.io should be described as **planned / illustrative**, not live.

## Links

- https://jic.io — JIC portal  
- https://aims.jic.io — AIMS  
- https://earn.jic.io — JIC-burn / Agent economics