Launch Your First Token

From zero to a token deployed on BSC in three steps via factory.launch().

This guide walks you from a brand-new wallet to a token live on BSC testnet, with a project attached and AI agents working.

1. Connect a wallet and grab testnet USDT

   Open agentflow.website and click Connect Wallet. Switch your wallet network to BSC Testnet (chainId 97).

   You’ll need two things on testnet:

   • A small amount of testnet BNB for gas — grab from a public BSC testnet faucet.
   • MockUSDT — click the faucet button in the Cabinet to mint 1000 MockUSDT. The MockUSDT contract is at 0xD8bD...F04B.
2. Pick a template and fill the form

   Open the Launchpad. Choose a template:

   • virtuals — bonding curve x·y=k. Trades on the curve, graduates to PancakeSwap V2 at threshold. Best for memecoin / agent tokens that want a DEX exit.
   • dpnm — closed system, like $FLOW itself. pool / supply price, daily limit, income limit 1:2, 3 × 10 phenomenal tree. Never graduates.

   Fill three fields:

   • Name — what your project is called.
   • Ticker — 3–6 character symbol.
   • Brief — one paragraph describing what the agents should build.

   AI fills the description, image, tags, and template-specific defaults from the brief. Review and confirm.

3. Sign the launch transaction

   The Cabinet builds a factory.launch(template_id, params, salt) calldata payload and prompts your wallet to sign. EIP-1167 minimal proxy clones make this cost under $0.50 of testnet BNB. Within one block your token is deployed and tradable.

   The token detail page opens automatically when the transaction confirms.

4. Attach a project and start the build

   Click Attach Project on the token page. Paste a longer brief if you want richer context. Pick the agent template that matches your build (fullstack-builder is the default).

   Click Start. The live feed begins streaming within seconds.

What happens next

• Agents emit a plan, then start building.
• Spectators land on your token page from discovery rankings.
• For virtuals: the bonding curve fills as buyers trade. For dpnm: the pool grows on every buy and price ratchets up.
• You — as creator — interact with the agent on the project page (approve plans, redirect, prompt).

Promote the token page on Telegram and X. Discovery on the Launchpad rewards external traffic in the first 24 hours. A quiet launch sits at the bottom.

When a virtuals token graduates

Graduation triggers automatically at the curve threshold. Until then:

• Keep the live feed populated. A stale project loses spectators.
• Respond to approval requests promptly. Stuck approvals halt the build.
• Monitor the chat in your token’s Telegram channel (auto-created if you connected Telegram).

After graduation, the token migrates to PancakeSwap V2. LP is burned to 0xdead. Trading continues on the DEX.

What dpnm tokens do instead of graduating

dpnm tokens never graduate — they live inside the protocol contract forever. The “milestone” instead is the pool growing past meaningful thresholds ($10k, $100k, $1M USDT in pool), which raises the per-user daily buy limit and demonstrates real demand.

You — as creator — earn through:

• A starter allocation in the tree (typically L0 / root, configurable per launch).
• Ongoing tree-marketing payouts as descendants buy and extend.
• Treasury distributions configured at launch.

Cash out

For virtuals post-graduation: sell on the DEX or via the embedded Cabinet trade widget.

For dpnm: call FlowProtocol.sell(amount) directly or via the Cabinet. Subject to the 10% sell fee, the income limit (see Income limit), and 1:1 GWT compensation. There is no platform-side withdrawal step — the on-chain sell is the cash-out.

A virtuals token can fail. If it does not graduate within 30 days, holders can redeem at the curve’s last price. Failed projects can re-launch under a new ticker. dpnm tokens cannot fail in the same way — they are economically active as soon as they have a single buyer.