Protocol Concepts

Background on how Fren tokens, fees, and swaps work. None of this is required reading to make a first trade, but it explains the constraints you will hit.

Tokens

Every token has a fixed supply of 100,000,000,000 with 18 decimals. Tokens launch as standard ERC-20s directly into a canonical Uniswap V3 pool against a counter asset (WETH, USDG, or FREN). There are no transfer hooks, no trading taxes, and no launch-time trading restrictions — once the pool is live, anyone can trade it with any Uniswap-compatible tooling.

Fees and rewards

A token's feeManager earns the Uniswap V3 LP fees from the locked initial liquidity position. The pool's fee tier is set at launch, and fees accrue to the position as the token trades. withdrawFees collects them in a single call.

Separately, token deployers earn protocol (FREN) rewards distributed via DeployHandler contracts, claimed with claimRewards.

Swaps

Swaps execute directly against the token's Uniswap V3 pool via the canonical SwapRouter02. Quote with GET /swaps/quote, build calldata with POST /swaps/build-tx, approve the router for the input asset, and submit the transaction from your own wallet.

Open pools

Because pools are canonical Uniswap V3, tokens are also tradeable through third-party aggregators, bots, and terminals from the moment they launch.

Liquidity

Liquidity is standard Uniswap V3: positions are minted over a tick range with a chosen fee tier (100, 500, 3000, 10000). The initial deploy liquidity is locked. Agents can mint and manage their own positions through the relayed liquidity actions — see Actions & Signing.

Constraints checklist

  • Initial buy bounds: read GET /info → deploy.initialBuyBounds per counter asset.
  • minTokensOut must be greater than 0 when initialBuyAmount > 0.
  • Intent binding: gasTx.data = keccak256(intentSignature).
  • Failed actions still consume the gas fee — always /verify first.
PreviousAgent EndpointsNextResources & Glossary