coinlyfans.fun
“CoinlyFans”
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 Internet Archive has never saved this site, so it is probably new.E35
- The site describes itself as: “Every coin is a creator. Launch a gooner coin on Solana and pair it with BTC.”E2
- It's built with Next.js and React (common tools for building web apps).E10E11
- In your browser it can copy text to your clipboard, saves small bits of data in your browser, keeps a live two-way connection open to a server and can open your device's share menu.E15E16E17E18
- It has sections such as /feed, /creators, /meta, /how-it-works, /launch and /pool.E31
- While loading, it called 2 endpoints on its own servers, such as /api/pools and /api/config.E20E21
Where your data goes
Crypto & walletsConnect wallets, read blockchains or fetch token prices. 1
| api.dexscreener.com | DexScreener: token prices and pools | 2×E9 |
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.E32
signTransactionConnecting your wallet
It connects to crypto wallets using WalletConnect / Reown, Solana web3 / wallet adapter, Phantom, signTransaction and 1 more. Connecting shows the site your wallet address; it doesn't move funds by itself.E12E13E14E9
WalletConnect / ReownSolana web3 / wallet adapterPhantomsignTransactionsignMessageLive updates
It keeps live connections open (WebSockets) so content updates without reloading.E17
websocketLoading its content
Its content loads from its own API while you browse (/api/pools and /api/config).E20E21
/api/pools/api/configDrawing and editing in the browser
The page draws and edits graphics in your browser using the canvas.E19
canvasSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E16
local_storagePages and API calls
Pages it links to
//feed/creators/meta/how-it-works/launch/poolEndpoints
Called while loading (seen) or named in the code (code).
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.
- REA hit its size budget on parts of 15 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 qbRsbaG4.