Status & availability
A launchpad’s worst lie is claiming a chain or feature works before it does. This page is the honest ledger: what you can exercise right now, what is fully built but held behind a flag, and what is still coming. Every state here is read from the same switches the code reads - the chain registry’s enabled flag and the launch flow’s live gates - so the docs and the app cannot drift apart.
Everything is testnet today
Every Live below means “works on that chain’s test network” - Robinhood Testnet, BSC Testnet, Base Sepolia, Solana Devnet. The mainnet launchpad contracts are not deployed anywhere yet, so nothing here spends real money. A chain flips to real mainnet only after its full launch → trade → graduation path has been watched end to end, the exact rule the enabled flag enforces in code.
The one exception is the bridge & swap: it runs on LI.FI, which serves live mainnets, so it moves real assets today even though the launch venues do not. Everything else on this page is testnet.
Chains
Launch availability per chain. The “live network” column is the network you can actually launch on today; mainnet is pending everywhere.
| Chain | Launch status | Live network today | Note |
|---|---|---|---|
| Robinhood Chain | Live | Robinhood Testnet | The home venue and the only chain with tokenized-equity features. Mainnet not deployed. |
| BNB Smart Chain | Live | BSC Testnet | Same contracts; graduates on PancakeSwap. Needs a keyed RPC to index. |
| Base | Live | Base Sepolia | Canonical Uniswap V4 - a launch → buy → graduate ran on Sepolia. |
| Ronin | Live | Ronin Saigon | Katana V3 graduator deployed - a launch → graduate ran on Saigon; post-graduation trades link out to Katana. No LayerZero, so no expansion ever. |
| Solana | Live | Solana Devnet | Meteora curves and Raydium custom pairs run on devnet; the Phantom signing path is the last unproven step. |
| Ethereum | Live | Mainnet (bridge only) | Never a launch venue - it exists only inside the bridge/swap widget. |
Features
Feature availability, independent of chain. Each state below is the value of a single flag the launch flow reads; when a flag is false the feature is fully built and tested but deliberately held off.
| Feature | State | Gated by | Where it is live |
|---|---|---|---|
| Bonding-curve launch | Live | enabled | Every enabled EVM testnet + Solana Devnet (SOL curve). |
| Custom-pair pool (Raydium CLMM) | Live | CLMM_LAUNCH_LIVE | Solana Devnet - proven end to end through the real UI. Also reachable on Solana mainnet, quoted in USDC (the first verified mainnet pair) or wrapped SOL. |
| Reward tokens (tax on transfer) | Built · not live | REWARD_LAUNCH_LIVE | Built on Solana Token-2022; held on a re-run of the payout keeper and client sign-off. |
| pump.fun bundle mode | Live | PUMP_LAUNCH_LIVE | Live on Solana mainnet; atomic Jito bundle proven live (slot 440317888). Three wallet sources (generate / use-my-own / one-buyer with an optional dev buy). |
| Native Solana DBC launch | Live | NEXT_PUBLIC_SOLANA_DBC_CONFIG | Live on mainnet: a Meteora DBC launch under config GU7mLsZ. 1% fee split 50% creator (claimed in-app) / 50% platform (auto-swept to treasury by the fee keeper); graduates at ~73 SOL to DAMM v2, LP locked 35/65. |
| Cross-chain expansion (OFT) | Built · not live | MULTICHAIN_LAUNCH_LIVE | EVM legs built end to end; held on two fee numbers and one watched run. Never on Ronin. |
| Pay fees in tokenized stock | Built · not live | External audit | Robinhood Chain only; the conversion rail opens after a fresh security audit. |
| In-app bridge & swap (LI.FI) | Live | feeEnabled | Works today across 5 chains; our 0.75% fee stays off until the integrator is registered. |
| Referral earnings | Live | enabled | On every EVM chain. A Solana trade records a referral of exactly 0 - EVM-only by design. |
| Coin flip (side game) | Dormant | FLIP_ADDRESS | Dormant until its contract is configured, and legal-gated where it does run. |
How this page stays honest
Two switches decide everything above. A chain’s enabled flag in the shared chain registry means a launch there actually works - it is flipped on only once a watched live run proves it, and off the moment nothing is deployed. A feature’s *_LAUNCH_LIVE gate in the launch flow means the same for that feature: the code is present and threaded either way, and the flag is the one line that changes when it goes live.
For the full feature-by-chain grid - every cell against every chain, with the same four states - see What works where. When this page and the launch form ever disagree, the form wins; both read the same flags.