For Aggregators

Discoverability is vital for tokens that are Flaunched to ensure that they can be bought and sold across the blockchain, without the user having to solely interact with the Flaunch front end.

We have worked with a number of routers, indexers and security researchers to ensure that our tokens are supported. These include:

KyberSwap	Uniswap Router	CoinGecko
DexScreener	1inch	Rainbow
Blockaid	GoPlus Security	OpenOcean
QuickIntel	Honeypot.is

Uniswap V4 LP Hooks

We use Uniswap V4 to power the Flaunch protocol, using hooked liquidity positions to provide beneficial logic for creators and traders. Due to ongoing upgrades to the protocol, we have a number of hooks that will need to be indexed for complete routing.

Base

Contract	Address
Position Manager V1	0x51bba15255406cfe7099a42183302640ba7dafdc
Position Manager V2	0xf785bb58059fab6fb19bdda2cb9078d9e546efdc
Position Manager V3	0xb903b0ab7bcee8f5e4d8c9b10a71aac7135d6fdc
Position Manager V4	0x23321f11a6d44fd1ab790044fdfde5758c902fdc
Any Position Manager V1	0x8dc3b85e1dc1c846ebf3971179a751896842e5dc

Base Sepolia

Contract	Address
Position Manager V1	0x9A7059cA00dA92843906Cb4bCa1D005cE848AFdC
Position Manager V2	0x24347e0dd16357059abfc1b321df354873552fdc
Position Manager V3	0x4e7cb1e6800a7b297b38bddcecaf9ca5b6616fdc
Any Position Manager V1	0xb4a535b9d35851972736495cc52fbfdacf32e5dc

Routing Considerations

When a token is launched on Flaunch, it is paired against flETH. This is a 1:1 wrapping of ETH and can be treated as such during any price calculations. There is zero chance of depegging as it is (un)wrapped.

This does mean, however, that if you are transacting via ETH, which is the primary market, then it would require a multi-hop swap to traverse: ETH <=> FLETH <=> TOKEN.

Chain	Contract Address
Base	0x000000000d564d5be76f7f0d28fe52605afc7cf8
Base Sepolia	0x000000000d564d5be76f7f0d28fe52605afc7cf8

Integration Examples

For onchain quoting, a full Uniswap V4 swap call against the PoolManager will have an estimated maximum gas cost of 150,000 when using our hooks. Please ensure that your quoter limits are set sufficiently to handle this.

KyberSwap

kyberswap-dex-lib/pkg/liquidity-source/uniswap/v4/hooks/flaunch at main · KyberNetwork/kyberswap-dex-libGitHub

Uniswap Routing API

routing-api/lib/util/hooksAddressesAllowlist.ts at main · Uniswap/routing-apiGitHub

---

Flaunch Token List API

To help external platforms that are indexing Flaunch tokens, we created a RESTful API to query and retrieve a list of all tokens launched on the Flaunch platform on the Base blockchain (chain ID: 8453).

This service aggregates token data from the Flaunch platform and provides it in a standardized format. It's designed for aggregators and developers who need to build comprehensive lists of all Flaunch tokens on Base.

Endpoints

The Base URL is: https://data.flayerlabs.xyz/

GET /tokens

Returns a list of Flaunch tokens in JSON format.

Query Parameters

All parameters are optional and can be combined:

Parameter	Type	Default	Description
limit	integer	1000	Maximum number of tokens to return. Must be between 1 and 1000. Values above 1000 will be capped at 1000.
creator	string	(none)	Filter tokens by creator wallet address. Returns only tokens created by the specified address.
orderId	integer	0	Pagination parameter. Returns tokens with orderId greater than this value. Use this to fetch tokens created after a specific timestamp.

Response Format:

{
  "code": 1,
  "message": "",
  "result": [
    {
      "chainId": 8453,
      "address": "0x...",
      "creator": "0x...",
      "launchTime": 1234567890,
      "orderId": 1234567890
    }
  ]
}

Response Fields:

• code : Status code (1 = success, 0 = error)

• message : Error message (empty on success)

• result : Array of token objects

  • chainId : Always 8453 (Base Mainnet)

  • address : Token contract address

  • creator : Wallet address of the token creator

  • launchTime : Unix timestamp of when the token was launched

  • orderId : Order ID (same as createdAt timestamp, used for pagination)

Examples

Get all tokens (up to 1000)

curl https://data.flayerlabs.xyz/tokens

Get tokens with a limit

curl https://data.flayerlabs.xyz/tokens?limit=100

Filter by creator address

curl https://data.flayerlabs.xyz/tokens?creator=0x1234567890123456789012345678901234567890

Pagination - Get tokens after a specific orderId

curl https://data.flayerlabs.xyz/tokens?orderId=1234567890&limit=1000

Combine parameters

curl https://data.flayerlabs.xyz/tokens?limit=500&creator=0x1234567890123456789012345678901234567890&orderId=1234567890

Use Cases

For Aggregators

This API is designed to help aggregators build a complete list of all Flaunch tokens on Base (chain ID: 8453). To retrieve all tokens:

1. Initial Request: Start with GET /tokens?limit=1000 to get the first 1000 tokens

2. Pagination: Use the highest orderId from the response as the orderId parameter in the next request

3. Repeat: Continue fetching until you receive fewer tokens than the limit (indicating you've reached the end)

Example Pagination Flow:

# First request
curl /tokens?limit=1000
# Response contains tokens with orderId up to 1234567890

# Second request (get next batch)
curl /tokens?limit=1000&orderId=1234567890
# Response contains tokens with orderId up to 1234567891

# Continue until response has fewer than 1000 tokens

For Developers

• Token Discovery: Find all tokens launched on Flaunch

• Creator Analytics: Filter tokens by creator to analyze specific wallets

• Integration: Integrate Flaunch token data into your application or service

• Monitoring: Track new token launches by polling with increasing orderId values

Response Codes

• 200 OK: Successful request

• 404 Not Found: Invalid endpoint path

• 500 Internal Server Error: Error fetching data from the GraphQL backend

Chain Information

All tokens returned by this API are on:

• Chain ID: 8453

• Network: Base Mainnet

• Explorer: https://basescan.org

Technical Details

• Ordering: Tokens are ordered by createdAt in ascending order

• Maximum Limit: 1000 tokens per request

---

Onchain PoolId ⇒ Token Data

To help support onchain lookups, we have added onchain PoolId lookups that will return token information. This can help to facilitate the decoding of the PoolId that is emitted from subgraph events.

Chain	Contract Address
Base	0x7c6088c1185fbb770deb1ca7ddeed4ba57659663
Base Sepolia	0x9fa6c64c5fe954f7da1832dc190bbabc0c234989

Each indexer will store the mapped information of all Flaunch tokens, regardless of the PositionManager that it was flaunched from.

---

Custom Event Emission

As our Flaunch events modify swaps and fees away from the standard Uniswap V4 flow, we follow the Uniswap V4 Hook Data Standard to ensure that data can be correctly indexed. These will be emitted from the PositionManager contract and will need to be indexed in conjunction with traditional Uniswap hooks.

event HookSwap(
    bytes32 indexed id,       // v4 pool id
    address indexed sender,   // router of the swap
    int128 amount0,
    int128 amount1,
    uint128 hookLPfeeAmount0,
    uint128 hookLPfeeAmount1
);

event HookFee(
    bytes32 indexed id,       // v4 pool id
    address indexed sender,   // router of the swap
    uint128 feeAmount0,
    uint128 feeAmount1
);