lemon.fun.

§1Chain & Infrastructure

§2Token Lifecycle - Instant V3 (current)

2.1  Launch (single transaction)

A creator calls LemonLaunchFactory.launch(...) with token metadata (name, ticker, image, socials) and a mandatory dev-buy in ETH (minimum 0.03 RBH to guarantee a healthy initial tick). In one atomic transaction the factory:

• Deploys the Lemon Token (ERC-20, 1,000,000,000 fixed supply, no owner, no mint, no tax).
• Wraps the dev-buy ETH to WETH.
• Creates the Uniswap V3 TOKEN/WETH 1% pool and initializes the sqrt price.
• Mints a single full-range LP position seeded with the entire token supply + dev-buy WETH via NonfungiblePositionManager.
• Deploys a fresh LemonLaunchLocker and transfers the LP NFT to it (LP is permanently locked from this block).
• Executes the dev-buy against the freshly-live pool and delivers tokens to the creator.
• Emits TokenLaunched(token, pool, locker, creator, tokenId).

2.2  Trading

All trades - from the first block onward - happen on the canonical Uniswap V3 pool via SwapRouter02. There is no bonding phase, no graduation event, and no migration risk. Scanners see a standard, verified V3 pool with a locked LP NFT.

2.3  Fee claiming

Anyone may call LemonLaunchLocker.claim() at any time. Fees collected from the LP NFT are split 30% to platform / 70% to creator on both the WETH and token sides. Contract emits FeesClaimed(...). LP principal cannot be withdrawn, migrated or upgraded - the locker has no such function.

§3Per-Launch Contracts

§4Platform Contracts

Lemon launcher (Instant V3)

Lemon launcher (Tax mode, Uniswap V4)

Robinhood Chain - Uniswap V3

Robinhood Chain - Core tokens

§5Fee Model

§6Public HTTP API

Base URL: https://lemon.fun. All endpoints are unauthenticated, CORS-enabled, and return application/json. Rate limits are per-IP and generous for indexers - contact the team for whitelisting.

6.1  Example - token detail

GET https://lemon.fun/api/public/launchpad/token/0xf363b1b0d7906058fba29fafc4c258b652b16432

{
  "address": "0xf363...6432",
  "name": "Lemon Cat",
  "ticker": "LEMONCAT",
  "pool": "0x331b215bc75c6a6605879366ba5f12854265ce50",
  "locker": "0xc10309cf03bc81c121a8270e3a28e159a9296903",
  "mcap_eth": 12.4,
  "price_eth": 0.0000000124,
  "holders": 128,
  "created_at": "2026-07-20T..."
}

6.2  On-chain event schema

§7Security Posture

• All platform contracts are ownerless once deployed; no upgrade proxy is used.
• Pool fee split (30% platform / 70% creator) is a compiled constant in LemonLaunchLocker; it cannot be changed by any party.
• The Uniswap V3 pool is created and seeded atomically at launch; there is no migration step and no privileged liquidity add path.
• LP NFTs are held by a per-token LemonLaunchLocker with no withdraw path; only fee collection is exposed.
• Every launch is emitted as a canonical event on the factory, enabling deterministic reconstruction of the launchpad from chain history alone.

§8Tokenized Stock Dividends

A creator can launch on the exact same curve, factory and locker as any other Lemon token and additionally nominate a tokenized stock on Robinhood Chain as the dividend asset. Pairing is always native RBH; the stock is bought with the creator share of pool fees by a per-token StockDividendVault and distributed to holders.

• Every 30 minutes the vault converts accumulated fee revenue into the nominated stock on Uniswap V3.
• Once per day at 12:00 UTC a holder snapshot is taken and a merkle root of allocations is published on-chain.
• 75% of converted stock goes to holders; the remainder splits between creator and platform as compiled constants.
• A creator-set minimum token balance decides eligibility; the threshold is stored in the vault and cannot be raised retroactively for a published epoch.
• Claims are pull-based merkle claims: holders claim at /stocks/<wallet> or from the terminal sidebar. No party can claim on a holder's behalf.
• The vault has no withdraw path for holder-allocated stock; the keeper key can only convert, publish and top up gas.
• The vault factory is deployed separately from LemonLaunchFactory and LemonLaunchLocker, so launcher bytecode - and third-party indexing of it - is untouched.

§9Contact & Verification

Bytecode for every contract in §4 is verified on Robinscan; the source Solidity is available in the platform's public repository.

© 2026 lemon.fun - Independent, community-built launchpad on Robinhood Chain.