FOMO Wallet: Find Any Trader's Solana & EVM Addresses

A FOMO wallet is the on-chain address (or addresses) tied to a social trader's public handle. When you see a trader posting wins on Twitter or sharing alpha in a Discord, their FOMO wallet is where those trades actually happened. Resolving a handle to a wallet address lets you verify their track record, copy their positions, and build tools that react to their moves in real time.

What Is a FOMO Wallet?

Most crypto traders operate across multiple chains. They might post screenshots from Solana, then flip to Base or Ethereum for an NFT mint. Each chain requires a separate wallet address, and those addresses are rarely advertised in a bio or pinned tweet.

A FOMO wallet is the set of wallet addresses (Solana and EVM) that belong to a single trader identity. The term comes from "fear of missing out" behavior: retail traders see a known wallet buy a token and rush to follow. But before you can follow, you need the actual address.

Social handles (Twitter, Telegram, Discord) do not natively map to wallet addresses. A trader might use @cryptowhale on Twitter and 0xabc...def on Ethereum, with no public link between them. The FOMO wallet is the bridge: it connects the social persona to the on-chain footprint.

This matters because on-chain data is the only source of truth. A trader can claim any track record in a tweet. Their wallet cannot lie. If you want to verify performance, track holdings, or trigger alerts when they trade, you need the wallet address first.

Why You Need a Trader's Wallet Address

Wallet addresses unlock three categories of data that social posts cannot provide. If you only need one trader checked by hand, a browser-based fomo wallet finder does that first step for free; the categories below are what you get once the address is in code:

Available position history. Public chain records can provide independently inspectable transactions, but API coverage and price interpretation can be partial. Preserve source and coverage fields before calculating entries, exits, holding periods, or PnL.

Live holdings and balances. A trader's current portfolio is visible in real time. You see every token, the quantity, the cost basis, and the unrealized gain or loss. This is critical for copy trading: you want to know what they hold now, not what they tweeted about last week.

Behavioral signals. Wallet activity generates signals: a trader accumulating a low-cap token, moving funds to a DEX, or exiting a position. These signals can trigger alerts, feed dashboards, or inform your own trades. But you cannot build a signal without the source address.

Manual lookups are slow and incomplete. Automated systems need a programmatic way to resolve @trader_handle to {solana_address, evm_addresses[]} in one call. That is the job of a FOMO wallet API.

Manual Methods to Find Trader Wallets (and Why They Fail)

The obvious approach is to check a trader's social profiles for a wallet address. Some traders do list a Solana address in their Twitter bio or pin a transaction link. But this breaks down quickly:

• Most traders do not advertise addresses. Privacy, security, and tax concerns keep wallets out of bios.
• Multi-chain traders have multiple addresses. A bio might show a Solana wallet but omit the EVM address they use for Base or BSC trades.
• Addresses change. A trader might rotate wallets, use a fresh address for a new strategy, or consolidate funds. A stale bio link sends you to an inactive wallet.

You could scrape transaction links from tweets. If a trader shares a Solscan or Etherscan link, you extract the address. This works once but does not scale. You need a bot to monitor every tweet, parse URLs, deduplicate addresses, and handle link shorteners. You still miss trades they do not tweet about.

Another method: cross-reference known wallets from leaderboards or Discord servers. Some communities maintain spreadsheets mapping handles to addresses. These lists are incomplete, outdated within days, and rarely cover more than one chain.

The core problem is that social identity and on-chain identity are separate systems with no native bridge. Manual methods are one-off hacks. They do not give you a live, multi-chain mapping you can query in code.

Using fomoapi.io to Resolve Handles to Wallets

fomoapi.io solves this by maintaining a resolved index of trader handles and their wallet addresses across Solana and EVM chains. You send a social handle, you get back all linked wallets in one JSON response.

The endpoint is GET /v2/users/{handle}. The {handle} parameter accepts Twitter handles, Telegram usernames, or internal user IDs. The API returns a user object containing:

• Solana wallet address
• EVM wallet addresses (Ethereum, Base, BSC, and three other chains)
• User metadata (name, profile image, social links)
• Summary stats (total PnL, traded volume, trade count)

This is a single HTTP request. No scraping, no guessing, no stale data. The response includes both Solana and EVM addresses because most active traders operate on multiple chains. You get the full picture in one call.

The API also powers a live trader leaderboard ranked by PnL. Every trader on the leaderboard has resolved wallet addresses, so you can query any top performer by handle and get their full on-chain history.

API Request and Response Shape

Here is a concrete example. You want to find the wallets for a trader with the handle @trader_alpha. The request:

GET https://api.fomoapi.io/v2/users/trader_alpha
Authorization: Bearer YOUR_API_KEY

