trychip.fun
“Chip”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
Staking / yield
“…orIdle Run chip Window #9850:00 left Compute rate 0H/s Reward pool 0.0357SOL SOL delivered 0.0000SOL $CHIPDock…chip 70% m…”E28
No matching code, calls or services in what loaded for us.
What it is
- The Internet Archive has never saved this site, so it is probably new.E29
- The site describes itself as: “Put your chip to work. Mine SOL in your browser, paid from coin fees.”E2
- It's built with Next.js and React (common tools for building web apps).E7E8
- Notable building blocks in its code: Three.js (3D graphics).E9
- 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, runs compiled WebAssembly code in your browser and 1 more.E11E12E13E14E15
- It has sections such as /launch, /explore, /earnings, /treasury, /ledger and /network.E25E26
- While loading, it called 1 endpoint on its own servers, such as /api/state.E17
Where your data goes
Not identifiedServices we don't have in our list yet. 1
| worker-production-80b5ef1a.up.railway.app | not identified | 1×E6 |
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.E27
signTransactionConnecting your wallet
It connects to crypto wallets using Phantom and signTransaction. Connecting shows the site your wallet address; it doesn't move funds by itself.E10
PhantomsignTransactionLive updates
It keeps live connections open (WebSockets and worker-production-80b5ef1a.up.railway.app) so content updates without reloading.E13E6
websocketworker-production-80b5ef1a.up.railway.appDrawing and editing in the browser
The page draws and edits graphics in your browser using Three.js (3D graphics), WebAssembly and the canvas.E9E14E16
Three.js (3D graphics)webassemblycanvasSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E12
local_storagePages and API calls
Pages it links to
//launch/explore/earnings/treasury/ledger/network/rules/_next/imageEvidence
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 13 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 ue2SpNix.