Contract addresses
Every production address on Robinhood Chain mainnet, verified on Blockscout, with the live parameters each one reads.
Every address below is deployed and verified on Robinhood Chain mainnet (chain 4663). Click any of them to open Blockscout, or use the copy button. If you are wiring an integration, these plus Interfaces are everything you need.
#Launchpad core
#Per-venue launch infrastructure
A FeeLocker binds its position manager immutably, so each launch venue has its own locker and fee receiver. Everything else — ownership, both fee managers, the fee split — is shared.
#Venue registry
| venueId | Venue | Router flavour | FeeLocker |
|---|---|---|---|
| 1 | Uniswap V3 | SwapRouter02 | 0x45B96D24…3B6eC7 |
| 5 | SushiSwap V3 | Original SwapRouter | 0xDAB52DF8…7766CD |
#Fee-policy modules
These are the modules bound to each policy id for new launches. A token binds to the module contract itself at launch and keeps it forever, so an older token may point at an earlier generation — read its policy record rather than assuming.
#Trading
#Venue adapters
Registered on the trade manager behind an append-only dexId → adapter map. Details on Venues & routing.
| dexId | Adapter | Address | Venue |
|---|---|---|---|
| 0 | UniswapV2V3Adapter | 0x5e4235F2De012FB095934e72FDba9e2F65Ea34a6 | Uniswap V2 |
| 1 | UniswapV2V3Adapter | 0x5e4235F2De012FB095934e72FDba9e2F65Ea34a6 | Uniswap V3 |
| 2 | UniswapV4Adapter | 0x2017ddD2F85B2A21639359D1B4A69bee52B2A5C4 | Uniswap V4 (native-ETH pools) |
| 3 | FlapAdapter | 0x794704d7caeB5BDfde209B4Fb9f9069cBeF2Bb11 | Flap curve |
| 4 | VirtualsAdapter | 0x81D44e68d62eBE05D884e9C74a409570B5fE4233 | Virtuals curve |
| 5 | SushiV3Adapter | 0xcA936118f2B955f11F0e8277BA6F4787f89161Be | SushiSwap V3 |
| 6 | StockPairV4Adapter | 0x5bD5ce5eA1Cc50D0F873a1c3ce5F870EB31912e2 | Stock-quoted V4 pools |
| 7 | MultiHopV4Adapter | 0xF0e2Fe45a4d4216EaB5398921309a71f7D4cDd13 | Multi-hop V4 (general executor) |
#Tools
#Chain periphery
Not ours — the chain’s own DEX infrastructure, listed for convenience.
#Live parameters
Read from mainnet on 2026-07-29.
| Contract | Call | Value | Meaning |
|---|---|---|---|
| HoodLauncher | launchFee() | 0.001 ETH | Flat fee per launch |
| HoodLauncher | creatorBps() | 7000 | Creator share of LP fees, 70% (protocol keeps 30%) |
| HoodLauncher | MIN_CREATOR_BPS() | 1000 | Compiled-in floor — 10%, unreachable by any setter |
| HoodLauncher | maxWalletBps() | 200 | Sniper-guard wallet cap, 2% of supply |
| HoodLauncher | restrictionBlocks() | 366 | Guard window ≈ 1.2 hours of wall clock |
| HoodLauncher | minFdvWei() / maxFdvWei() | 1.11 / 5556 ETH | Accepted implied starting FDV band |
| HoodLauncher | minSupply() / maxSupply() | 1 / 1e15 tokens | Accepted supply band; default 1e9 |
| HoodLauncher | POOL_FEE() | 10000 | Launch pools are always the 1% tier |
| V4TradeManager | platformFeeBps() | 100 | Trading fee, 1% |
| V4TradeManager | MAX_PLATFORM_FEE_BPS() | 200 | Hard cap, 2% |
| V4TradeManager | referralBps() | 1000 | Referral share, 10% of the fee |
| V4TradeManager | MAX_REFERRAL_BPS() | 5000 | Hard cap, 50% of the fee |
| TokenBackingVault | REDEEM_SKIM_BPS() | 100 | FLOOR redemption skim, 1% — a constant in the bytecode, not a setting |
RPC=https://rpc.mainnet.chain.robinhood.com
cast call 0x5e4121c262B846eb518EF3EADCD5566838AA841F "launchFee()(uint256)" --rpc-url $RPC
cast call 0x5e4121c262B846eb518EF3EADCD5566838AA841F "creatorBps()(uint16)" --rpc-url $RPC
cast call 0xc85237F66E950B4742246F4C0b780f3D0A9BD0B3 "platformFeeBps()(uint16)" --rpc-url $RPC
cast call 0xc85237F66E950B4742246F4C0b780f3D0A9BD0B3 "adapters(uint8)(address)" 7 --rpc-url $RPC#Superseded deployments
These are not the addresses to integrate against. They are here because they are still live and still matter to the tokens that launched on them: a token bound to an older launcher collects its fees from that generation’s locker forever, and trades executed through an older terminal remain part of the indexed history.
Show superseded contracts
- Launcher v2 can no longer register launches — its pointer on the ownership registry and both fee managers was moved to the multi-venue launcher.
- Its locker and receiver stay live forever. Positions cannot be migrated, by design, so
collect()on the old locker is the only way v2 tokens’ fees flow — and it still works exactly as it did. - Old trade managers still execute. Nothing was paused. They are simply not what the app routes through, and the referral manager is shared across all of them, so referral balances carry over.
