Your wallet. Your account.
Ready when you are.

Getting started

1. Open the dedicated account setup page and choose Sign in / Create account. Use a wallet through Privy. This wallet identifies your account; it does not automatically become a trading wallet. Use the same sign-in wallet on future visits.
2. Follow the required setup wizard for each chain. Import the exportable Fomo wallet, compare its full address and explicitly authorize seamless trading. Solana is required for Fomo Cash: enable Fomo Cash trading for your Solana wallet and every other chain you enable. Keep the required Solana fee balance shown in setup. For BNB and Robinhood sells, enable automatic sells in wallet setup when prompted; this is a one-time authorization.
3. Download the Chrome extension, unzip it, open chrome://extensions, enable Developer mode and choose Load unpacked. Select the folder containing manifest.json.
4. Open the extension and choose Connect account. Extension orders use your imported and authorized Solana USDC cash wallet. Buys spend Solana USDC; sells settle back to Solana USDC.
5. Open a supported token page on Fomo. Check the detected token and network before entering an order.

Version 0.5.6 · Submitted to the Chrome Web Store. The listing is coming soon; download directly from this website in the meantime. To update an unpacked installation, replace its files and click Reload in chrome://extensions. Keep the existing extension installed so its saved order recovery remains available. This is a live account interface: balances and orders come from your account.

Desktop Chrome is required for the extension. A mobile companion is coming soon.

Import your Fomo trading wallet

Your fomoTX account is independent from Fomo. Signing in does not reuse your Fomo login or authorize trading by itself. Limit orders must be able to execute when their target is reached, so trading-wallet setup uses seamless execution only.

Seamless execution

Trading wallets use seamless execution for automatic extension orders. Export the wallet only through Fomo’s wallet settings. In Account setup, choose your chain, paste the full public address holding your assets in Fomo, and enter the exported private key in the dedicated import field. The browser checks the derived address before invoking Privy’s wallet import.

The private key goes directly through the Privy SDK. It is never sent to the fomoTX API or extension, stored in browser storage, placed in a URL or logged. The import field is cleared after each attempt. Do not enter a recovery phrase or send a key in support messages.

The full address must match. An EVM owner key may have a different address from Fomo’s smart account. Importing that key does not provide access to the smart-account balance. A mismatch blocks import. The same imported EVM address can be selected on Ethereum, BNB and Robinhood; balances remain separate on each network.

One-time, revocable trading authorization

Compare the imported address again, then review and approve the trading authorization. fomoTX can sign orders you submit within its configured Privy policy for 30 days. The extension route does not ask an external wallet to sign each order. Policy and provider checks constrain supported networks, methods, contracts, fees, slippage and expiry. This is not a daily spending cap.

Choose Revoke trading authorization to stop new account trades. This disables backend execution before removing the Privy signer. If the Privy revocation prompt is interrupted, retry removal here. Orders already accepted by a provider may remain active, so review them before revoking. Reauthorization is explicit.

Account setup and trading authorization are required. No separate tester allowlist is needed. If signing policy configuration is unavailable, trading stays disabled.

Place an order

1. Check the token and network. The extension reads your current Fomo token page. Unsupported or ambiguous context blocks trading.
2. Choose buy or sell. With cash routing enabled, buy amounts spend your Solana USDC and sells settle back into Solana USDC. Sell amounts are units of the selected token. Legacy chain-funded routes use the settlement asset shown in the panel. Check the pair and the price denomination shown.
3. Enter your terms. Select an available type, amount, limit or trigger, expiry and slippage.
4. Review and submit. Confirm the full token and wallet addresses, amounts, minimum output, provider, fees and any vault custody terms. The account signs within the authorization you approved.
5. Follow the same order everywhere. The extension and dashboard read the account’s durable order record. Submission is not proof of a fill.

If a submission is uncertain, keep the original order and wait for reconciliation. Do not create another order to compensate for a delayed result.

Order types

Cash routing

Market orders execute when submitted. Limit orders wait for the target and enforce a minimum output. Stop orders trigger at the chosen price and then use the selected slippage; the trigger is not a guaranteed fill price. Execution requires an available validated route.

Legacy chain-funded routes

