Tokenomics view
See Tokenomics → wBINI Cap Rule for why pool topology matters and how the $240M ceiling shapes liquidity flow.
Three pool types
BaiDEX supports three canonical pool configurations:
Other pools (e.g., direct Agent-Token-to-Agent-Token) are technically possible but discouraged by the topology.
Topology
wBINI / USBI (anchor pool)
One canonical pool, capped at $12M TVL. The wBINI side caps at 0.12 reference price). The USBI side mirrors it at $6M to keep the pool balanced. The anchor pool serves as:- The price oracle for wBINI vs USBI
- The trading venue for users who want to convert between wBINI and USBI directly
- The reference benchmark for off-chain valuations of BINI
USBI / Agent Token (growth pools)
One per Agent Token, auto-listed when the token is spawned via AgentT Launchpad. Why USBI as the pair side:- USBI is a sandbox stablecoin → low volatility relative to fiat
- USBI scales with user XP entitlement → there’s always more USBI to LP as user count grows
- No cap on USBI side → these pools can grow large
wBINI / Agent Token (premium pools)
Optional pools for Agent Tokens that want direct BINI exposure (and the volatility / opportunity that comes with it). Why these are limited:- wBINI total supply is capped at 50M (5% of BINI total)
- The anchor pool consumes a chunk of available wBINI
- Remaining wBINI is split across premium pools
- Existing wBINI holders to provide the wBINI side
- Treasury seeding (rare — usually for high-priority projects)
Liquidity dynamics
See Tokenomics → Simulation for projections.
Permissionless or not?
Worker per pool
Every Agent Token pool has a Worker assigned (from Agent Hive). The Worker provides a management layer on top of the V3 mechanics:- Tracks pool depth
- Reacts to Scout signals (e.g., new launches, volume spikes)
- Receives strategy from Queens
- Logs all actions on-chain
Related
Liquidity
LP rules and bootstrapping
wBINI Cap Rule
Why the topology
AgentT Launchpad
Spawn auto-creates a pool
Agent Hive
Workers managing each pool
