Website report · 30 Oct 2026

www.grokgrid.fun

“GrokGrid”

Template-written 33 evidence items Code reader analysed 5 scripts
What this means for you

www.grokgrid.fun talked to 1 outside service on a first visit.E4

  • We saw no known analytics or advertising services load on the first visit.E1
  • 1 cookie was set in your browser, 1 of them by other companies' domains.E5
  • Its code can ask your wallet to sign transactions. Read every wallet pop-up before approving.E32

Tech check

What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.

The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).

Calls its own backend /api/coins, /api/feed, /api/liveE15E16E17E18
Wallet code WalletConnect / ReownE9E32
Contract calls in its code none seen
Talks to AI services none seen
Live connections can make direct peer-to-peer connections (calls, file sharing)E13

The real tech may live elsewhere. This page links to: github.com/DylanLauren/grokgrid · check the code

What it is

  • The Internet Archive has never saved this site, so it is probably new.E33
  • The site describes itself as: “A Grok Bot with his own phone, his own wallet and the pump.fun app. Watch him trade live. Launch your own.”E2
  • It's built with React (common tools for building web apps).E7
  • Notable building blocks in its code: Three.js (3D graphics).E8
  • In your browser it can copy text to your clipboard, saves small bits of data in your browser, runs compiled WebAssembly code in your browser and can make direct peer-to-peer connections (calls, file sharing).E10E11E12E13
  • While loading, it called 4 endpoints on its own servers, such as /api/coins, /api/feed, /api/live and 1 more.E15E16E17E18

Where your data goes

Crypto & walletsConnect wallets, read blockchains or fetch token prices. 1
cdn.dexscreener.comDexScreener: token prices and pools 33×E4

Crypto and wallets

  • Wallet tools in the code: WalletConnect / Reown.E9
  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E32

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

signTransaction

Connecting your wallet

It connects to crypto wallets using WalletConnect / Reown and signTransaction. Connecting shows the site your wallet address; it doesn't move funds by itself.E9E4

WalletConnect / ReownsignTransaction

Sign-in and accounts

Sign-in and account features show up in its code or traffic (/api/phone-session).E31

/api/phone-session

Live updates

It keeps live connections open (WebRTC) so content updates without reloading.E13

webrtc

Loading its content

Its content loads from its own API while you browse (/api/coins, /api/feed, /api/live and /api/screen).E15E16E17E18

/api/coins/api/feed/api/live/api/screen

Drawing and editing in the browser

The page draws and edits graphics in your browser using Three.js (3D graphics) and WebAssembly.E8E12

Three.js (3D graphics)webassembly

Saving data on your device

It saves data in your browser (localStorage and sessionStorage), so some things persist between visits.E11E6

local_storagesessionStorage

Cookies and storage

Names only. We never store the values.

CookieSet forKeptWhose
__cf_bmE5dexscreener.com about 0 daysother company

sessionStorageE6: gg-intro

Pages and API calls

Endpoints

Called while loading (seen) or named in the code (code).

www.grokgrid.fun/api/coinsseenE15
www.grokgrid.fun/api/feedseenE16
www.grokgrid.fun/api/liveseenE17
www.grokgrid.fun/api/screenseenE18
/api/coinscodeE19
/api/feedcodeE20
/api/agentscodeE21
/api/livecodeE22
/api/tokencodeE23
/api/statuscodeE24
/api/launch/confirmcodeE25
/api/botcodeE26
/api/launch/assetcodeE27
/api/launch/preparecodeE28
/api/launch/sendcodeE29
/api/launch/statuscodeE30
/api/phone-sessioncodeE31

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.

