Website report · 17 Oct 2026
eggwar.fun
“Eggwar · crack eggs, get paid”
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).
What it is
- The site describes itself as: “Eggwar is a first-person egg shooter in the browser. Twelve eggs, four minutes, four modes, the top three split the match's prize in SOL. Fr”E2
- Notable building blocks in its code: Three.js (3D graphics).E6
- 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.E8E9E10
- It has sections such as /docs.E28
- While loading, it called 2 endpoints on its own servers, such as /api/social/boards and /api/social/me.E12E13
Where your data goes
On a first visit the page only talked to its own servers (eggwar.fun).
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.E29
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.E7
PhantomsignTransactionSign-in and accounts
Sign-in and account features show up in its code or traffic (/api/account).E27
/api/accountLive updates
It keeps live connections open (WebSockets) so content updates without reloading.E10
websocketLoading its content
Its content loads from its own API while you browse (/api/social/boards and /api/social/me).E12E13
/api/social/boards/api/social/meCookies and storage
Names only. We never store the values.
localStorageE5: yolk.pid
Pages and API calls
Pages it links to
//docsEndpoints
Called while loading (seen) or named in the code (code).
| eggwar.fun/api/social/boards | seenE12 |
| eggwar.fun/api/social/me | seenE13 |
| /api/shop | codeE14 |
| /api/shop/order | codeE15 |
| /api/shop/blockhash | codeE16 |
| /api/shop/paid | codeE17 |
| /api/shop/check | codeE18 |
| /api/social/boards | codeE19 |
| /api/clientlog | codeE20 |
| /api/clientperf | codeE21 |
| /api/live | codeE22 |
| /api/social/me | codeE23 |
| /api/social/add | codeE24 |
| /api/social/answer | codeE25 |
| /api/social/remove | codeE26 |
| /api/account | codeE27 |
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: Eggwar · crack eggs, get paid
page title · https://eggwar.fun/
E2
Page description: Eggwar is a first-person egg shooter in the browser. Twelve eggs, four minutes, four modes, the top three split the match's prize in SOL. Free: paste
page description · https://eggwar.fun/
E3
Main heading: Crack eggs.
Get paid.
page h1 · https://eggwar.fun/
E4
66 request(s) to eggwar.fun
types: 33 script, 24 image, 4 font
GET https://eggwar.fun/ · script · 66 requests · network recording
E5
localStorage: 1 key(s) saved in your browser
localStorage keys: yolk.pid · values not stored
E6
Three.js (3D graphics) found in the code
eggwar.fun/ (page HTML) @ 14:71 · “three.module” · pattern scan
E7
Phantom found in the code
eggwar.fun/js/armory.js @ 22:28 · “window.phantom” · pattern scan
E8
Uses the browser ability: clipboard_write
can copy text to your clipboard
eggwar.fun/js/social.js @ 66:95 · “clipboard.writeText(” · pattern scan
E9
Uses the browser ability: local_storage
saves small bits of data in your browser
eggwar.fun/js/main.js @ 29:144 · “localStorage.setItem(” · pattern scan
E10
Uses the browser ability: websocket
keeps a live two-way connection open to a server
eggwar.fun/js/main.js @ 155:14 · “new WebSocket(” · pattern scan
E11
Uses the browser ability: canvas
draws graphics on a canvas
eggwar.fun/js/main.js @ 68:67 · “getContext('webgl2'” · pattern scan
E12
The page called /api/social/boards on eggwar.fun (POST)
POST https://eggwar.fun/api/social/boards · fetch · network recording
E13
The page called /api/social/me on eggwar.fun (POST)
POST https://eggwar.fun/api/social/me · fetch · network recording
E14
Code reader found the endpoint /api/shop
how: call:fetch
eggwar.fun/js/armory.js @ 37:26 · “/api/shop” · The code reader analyze-web-bundle 6.4.0
E15
Code reader found the endpoint /api/shop/order
how: call:post
eggwar.fun/js/armory.js @ 81:30 · “/api/shop/order” · The code reader analyze-web-bundle 6.4.0
E16
Code reader found the endpoint /api/shop/blockhash
how: call:post
eggwar.fun/js/armory.js @ 83:23 · “/api/shop/blockhash” · The code reader analyze-web-bundle 6.4.0
E17
Code reader found the endpoint /api/shop/paid
how: call:post
eggwar.fun/js/armory.js @ 96:12 · “/api/shop/paid” · The code reader analyze-web-bundle 6.4.0
E18
Code reader found the endpoint /api/shop/check
how: call:post
eggwar.fun/js/armory.js @ 104:28 · “/api/shop/check” · The code reader analyze-web-bundle 6.4.0
E19
Code reader found the endpoint /api/social/boards
how: call:fetch
eggwar.fun/js/lobby.js @ 41:35 · “/api/social/boards” · The code reader analyze-web-bundle 6.4.0
E20
Code reader found the endpoint /api/clientlog
how: call:fetch
eggwar.fun/js/main.js @ 25:59 · “/api/clientlog” · The code reader analyze-web-bundle 6.4.0
E21
Code reader found the endpoint /api/clientperf
how: call:fetch
eggwar.fun/js/main.js @ 56:23 · “/api/clientperf” · The code reader analyze-web-bundle 6.4.0
E22
Code reader found the endpoint /api/live
how: call:fetch
eggwar.fun/js/main.js @ 122:65 · “/api/live” · The code reader analyze-web-bundle 6.4.0
E23
Code reader found the endpoint /api/social/me
how: call:post
eggwar.fun/js/social.js @ 18:51 · “/api/social/me” · The code reader analyze-web-bundle 6.4.0
E24
Code reader found the endpoint /api/social/add
how: call:post
eggwar.fun/js/social.js @ 65:108 · “/api/social/add” · The code reader analyze-web-bundle 6.4.0
E25
Code reader found the endpoint /api/social/answer
how: call:post
eggwar.fun/js/social.js @ 68:49 · “/api/social/answer” · The code reader analyze-web-bundle 6.4.0
E26
Code reader found the endpoint /api/social/remove
how: call:post
eggwar.fun/js/social.js @ 69:32 · “/api/social/remove” · The code reader analyze-web-bundle 6.4.0
E27
The code names the endpoint /api/account
eggwar.fun/js/main.js @ 130:41 · “/api/account” · pattern scan
E28
2 links to pages on the same site
page links · https://eggwar.fun/ · /, /docs
E29
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
eggwar.fun/js/armory.js @ 92:25 · “signAndSendTransaction” · pattern scan
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 54 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 PVn2sODN.