which chain is fomo actually on?

fomo is built so you never think about networks. you tap an asset, you get a fill, and the plumbing stays out of the way. that is genuinely good product design and it produces one specific confusion: people cannot answer where their money is when they need to.

robinhood chain, id 4663

the default execution venue is robinhood chain, chain id 4663. that is where most fomo trades settle.

the name causes a predictable misunderstanding, so it is worth being direct: using a chain is not a corporate relationship. settling trades on a network says nothing about ownership, partnership or endorsement by the company associated with its name. it is infrastructure, chosen for cost and speed, and nothing about your fomo account is a robinhood account.

robinhood chain is not the only one in play. bsc, ethereum, base, arbitrum, polygon and solana all appear, depending on where the asset you are trading actually lives.

orders route, they do not just swap

the second piece of architecture worth knowing: fomo does not send your order to a single exchange. trades are routed through an aggregator's router contract, which finds a path across venues and executes it.

three consequences that show up in real use:

• your transaction will not look like a simple swap on an explorer. it looks like an interaction with a router contract, which is why people who go looking sometimes conclude something is wrong when nothing is.
• a single « trade » can touch more than one venue, and its execution quality depends on the route available at that instant.
• size still meets reality. routing finds the best available path; it does not create liquidity that is not there. on a thin memecoin the depth in front of you is the depth in front of you, and this is the mechanism behind most complaints about bad fills and failed sells.

smart accounts, not plain wallets

fomo wallets are erc-4337 smart accounts created behind a normal login rather than externally owned accounts controlled by a seed phrase. transactions go through a bundler instead of being submitted directly.

this is why the app can offer a login-based wallet with no seed phrase at all, and it is covered properly in the key export piece. for chain purposes the practical upshot is that your fomo address is a contract account, and some tooling built for plain wallets treats those differently.

why any of this matters to you

withdrawals

this is the one that costs people money. inside the app you trade assets. the moment funds leave, they are on a specific chain, and the destination must support that same chain. mismatch it and the transfer can succeed on-chain while the funds sit somewhere your receiving app does not display. it is the most common withdrawal failure by a wide margin.

gas

every transaction costs a fee in the native token of whichever chain it runs on. an account emptied to exactly zero cannot pay for its own next transaction. keeping a few dollars of gas per chain is a habit that prevents an entire category of stuck-looking balances.

watching a trader

if you want to track a fomo trader on-chain, multi-chain routing is not a detail — it is the design constraint. a watcher subscribed to one chain will miss trades on the others, and it will miss them silently, which is the worst way to be wrong. the same goes for the address itself: a trader's footprint is spread across these networks, and a resolver that only looks at one of them is working with half the evidence.

the short version

• default venue: robinhood chain, id 4663. no corporate relationship implied.
• also in play: bsc, ethereum, base, arbitrum, polygon, solana.
• orders route through an aggregator, so explorer views look like router calls.
• wallets are erc-4337 smart accounts behind a login.
• the abstraction ends at withdrawal. that is where you must know the chain.