Launch straight into
locked V3 liquidity.

Introduction

DYOR Fun is a permissionless token launchpad on Robinhood Chain. Every launch creates a standard ERC-20 token and immediately places its complete fixed supply into a real Uniswap V3 pool. There is no private bonding curve, later liquidity migration, or separate inside and outside market.

The pool exists from the launch transaction onward. Its V3 position NFT is transferred to the immutable DYOR Fun Vault and cannot be withdrawn through the protocol.

How it works

Protocol parameters

Launch a token

1. Connect a wallet.Switch to Robinhood Chain and keep enough ETH for the launch fee, optional buy, and gas.
2. Upload an image.PNG, JPEG, WebP, or GIF up to 4.5 MB in any aspect ratio. Images are automatically cropped and normalized to a square WebP.
3. Enter token details.Name and ticker go onchain. Description and links become public metadata.
4. Choose the creator wallet.The connected wallet is the default; advanced settings accept another EVM address.
5. Optionally buy initially.The initial buy executes against the new pool within the launch transaction.
6. Review and sign.Your wallet submits the transaction. The API never receives your private key.
7. Wait for indexing.The token appears with its pool, progress, market cap, and metadata.

Trade a token

Each token page includes a non-custodial swap panel connected directly to its official Uniswap V3 pool. Quotes come from the Uniswap V3 Quoter and transactions go through SwapRouter02.

• Buy: native ETH is wrapped to WETH inside the router and exchanged for the token.
• Sell: the token is approved, exchanged for WETH, and unwrapped back to native ETH.
• Fee tier: 1% for every official pool.
• Slippage is selected by the user; the transaction reverts if minimum output is not met.
• Successful approvals and swaps are confirmed on Robinhood Chain before the interface reports success.

Graduation progress

Graduation is a permanent UI milestone. It does not migrate liquidity, change the token, unlock LP, or create another market.

progressBps = min(poolWethBalance / 4.5 ETH × 10,000, 10,000)

graduated = allTimeHighPoolWethBalance >= 4.5 ETH

Before graduation, progress follows the current WETH balance. Once indexed ATH reaches 4.5 ETH, graduated remains true and progressBps remains 10000.

Fees and creator rewards

Every pool uses the standard Uniswap V3 1% fee tier. Fees accrue in the locked position as users trade.

• The DYOR interface verifies the connected wallet against the token creator before enabling a fee claim.
• The underlying Locker remains permissionless onchain; a caller can trigger distribution but cannot redirect any recipient.
• Native-side fees are collected, unwrapped from WETH, and automatically distributed to the configured recipients.
• Token-side fees are collected and sent to the burn address.
• Harvesting never unlocks or migrates the LP position.
• The ecosystem treasury may support standout CTO teams and high-quality IP projects through periodic buybacks.

Locked liquidity

The Factory mints a V3 position NFT using the complete launch supply and transfers it to the immutable LP Vault. The Vault exposes fee collection only and has no NFT transfer, approval, owner, or upgrade function.

Factory and fee-distribution Locker logic use owner-authorized UUPS proxies, while launch tokens share an owner-controlled Upgradeable Beacon. The immutable Vault is deliberately outside that upgrade authority, so existing official LP NFTs cannot be withdrawn through a future implementation upgrade.

This removes LP migration and conventional creator LP withdrawal, but it does not remove risks such as low demand, volatility, wallet concentration, implementation upgrades, or unrelated third-party positions.

Temporary anti-snipe restrictions

• Public same-block buys are blocked during the launch block; the launch origin may perform its configured initial buy.
• The temporary maximum wallet limit is 2% of total supply.
• A temporary per-origin cap limits cumulative buys inside a block.
• Restrictions expire automatically at restrictionEndBlock.
• After expiry, the token behaves as a standard ERC-20 without these limits.

Robinhood Chain uses Arbitrum Orbit infrastructure, so block timing may differ from a simple wall-clock estimate.

Verify an official launch

Names and tickers are not unique. Always verify the token address.

1. Call getLaunchedToken(token) on the official Factory.
2. Confirm exists is true.
3. Compare the returned pool with the expected V3 pool.
4. Confirm the position ID is registered in the official Locker.
5. Use Blockscout rather than trusting screenshots.

if (!(await factory.getLaunchedToken(token)).exists) throw new Error("Not official")

Robinhood Chain contracts

Developer API

The API supports image uploads, metadata, unsigned launch preparation, discovery, live progress, and indexed V3 swaps. Callers always sign with their own wallet.

curl "https://dyor-flame.vercel.app/api/v1/integration/status/0x..."

API quick start → OpenAPI JSON →

GMGN and DeBot integration

DYOR Fun has no internal market, bonding curve, or migration. Every token trades directly in its official 1% Uniswap V3 token/WETH pool from launch onward. Integrators can reuse the same standard Uniswap V3 trading and Swap-event ABIs used for NOXA, while using the DYOR Factory and API for discovery, verification, progress, and graduation.

• Read progress.bps and progress.graduated from the stable integration status endpoint.
• migration.required and migration.migrated are always false; graduation never changes the pool.
• During the first 300 blocks, the temporary maximum wallet is 2% of the fixed supply.
• The launch block blocks ordinary public buys; the launch origin may perform its initial buy.
• TEST provides a 100% graduated fixture; TEST1 provides a non-zero, non-graduated fixture.

Download GMGN / DeBot integration package →

Indexing and data freshness

• A persistent Railway worker discovers Factory TokenLaunched logs.
• Pool Swap logs are scanned in pool-address batches and power volume, trades, and liquidity milestones.
• Multicall3 refreshes market cap and pool WETH balance for many tokens in one block-consistent batch.
• Metadata, launches, metrics, trades, holder snapshots, protocol state, global rollups, and cursors use Neon Postgres.
• Vercel pages and read APIs only query Neon; user requests never trigger chain indexing.
• Images use Vercel Blob and its CDN.

RPC providers and indexers can briefly lag chain head. Verify high-value actions directly through an RPC.

Errors, limits, and caching

• API errors contain a stable code and readable message.
• Lists use cursor pagination, SQL sorting, indexed columns, and maximum page sizes.
• Read responses use CDN stale-while-revalidate caching.
• The live trade panel pauses polling in hidden browser tabs.
• A Neon lease ensures only one Railway replica advances an index cursor.
• Images are size-limited and normalized before storage.
• All v1 endpoints support browser CORS.
• The API never retries wallet failures with a private key.

Risks

Frequently asked questions