www.fomocurve.family
“Fomo Curve: where tokens go viral”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
What it is
- The site describes itself as: “Fills the curve. Lands in their bags. Fomo Curve is an independent Solana launchpad.”E2
- It's built with Next.js and React (common tools for building web apps).E6E7
- In your browser it can copy text to your clipboard, saves small bits of data in your browser and keeps a live two-way connection open to a server.E11E12E13
- It has sections such as /explore.E46
- While loading, it called 1 endpoint on its own servers, such as /api/auth/session.E15
Where your data goes
On a first visit the page only talked to its own servers (www.fomocurve.family).
Crypto and wallets
How key features work
What it can ask your wallet to sign
Its code can ask your wallet for signTransaction. Each of these opens a wallet pop-up you must approve; read it before you click.E47
signTransactionConnecting your wallet
It connects to crypto wallets using WalletConnect / Reown, Solana web3 / wallet adapter, signTransaction and signMessage. Connecting shows the site your wallet address; it doesn't move funds by itself.E9E10
WalletConnect / ReownSolana web3 / wallet adaptersignTransactionsignMessageSign-in and accounts
Sign-in and account features show up in its code or traffic (/api/auth/session, /api/auth/challenge, /api/auth/verify and /api/auth/x/start).E15E18E19E8
/api/auth/session/api/auth/challenge/api/auth/verify/api/auth/x/startLive updates
It keeps live connections open (WebSockets) so content updates without reloading.E13
websocketLoading its content
Its content loads from its own API while you browse (/api/auth/session).E15
/api/auth/sessionDrawing and editing in the browser
The page draws and edits graphics in your browser using the canvas.E14
canvasPages and API calls
Pages it links to
//exploreEndpoints
Called while loading (seen) or named in the code (code).
| www.fomocurve.family/api/auth/session | seenE15 |
| /api/platform/features | codeE16 |
| /api/market/board | codeE17 |
| /api/auth/challenge | codeE18 |
| /api/auth/verify | codeE19 |
| /api/auth/x/start | codeE20 |
| /api/img | codeE21 |
| /api/launches | codeE22 |
| /api/campaigns | codeE23 |
| /api/proposals | codeE24 |
| /api/me | codeE25 |
| /api/metadata | codeE26 |
| /api/platform | codeE27 |
| /api/portfolio | codeE28 |
| /api/me/profile | codeE29 |
| /api/me/profile/x | codeE30 |
| /api/me/profile/username | codeE31 |
| /api/platform/kols/fomo | codeE32 |
| /api/market/token | codeE33 |
| /api/search | codeE34 |
| /api/community/creators | codeE35 |
| /api/auth/x/session | codeE36 |
| /api/proposals/sent | codeE37 |
| /api/kol/me/proposals | codeE38 |
| /api/community/proposals | codeE39 |
| /api/kol/me/profile | codeE40 |
| /api/kol/me/blocks | codeE41 |
| /api/community/creators/match | codeE42 |
| /api/kol/me/stats | codeE43 |
| /api/kol/terms | codeE44 |
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- The tech check compares the site's own words with what its public page loads. Work done on servers, in private code or in separate apps isn't visible here, so 'nothing found' means not visible on the public page, not that it doesn't exist.
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- The code reader hit its size budget on parts of 12 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id 8n8Ss9KY.