What BlueFun provides
A complete launch, discovery, trading and creator-revenue experience built around verifiable onchain state.
Create
Deploy a 1B-supply token through a Bond or Direct DEX route, with metadata and an optional creator first buy.
Explore
Discover newest, bonding, graduated and direct markets across both supported networks.
Trade
Buy and sell from the token page with quotes, minimum received, slippage controls and onchain activity.
Dashboard
Track created tokens, held assets, trading activity and claimable creator revenue from one wallet view.
Locked liquidity
Production LP positions remain in protocol custody without a principal-withdrawal or NFT-transfer path.
Historical continuity
Tokens created by legacy deployments remain indexed and continue to use the contracts they launched with.
Networks and token standards
The product experience is shared, while each network uses its native launch standard and Uniswap v4 deployment.
Launches use the Base-native B20 ASSET standard. BLUE also lives on Base.
Launches use fixed-supply ERC-20 tokens and the network's official Uniswap v4 stack.
Choose how price discovery begins
Both routes create a 1B-supply token with zero free creator allocation, but liquidity begins differently.
Price discovery before DEX graduation
- 01
The full supply enters the protocol bonding-curve market.
- 02
Users trade against virtual reserves until the fixed 5 ETH gross target is reached.
- 03
Remaining tokens and real ETH reserves graduate into a locked Uniswap v4 position.
- Optional first buy
- Up to 5 ETH
- Creator allocation
- 0%
- Graduation
- 5 ETH gross
A live Uniswap v4 market in one launch transaction
- 01
The token and concentrated-liquidity pool are created atomically.
- 02
The 1B supply starts as token-only, permanently locked liquidity.
- 03
Early buys add native ETH depth and move price along the configured curve.
- Optional first buy
- Max 5% supply
- Creator allocation
- 0%
- Graduation
- Not required
Fees and revenue distribution
Launch fees, curve trading fees and Direct DEX fees are accounted for separately.
Paid to the platform on either route. An optional first buy is added on top.
0.7% platform and 0.3% creator, charged in ETH on buys and sells.
0.7% platform and 0.3% creator through the locked LP fee accounting.
0.7% of native output to the platform; 0.3% token-input fee is burned.
| Event | Platform | Creator | Token burn |
|---|---|---|---|
| Bond buy | 0.7% ETH | 0.3% ETH | — |
| Bond sell | 0.7% ETH | 0.3% ETH | — |
| Bond LP after graduation | 70% of realized fees | 30% of realized fees | — |
| Direct buy | 0.7% ETH | 0.3% ETH | — |
| Direct sell | 0.7% native output | — | 0.3% token input |
Permanently locked principal
The protocol separates liquidity principal from collectible trading fees.
No principal-withdrawal function is exposed by the production lockers.
No LP NFT transfer function is exposed to the creator or platform.
Fee realization uses a zero-liquidity delta and verifies liquidity before and after collection.
Creator and platform balances are pull-based: each beneficiary can claim only its own recorded amount.
Anyone may trigger fee realization for a position, which allows keepers to maintain accounting. Triggering collection does not grant the caller ownership of the funds; proceeds are credited only to the configured platform recipient and the launch creator.
From launch to lifetime tracking
Creators keep control of their wallet while BlueFun organizes the onchain and indexed data around it.
Select Base or Robinhood Chain and connect the wallet that will own the launch identity.
Add token identity, choose a launch route and optionally execute the creator first buy atomically.
View created tokens, holdings, trades and creator-fee balances in the dashboard.
Claim available ETH or legacy Bond LP token fees directly to the creator wallet.
Trading and approvals
Quotes and transactions use the route associated with the token's original launch.
Bonding phase
Buys and sells execute against the BlueFun bonding-curve market. Trading closes when graduation is ready, then moves to the locked Uniswap v4 pool.
DEX phase
Graduated and Direct tokens trade through their Uniswap v4 pool. Custom-hook pools may not appear immediately in every third-party aggregator even when BlueFun routing works.
Allowance reuse
A sell requires token allowance for the relevant spender. If the existing allowance is sufficient, BlueFun reuses it; otherwise approval and swap remain two separate wallet transactions.
Execution protection
The interface shows quotes and minimum received. Contract calls enforce deadlines, minimum output and the launch configuration hash where applicable.
BLUE
The canonical BlueFun ecosystem token on Base.
- Network
- Base
- Standard
- B20 ASSET
- Total supply
- 1,000,000,000 BLUE
- Decimals
- 18
- Original route
- Bond launch
- Launch ID
- #3
- Initial creator allocation
- 0 BLUE
- Market state
- Graduated to Uniswap v4
0xb200000000000000000000af2d07754b927109bcAlways verify the full contract address before trading. Live creator, burn and holder-bucket balances are read directly from Base.
BLUE is a community and platform identity asset. This documentation does not promise price appreciation, yield, governance rights or future utility.
Current production contracts
New launches use the current deployment set. Historical launches remain connected to their original verified contracts.
0x830569…ed34360xb503b0…1498dd0x48aa4c…8ab4d50x024668…8ba275Security model and known constraints
Locked liquidity reduces one class of risk; it does not make a token valuable or eliminate smart-contract, market and infrastructure risk.
Bond administration
Current Bond factory administration is behind a two-key 48-hour timelock. Reserve custody is isolated from routine factory configuration.
Direct configuration
Current Direct factory parameters are controlled by the platform deployer. Fee constants live in the deployed hook; per-position shares are stored when liquidity is created.
Burn accounting
Direct sell-token fees are sent to 0x0000…dEaD. Burn and platform revenue are emitted and readable onchain.
Market risk
Low liquidity, volatility, price impact, failed routing, RPC outages and irreversible transactions remain possible.