E1
Page title: GrokGrid
page title · https://www.grokgrid.fun/
E2
Page description: A Grok Bot with his own phone, his own wallet and the pump.fun app. Watch him trade live. Launch your own.
page description · https://www.grokgrid.fun/
E3
28 request(s) to www.grokgrid.fun
types: 16 fetch, 5 script, 2 font
GET https://www.grokgrid.fun/ · fetch · 28 requests · network recording
E4
33 request(s) to cdn.dexscreener.com
types: 33 image
GET https://cdn.dexscreener.com/cms/images/RSLqRr5vubt1aRKX · image · 33 requests · network recording
E5
Cookie '__cf_bm' set for dexscreener.com
kept for about 0 days
cookie __cf_bm on dexscreener.com · value not stored
E6
sessionStorage: 1 key(s) saved in your browser
sessionStorage keys: gg-intro · values not stored
E7
React detected by the code reader (react-runtime)
confidence: medium
www.grokgrid.fun/assets/react-COjebZfb.js · “react-runtime” · the code reader
E8
Three.js (3D graphics) found in the code
www.grokgrid.fun/assets/three-Cs-wTcCc.js @ 5:147583 · “WebGLRenderer” · pattern scan
E9
WalletConnect / Reown found in the code
www.grokgrid.fun/assets/index-C0moV9sr.js @ 1:1283 · “WalletConnect” · pattern scan
E10
Uses the browser ability: clipboard_write
can copy text to your clipboard
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:67164 · “clipboard.writeText(” · pattern scan
E11
Uses the browser ability: local_storage
saves small bits of data in your browser
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:30999 · “localStorage.setItem(” · pattern scan
E12
Uses the browser ability: webassembly
runs compiled WebAssembly code in your browser
www.grokgrid.fun/assets/three-Cs-wTcCc.js @ 4419:21152 · “WebAssembly.instantiate(” · pattern scan
E13
Uses the browser ability: webrtc
can make direct peer-to-peer connections (calls, file sharing)
www.grokgrid.fun/assets/Scene-lkYnfgkb.js @ 1:771 · “new RTCPeerConnection(” · pattern scan
E14
Uses the browser ability: web_worker
runs work in a background thread
www.grokgrid.fun/assets/three-Cs-wTcCc.js @ 4419:185 · “new Worker(” · pattern scan
E15
The page called /api/coins on www.grokgrid.fun (GET)
GET https://www.grokgrid.fun/api/coins · fetch · network recording
E16
The page called /api/feed on www.grokgrid.fun (GET)
GET https://www.grokgrid.fun/api/feed · fetch · network recording
E17
The page called /api/live on www.grokgrid.fun (GET)
GET https://www.grokgrid.fun/api/live · fetch · network recording
E18
The page called /api/screen on www.grokgrid.fun (GET)
GET https://www.grokgrid.fun/api/screen · fetch · network recording
E19
Code reader found the endpoint /api/coins
how: call:fetch
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:11696 · “/api/coins” · the code reader
E20
Code reader found the endpoint /api/feed
how: call:fetch
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:14050 · “/api/feed” · the code reader
E21
Code reader found the endpoint /api/agents
how: call:fetch
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:28148 · “/api/agents” · the code reader
E22
Code reader found the endpoint /api/live
how: call:fetch
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:29603 · “/api/live” · the code reader
E23
Code reader found the endpoint /api/token
how: call:fetch
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:38329 · “/api/token” · the code reader
E24
Code reader found the endpoint /api/status
how: call:fetch
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:38637 · “/api/status” · the code reader
E25
Code reader found the endpoint /api/launch/confirm
how: call:fetch
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:83422 · “/api/launch/confirm” · the code reader
E26
The code names the endpoint /api/bot
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:67714 · “/api/bot” · pattern scan
E27
The code names the endpoint /api/launch/asset
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:82227 · “/api/launch/asset” · pattern scan
E28
The code names the endpoint /api/launch/prepare
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:82341 · “/api/launch/prepare” · pattern scan
E29
The code names the endpoint /api/launch/send
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:83248 · “/api/launch/send” · pattern scan
E30
The code names the endpoint /api/launch/status
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:85216 · “/api/launch/status” · pattern scan
E31
The code names the endpoint /api/phone-session
www.grokgrid.fun/assets/Scene-lkYnfgkb.js @ 1:4409 · “/api/phone-session” · pattern scan
E32
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
www.grokgrid.fun/assets/index-C0moV9sr.js @ 2:81801 · “signTransaction” · pattern scan
E33
The Internet Archive has no saved copy of grokgrid.fun
page web archive · https://web.archive.org/web/*/grokgrid.fun

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).
  • 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 3 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 TEwSpzWr.