Developer overview
Build on BIBO: create launches, connect markets and bring project rewards into your application.
On this page
Choose where to connect
BIBO connects token launches, liquidity markets and project rewards. Launchpad integrations follow a token from its curve into a pool; DEX integrations discover and route through its concentrated liquidity pools. Start with the market or action your application needs to support.
The launch edition pairs launches with BIBOCAT, and from 2 October 2026 also with WETH and BGB, as each is approved in LaunchFactory's quote registry. BIBO, the platform token, has not been issued and ve(3,3) is not active in this release. Voting interfaces are included separately as a future reference.
These pages cover selected public interfaces and the steps needed to use them. Solidity excerpts are interface references, not complete ABIs or deployable contracts. The contract directory lists this deployment's contracts and explains how to discover each project's instances.
Choose an integration
Amounts, approvals and confirmations
- Use integer amounts
- Token amounts use the asset's smallest unit. Read decimals() on each ERC-20 and keep onchain values in integer arithmetic. Launchpad fields ending in Bps use basis points with a denominator of 10,000. Pool fees use pips with a denominator of 1,000,000: the market fee, fee(), and the additional quote-side fee, creatorFeePips(), which holds the Creator Fee and any platform fee. Timestamps and deadlines are Unix seconds.
- Approve the contract that spends
- Use LaunchFactory for launch fees, BondingCurve for curve trades, SwapRouter for CL swaps, NonfungiblePositionManager for CL deposits and LaunchStakingRewards for Meme stakes. When an executor calls a router, that executor also needs to approve it. Read the current allowance before requesting an approval.
- Read, simulate, submit, confirm
- Read related values at the same block where possible. Simulate the intended call with the actual sender and arguments, submit it, then confirm the receipt and refresh contract state. An ERC-20 approval does not complete the action that follows it.
- Use events for discovery, state for decisions
- Index logs by chain, contract, transaction hash and log index, and account for chain reorganizations. Contract reads determine whether a launch is tradable and which rewards are currently claimable. A transaction's return value is available in simulation; submitted transactions are followed through receipts, events and subsequent reads.