pillees.fun
“Pillees”
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).
The real tech may live elsewhere. This page links to: github.com/buenoyed/pillees · check the code
What it is
- The site describes itself as: “Pillees launches autonomous arbitrage bots on Pump. Routes use PumpSwap multi_hop_swap: several hops, one instruction, fees once.”E2
- It's built with React (common tools for building web apps).E6
- In your browser it saves small bits of data in your browser.E8
- It has sections such as /leaderboard, /markets, /profile, /protocol, /docs and /pump.E23
- While loading, it called 2 endpoints on its own servers, such as /api/coins and /api/bots.E10E11
Where your data goes
Crypto and wallets
How key features work
Connecting your wallet
It connects to crypto wallets using Phantom and signMessage. Connecting shows the site your wallet address; it doesn't move funds by itself.E7
PhantomsignMessageLoading its content
Its content loads from its own API while you browse (/api/coins and /api/bots).E10E11
/api/coins/api/botsDrawing and editing in the browser
The page draws and edits graphics in your browser using the canvas.E9
canvasSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E8
local_storagePages and API calls
Pages it links to
//leaderboard/markets/profile/protocol/docs/pump/sdk/launch/bots/runEndpoints
Called while loading (seen) or named in the code (code).
| pillees.fun/api/coins | seenE10 |
| pillees.fun/api/bots | seenE11 |
| /api/bots/ilbuipYU/logo | codeE12 |
| /api/bots/KB22CCaK/logo | codeE13 |
| /api/bots/HCEEHhdF/logo | codeE14 |
| /api/bots/QoBBFKgx/logo | codeE15 |
| /api/bots/HMm7M3Jr/logo | codeE16 |
| /api/coins/5aeCFDmXQzrbatAFGeQ98oMVgoVd2Z9LF3qvtafr18Hm/image | codeE17 |
| /api/coins/A5KBjTwzVJtp2AWEMRKLraiukvAvVgeXQ15trgdBnLgj/image | codeE18 |
| /api/coins/5WHC3F74JTNgRNmsDfCvPTJZaJvMff9ZtkgqMGefq8Rc/image | codeE19 |
| /api/coins/3ozVDrgqUzxSZLK2aFMBJYDpwLDHcnm7axB8LSVQ5Tyr/image | codeE20 |
| /api/coins/9ZBuNvy4hFpBvmzJytHzNdcR5rUw7TfxGCFQdYYPJTNx/image | codeE21 |
| /api/coins/BiU3W5rUrh8JNmxDk8gDN2UUGRAHiFAax7kPi8C2qKX5/image | codeE22 |
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).
- 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 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 5k2Fhbq2.