parisriot.fun
“Paris Riot · Take Paris”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
On-chain / smart contracts
“…blic wallet from the first payday, so every payment is on chain. 03 THE MAP PARIS, LIVE. Every point in its owner's co…”E199
No matching code, calls or services in what loaded for us.
What it is
- The site describes itself as: “Paris in the mayhem. Gangs take the real streets of Paris point by point: the Tower, the bank, the church, the government house, the police ”E2
- Notable building blocks in its code: Three.js (3D graphics).E7
- In your browser it can ask to use your camera or microphone, can copy text to your clipboard, saves small bits of data in your browser, keeps a live two-way connection open to a server and 2 more.E9E10E11E12E13E14
- While loading, it called 60 endpoints on its own servers, such as /media/ui/paris-points.json, /api/war, /media/chars/chars.json and 57 more.E17E18E19E20
Where your data goes
Crypto and wallets
- Wallet tools in the code: wagmi.E8
How key features work
Connecting your wallet
It connects to crypto wallets using wagmi. Connecting shows the site your wallet address; it doesn't move funds by itself.E8
wagmiLive updates
It keeps live connections open (WebSockets and WebRTC) so content updates without reloading.E12E14
websocketwebrtcLoading its content
Its content loads from its own API while you browse (/media/ui/paris-points.json, /api/war, /media/chars/chars.json, /src/paris/data/paris/index.json and 2 more).E17E18E19E20E21
/media/ui/paris-points.json/api/war/media/chars/chars.json/src/paris/data/paris/index.json/src/paris/data/paris/spawns.json/src/paris/data/paris/areas.jsonDrawing and editing in the browser
The page draws and edits graphics in your browser using Three.js (3D graphics), WebAssembly and the canvas.E7E13E16
Three.js (3D graphics)webassemblycanvasSaving 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
/Endpoints
Called while loading (seen) or named in the code (code).
| parisriot.fun/media/ui/paris-points.json | seenE17 |
| parisriot.fun/api/war | seenE18 |
| parisriot.fun/media/chars/chars.json | seenE19 |
| parisriot.fun/src/paris/data/paris/index.json | seenE20 |
| parisriot.fun/src/paris/data/paris/spawns.json | seenE21 |
| parisriot.fun/src/paris/data/paris/areas.json | seenE22 |
| parisriot.fun/src/paris/data/paris/landmarks.json | seenE23 |
| parisriot.fun/src/paris/data/paris/points.json | seenE24 |
| parisriot.fun/src/paris/data/paris/rings.json | seenE25 |
| parisriot.fun/src/paris/data/paris/names.json | seenE26 |
| parisriot.fun/src/paris/data/paris/map.json | seenE27 |
| parisriot.fun/src/paris/riot/zone.json | seenE28 |
| parisriot.fun/src/paris/data/bakes.json | seenE29 |
| parisriot.fun/src/paris/data/full/landmarks.json | seenE30 |
| parisriot.fun/src/paris/data/full/parts.json | seenE31 |
| parisriot.fun/src/paris/data/paris/tiles/-11_1.json | seenE32 |
| parisriot.fun/src/paris/data/paris/tiles/-10_1.json | seenE33 |
| parisriot.fun/src/paris/data/paris/tiles/-11_2.json | seenE34 |
| parisriot.fun/src/paris/data/paris/tiles/-10_0.json | seenE35 |
| parisriot.fun/src/paris/data/paris/tiles/-10_2.json | seenE36 |
| parisriot.fun/src/paris/data/paris/tiles/-11_0.json | seenE37 |
| parisriot.fun/media/paris/landmarks/lm-extra.json | seenE38 |
| parisriot.fun/media/props/crew_van.json | seenE39 |
| parisriot.fun/media/paris/landmarks/lmb-full.json | seenE40 |
| parisriot.fun/media/props/civ_suv.json | seenE41 |
| parisriot.fun/src/war/paris-cover.json | seenE42 |
| parisriot.fun/media/props/police_car.json | seenE43 |
| parisriot.fun/src/paris/data/paris/tiles/-9_2.json | seenE44 |
| parisriot.fun/src/paris/data/paris/tiles/-12_2.json | seenE45 |
| parisriot.fun/src/paris/data/paris/tiles/-9_1.json | seenE46 |
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 51 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 pjYIi89l.