Existing Jupiter price-trigger orders use custodial vaults. Existing EVM routes use 1inch limits and 0x market swaps. Their token and order-type restrictions still apply until cash routing is explicitly authorized.

Network coverage

Robinhood uses chain ID 4663. Its ETH balance is separate from Ethereum ETH. With cash routing enabled, Robinhood orders settle through Relay to Solana USDC. Legacy Robinhood chain-funded routes use USDG and support market orders only. Wallet import alone does not enable a provider route. A token appearing on Fomo does not establish an executable route; token and transaction validators must also accept it.

One cash balance, across chains

Enable Solana and your destination chain, then authorize cash routing for both Fomo wallets in account setup. Buys use USDC from your Solana wallet; sells return USDC to that wallet through Relay, or Jupiter for supported same-chain Solana token sells. The panel always shows the payment or settlement chain before you submit. Keep SOL available for Solana source fees. Supported automatic BNB and Robinhood sells deduct Relay execution fees from the proceeds.

Market, limit and stop orders use validated Relay or Jupiter routes. Limit orders wait for your target and enforce a minimum output; a touched price does not guarantee a fill. Available routes depend on liquidity and token support. If a Relay trade fails, its refund may arrive as the original asset on the source chain or as USDC/USDG in your destination wallet, less fees; a failed buy does not necessarily return cash to Solana. Native SOL, standard SPL and validated Token-2022 tokens are supported, including tokens with supported metadata or transfer-fee extensions. The panel shows any detected token transfer fee; each quote must meet the validated minimum output. Tokens with transfer hooks or other unvalidated extensions remain unavailable, and some pool routes are not yet supported. Existing wallet authorizations continue to work for their original routes until you opt into the new signer.

The overview combines enabled wallets, cash and discovered holdings. Missing token prices and incomplete wallet indexing are labelled. Provider vault balances and funds in transit are excluded until they arrive in a wallet.

Slippage and fees

Slippage defaults to 5% and can be set from 1% to 99.99%. Values of 100% or more are not supported. Order expiry is limited to 30 days. fomoTX never increases your chosen slippage automatically. Provider and network fee checks also apply. Review the minimum output and fees for every order.

Keep SOL available for Solana source fees. Buys from Solana USDC do not require gas in the destination wallet. For supported BNB and Robinhood wallets, authorize automatic sells once in account setup: fees are deducted from the proceeds and a separate native-gas deposit is not required. Wrapped BNB and wrapped ETH can be unwrapped within the same trade. Provider vault balances remain separate from wallet balances. A trade can fail if its token precision, balance, route or fees do not pass validation.

Wallet balances and funding

Your dashboard combines live cash and discovered holdings across your enabled wallets. Verify its full address and network before moving funds. Funds in a provider vault or a different Fomo smart account are separate. Wait for confirmed destination settlement before trading.

Manage orders

Orders shows the provider, wallet, terms and status. Updates arrive through your authenticated account sync connection. If the connection drops, the dashboard reconnects and loads a fresh account snapshot.

Open an order’s details before cancelling. Cancellation uses your account trading authorization and can incur network fees. The order can fill before cancellation confirms. An unknown or submitting status needs reconciliation, not a duplicate broadcast. The extension checks saved requests for your connected account even after you leave their token page. A pending request does not block trading other tokens; its notice identifies the token and links back to Fomo.

Provider orders can remain active after Chrome closes or authorization is revoked. A revoked account may need reauthorization or the provider’s own recovery interface to manage an existing order. Keep transaction hashes when requesting help.

Troubleshooting

Wallet safety and release scope

The extension receives an expiring account session, never your private key or Fomo credentials. Wallet import happens only in your signed-in fomoTX account through Privy. Authorization remains revocable and incomplete setup blocks execution.

• Use only the dedicated wallet import flow for an exported key. Never send keys or recovery phrases in support messages.
• Check the full wallet, token, network, amount and provider terms before submitting.
• Review vault custody and keep the required Solana fee reserve.
• Testing does not guarantee a fill or remove token, contract, liquidity or provider risk.

Funded imports, policy authorization, live fills, withdrawals and the installed extension lifecycle require acceptance testing with an eligible account. Features marked coming soon remain unavailable.