Flow

Flow Protocol Skill

Flow enables permissionless token launches via Continuous Clearing Auctions (CCA) with automatic Uniswap V4 liquidity deployment on Base.

For Agents: Load only the resource you need (see decision tree below). Each resource is self-contained with all required code. API base URL: https://api.flow.bid

Transaction Building: Use POST /launches/build-tx for token launches, POST /bids/build-tx for bids, POST /claims/build-tx for claims/exits. Pass the user's wallet address - this determines ownership. Validate wallet setup directly with Bankr API.

Normative Language (RFC-2119)

This skill uses RFC-2119 keywords:

• MUST / MUST NOT: non-optional safety or correctness requirements
• SHOULD / SHOULD NOT: recommended defaults that can be overridden with clear reason
• MAY: optional behavior

If instructions conflict, follow in this order:

1. Safety requirements (MUST)
2. Ownership correctness (msg.sender, wallet identity)
3. Endpoint/schema correctness from references/constants-and-schemas.md
4. UX conventions

For every confirmed on-chain transaction, agents MUST include a BaseScan link in the user-facing confirmation message: https://basescan.org/tx/{txHash}.

UX Guideline: Agents SHOULD NOT display raw transaction data (hex-encoded calldata, transactions arrays from build-tx responses) during user confirmations. Summarize the action in plain language (e.g., "Bid 500 USDC at $45k max FDV on $TOKEN"). Only show raw transaction data if the user explicitly requests it.

Overview

• Continuous Clearing Auction (CCA): Fair price discovery where tokens release gradually over time
• Graduation: Auction succeeds when minimum raise threshold is met (configurable by deployer, default 2000 USDC for USDC auctions)
• Liquidity Deployment: Upon graduation, raised funds + tokens automatically seed a Uniswap V4 pool
• Base Network: All operations on Base (Chain ID: 8453)

Prerequisites

Before using Flow, ensure:

• Wallet configured - Bankr or equivalent (see resources/setup.md)
• ETH for gas - ~0.001 ETH minimum on Base
• USDC for bidding - If participating in auctions (no minimum amount)
• Security reviewed - Read security.md for risk awareness

Cron Job Configuration

For automated operations (scheduled bids, claims, etc.), agents must use the correct session configuration to access blockchain tools:

CRITICAL: Using sessionTarget: "isolated" will cause blockchain operations to fail silently - the agent won't have access to wallet providers like Bankr.

Two-Part Cron Job System

To prevent API overload at auction start time, agents MUST use a two-part system for scheduled bids:

1. At schedule time: Call /bids/build-tx and store the pre-built transactions in the cron job payload
2. At execution time: Submit the pre-built transactions directly to Bankr (no Flow API call needed)

This distributes API load across scheduling times rather than concentrating it at auction start.

See resources/submit-bid.md for complete cron job examples with correct configuration.

Resources

Access detailed implementation guides in this directory:

Canonical References

Setup & Security

Quick Start: Which Resource Do I Need?

What do you want to do?
|
+-- LAUNCH a token
|   +-- resources/launch.md (supports both default and custom params)
|
+-- BID on an auction
|   +-- resources/submit-bid.md (includes trust assessment)
|
+-- CLAIM tokens after auction ends
|   +-- resources/claim-tokens.md (uses claim-hints API)
|
+-- DEPLOY liquidity (permissionless, after graduation)
|   +-- resources/deploy-liquidity.md
|
+-- DEPLOYER ADMIN (claim vesting, collect fees, transfer roles)
|   +-- resources/deployer-admin.md
|
+-- DISCOVER auctions (browse, search, lookup)
|   +-- resources/discover-auctions.md
|
+-- SECURITY concerns or wallet setup
    +-- General security practices --> security.md
    +-- Bankr wallet integration --> wallets/bankr.md

Note: Only load the resource you need. Each resource is self-contained.

Contract Addresses (Base Mainnet)

Function Selectors

LiquidLaunch Contract

AuctionManager Contract

FullRangeStrategy Contract

LiquidLaunchHook Contract

ERC20 (USDC)

Flow API

All auction data is available via the Flow REST API. No RPC URL required.

Base URL: https://api.flow.bid

Endpoints

Example: Fetch Active Auctions

const response = await fetch('https://api.flow.bid/launches/active');
const data = await response.json();

for (const launch of data.launches) {
  console.log(`${launch.tokenSymbol}: Floor FDV $${launch.floorFDV}`);
}

Example: Get User's Bids

const response = await fetch(`https://api.flow.bid/user/${walletAddress}/bids`);
const data = await response.json();

for (const bid of data.bids) {
  console.log(`Bid ${bid.bidId}: ${bid.amountBid} USDC, claimed: ${bid.hasClaimedTokens}`);
}

Pagination

Paginated endpoints accept a page query parameter (25 items per page):

// Get page 2 of completed launches
const response = await fetch('https://api.flow.bid/launches/completed?page=2');

Rate Limits

• 100 requests per minute per IP
• Response headers include X-RateLimit-Remaining

Revenue Model

Flow has a two-tiered revenue model:

LP Fees

By default, all deployer fees are auto-swapped into USDC to allow deployers to claim in one token.

Launch Proceeds