www.useversus.xyz
“versuspad · every coin launches long and short”
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.E24
- The site describes itself as: “Launch a coin on StonkFun that anyone can go long or short on from its first minute. Every coin's creator fees fill the pool that pays the w”E2
- It's built with React (common tools for building web apps).E8
- In your browser it can copy text to your clipboard and saves small bits of data in your browser.E10E11
- It has sections such as /create, /trade, /portfolio, /how and /c.E20
- While loading, it called 5 endpoints on its own servers, such as /api/state, /api/feed, /api/pad and 2 more.E12E13E14E15
Where your data goes
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.E21
signTransactionConnecting your wallet
It connects to crypto wallets using Phantom, signTransaction and signMessage. Connecting shows the site your wallet address; it doesn't move funds by itself.E9
PhantomsignTransactionsignMessageLoading its content
Its content loads from its own API while you browse (/api/state, /api/feed, /api/pad, /api/top and 1 more).E12E13E14E15E16
/api/state/api/feed/api/pad/api/top/api/houseSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E11
local_storagePages and API calls
Pages it links to
//create/trade/portfolio/how/cEndpoints
Called while loading (seen) or named in the code (code).
| www.useversus.xyz/api/state | seenE12 |
| www.useversus.xyz/api/feed | seenE13 |
| www.useversus.xyz/api/pad | seenE14 |
| www.useversus.xyz/api/top | seenE15 |
| www.useversus.xyz/api/house | seenE16 |
| /api/img/13zKpWypH6BA1qj9sQbgBHdMxUhBd9LCmVric2Ucdevs | codeE17 |
| /api/img/13m8eAQj6xa6iGKJkXhyBRZEMfBADGxqECxygzkQRJvs | codeE18 |
| /api | codeE19 |
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 1 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 CZrAx5SK.