pumpprotest.fun
“PumpProtest — Make some noise.”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
Wallet connection
“…OTEST™ PARIS, FRANCE 48.8566° N, 2.3522° E YOUR AVATAR CONNECT WALLET ✳ THE STREETS ARE YOURS. PumpProtest MAKE A SIGN. MAKE…”E26
No matching code, calls or services in what loaded for us.
What it is
- The site describes itself as: “Welcome to PumpProtest. An unruly Paris street, a cardboard sign, and something to say. Enter the playable protest sandbox.”E2
- Notable building blocks in its code: Three.js (3D graphics).E7
- In your browser it can ask to use your camera or microphone, 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.E8E9E10E11E12
- While loading, it called 7 endpoints on its own servers, such as /api/event, /map/resistance-metadata.json, /map/resistance-fallbacks.json and 4 more.E15E16E17E18
Where your data goes
How key features work
Sign-in and accounts
Sign-in and account features show up in its code or traffic (/api/admin/session).E23
/api/admin/sessionLive updates
It keeps live connections open (WebSockets and WebRTC) so content updates without reloading.E10E12
websocketwebrtcLoading its content
Its content loads from its own API while you browse (/api/event, /map/resistance-metadata.json, /map/resistance-fallbacks.json, /map/resistance-props-metadata.json and 2 more).E15E16E17E18E19
/api/event/map/resistance-metadata.json/map/resistance-fallbacks.json/map/resistance-props-metadata.json/map/resistance-routes.json/map/resistance-navigation.jsonDrawing and editing in the browser
The page draws and edits graphics in your browser using Three.js (3D graphics), WebAssembly and the canvas.E7E11E14
Three.js (3D graphics)webassemblycanvasSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E9
local_storagePages and API calls
Pages it links to
/Endpoints
Called while loading (seen) or named in the code (code).
| pumpprotest.fun/api/event | seenE15 |
| pumpprotest.fun/map/resistance-metadata.json | seenE16 |
| pumpprotest.fun/map/resistance-fallbacks.json | seenE17 |
| pumpprotest.fun/map/resistance-props-metadata.json | seenE18 |
| pumpprotest.fun/map/resistance-routes.json | seenE19 |
| pumpprotest.fun/map/resistance-navigation.json | seenE20 |
| pumpprotest.fun/version.json | seenE21 |
| /version.json | codeE22 |
| /api/admin/session | codeE23 |
| /api/admin/event | codeE24 |
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 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 EJAd8dlT.