Lots and third-party platforms
Where you trade determines the route, fees and transaction controls. FOMO, Uniswap interfaces, aggregators and chart providers operate independently of Lots. Listings and prices do not guarantee execution or a later sale.
How the native platform interacts with contracts
The Lots application prepares transactions for your wallet:
| Action | Contract path |
|---|---|
| Compose | Lots factory creates the recipe vault |
| Mint / redeem | Lot vault receives or returns components |
| Launch | Launch factory creates the token and pool |
| Buy / sell / rotate | Lots router settles through official launch pools |
| Collect / claim | Locker accounts for fees and pays entitlements |
| Get ready / fund liquidity | LotFlow and the shared manager, with Uniswap Universal Router swaps |
RouterV16 serves launch tokens. An ETH-funded Lot-paired buy acquires components, mints the Lot and buys the launch token. Selling to ETH reverses this path; selling to the Lot stops before redemption. Rotation uses the shared quote without rebuilding it.
Underlying exchange contracts and component markets remain dependencies. See contract identities.
Where LotFlow fits
LotFlow is Lots' Uniswap v4 hook for the Lot/USDG market, not a separate app or a router every service uses. Providers identify it by hook address on Robinhood Chain (4663):
| Market | Contract | Address |
|---|---|---|
| LotFlow | NavJitHookV17 | 0xb672a5d825F82dEA8574711d1dA696FcC48d2AE0 |
| LotFlow, ETH-priced components | NavJitHookV17 | 0x447184450e4615c2ec2545540B53F213fB9c2aE0 |
Support for one hook does not imply support for another. See LotFlow liquidity.
Compatible routers can use LotFlow as one leg:
Payment → USDG → LotFlow → Lot token → launch-token/Lot pool
A direct launch-token/Lot swap omits LotFlow. Native launch trading uses Lots routers, while native Get ready and liquidity-funding swaps also use LotFlow. The interface name alone does not identify the route.
The Lot/USDG and launch-token/Lot markets have separate fees, liquidity and checks. Token rights stay the same whichever interface is used. LotFlow supports at most five constituents; compatible composition alone does not establish execution availability. Check the exact hook and provider route against the LotFlow addresses.
FOMO, Uniswap and other services
- FOMO supports Robinhood Chain through its own trading experience. Check support for the exact token, size and direction, receiving account and withdrawal options. FOMO announcement.
- Uniswap's interface selects from supported routes and hooked pools. Its interface is distinct from Uniswap contracts used inside Lots. Hooked-pool routing guidance.
- Other providers may omit native Rotate or in-kind redemption, or add bridging and other stages to a multi-chain order. Review each stage separately.
What to review before trading elsewhere
| Check | Review |
|---|---|
| Identity | Network and full token addresses |
| Route and output | Actual final asset and whether you receive tokens or a service balance |
| Protection | Expected output, minimum received and expiry |
| Costs | Pool fees, component fees, LotFlow spread, provider fees and gas |
| Authorization | Spender, allowance and signed-order terms |
| Custody | Receiving wallet, transfer and withdrawal options |
| Settlement | Order stages and transaction receipts |
Native approvals and slippage settings do not carry over. Official launch-pool fees and active early limits apply when that pool is used; an external route can select different pools.
Why availability and prices differ
Providers support different hooks, pools and routes. An external provider can reject a trade that the native component route can quote. LotFlow still needs transferable components, liquidity, price guards and settlement inventory. More slippage cannot supply missing support or inventory.
Readiness and extra deposits do not guarantee external charts or execution. For an external order problem, retain its reference and transaction hashes and use that provider's official support. For native actions, use walkthroughs. Access rules, token rights and market risks apply through every interface.