The response (simplified):

{
  "id": "usr_abc123",
  "handle": "trader_alpha",
  "name": "Alpha Trader",
  "avatar_url": "https://...",
  "solana_wallet": "9xQeWvG816bUx9EPjHmaT23yvVM2ZWbrrpZb9PusVFin",
  "evm_wallets": [
    {
      "chain": "ethereum",
      "address": "0x1234567890abcdef1234567890abcdef12345678"
    },
    {
      "chain": "base",
      "address": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd"
    }
  ],
  "stats": {
    "total_pnl_usd": 145230.50,
    "total_trades": 412
  }
}

The solana_wallet field is a single string because Solana uses one address per user in most cases. The evm_wallets array contains objects with chain and address fields. A trader might have addresses on Ethereum, Base, BSC, Polygon, Arbitrum, and Optimism (six EVM chains total).

You now have the raw material to query trade history, fetch current balances, or subscribe to live updates. The wallet addresses are the keys that unlock the rest of the API endpoints documentation.

Solana + EVM: Six Chains in One Call

Crypto traders do not stay on one chain. A Solana degen might ape into a Base memecoin. An Ethereum whale might farm yield on BSC. If you only track one chain, you see a fraction of their activity.

fomoapi.io indexes six chains:

When you query a trader's handle, you get addresses for all chains they have linked. This is not a guess or a heuristic. The API stores verified mappings from identity providers and on-chain signatures.

A single trader might have a Solana wallet for SPL tokens and an Ethereum wallet for ERC-20s. You need both to calculate total PnL. The API gives you both in one response, so you do not make six separate calls or maintain six different data pipelines.

On-Chain Wallet Data vs. Self-Reported Stats

The difference between a FOMO wallet and a social media claim is verification. Anyone can tweet "10x on $TOKEN". A wallet either executed that trade or it did not. The blockchain is the source of truth.

fomoapi.io resolves the wallet from on-chain transaction logs. Every trade, every transfer, every swap that address made is on the canonical ledger. The PnL numbers and trade counts in the API response are fomo.family's, and every one arrives with the wallet it belongs to.

This eliminates several attack vectors:

• Cherry-picking wins. A trader cannot hide losses. The API sees every transaction, including the ones they do not tweet about.
• Fake screenshots. On-chain data cannot be Photoshopped. If the trade did not happen on the blockchain, it does not appear in the API.
• Inflated stats. Self-reported returns often exclude small losses or count paper gains as realized PnL. The wallets come back with it, so the entries and exits are there to read.

That matters for copy trading and leaderboard systems. If you are routing real money based on a trader's performance, you need confidence that the performance is real. A FOMO wallet gives you that confidence because the data comes from the chain, not the trader.

You can cross-check the API response against a block explorer. The solana_wallet address can be pasted into Solscan. The evm_wallets addresses can be checked on Etherscan, Basescan, or BscScan. The transactions will match because the API is reading the same data you would see manually, just aggregated and served through a clean JSON interface.

Next Steps: From Wallet to Trade History

Once you have a trader's wallet addresses, you can query their available trade history with the /trades endpoint:

GET https://api.fomoapi.io/v2/users/usr_abc123/positions?limit=50

This returns an array of trade objects, each with:

• Token bought or sold
• Entry and exit price
• Quantity
• Timestamp
• Realized PnL
• Transaction hash

You can filter by date range, token address, or trade outcome (win/loss). This is the raw data you need to build a trade journal, calculate Sharpe ratios, or generate alerts when a trader opens a new position.

For live updates, the WebSocket endpoint at wss://api.fomoapi.io/ws/alerts streams real-time trade events. You subscribe to a user ID and receive a JSON message every time they execute a trade. Events arrive as FOMO publishes them, so timing follows the app rather than block time.

You can also fetch current holdings with GET /v2/users/{id}/balances. This shows every token the trader holds right now, with current market value and unrealized PnL. Combine this with trade history and you have a complete picture: past performance and present exposure.

For token-level analysis, the GET /token/{address}/holders endpoint shows which traders hold a specific token. This is the inverse lookup: instead of "what does this trader hold?", you ask "who holds this token?". It is useful for finding early adopters, tracking whale accumulation, or identifying which traders are rotating into a new asset.

All of these endpoints require the wallet addresses you get from the /v2/users/{handle} call. The FOMO wallet is the entry point. Without it, you cannot query trade history, balances, or live feeds. With it, you have programmatic access to the full on-chain footprint of any social trader.

fomoapi.io offers a free tier for testing and paid plans starting at $49.99/month for production use. Full details on rate limits and features are available on the API pricing tiers page. To request an API key, message t.me/eulatxt.