trenchcoat
Free · no sign-up
Website report · 03 Nov 2026

www.xlooong.fun

“Long Monero”

Template-written 21 evidence items Code reader analysed 13 scripts
What this means for you

Long Monero talked to 1 outside service on a first visit.E6

  • An AI agent used the site and saw 1 of 2 claimed features working.E14E16E18E19E21E16
  • Claims the pump.fun XMR fees, swaps them to SOL, and sends that SOL into the XMR long on Hyperliquid.: The page and its /api/xmr endpoint showed live data: claimable fees rose from 0.000097 to 0.000232 XMR, plus the XMR price and Hyperliquid market stats. Across a full 'NEXT CLAIM' countdown, though, the fees were not claimed or reset, collateral stayed at $0.00, the Hyperliquid address field was empty, and position was null ('No XMR long open'). I could not see the swap to SOL or any long positionE14E16E18E19E21
  • Extra observation: live market and fee data: Each page load called www.xlooong.fun/api/xmr, which returned live XMR price, funding rate, open interest, max leverage 5 and a claimable fee amount that went up over time. The page also read a contract address from a Firebase database (eccomerceapp-4c533-default-rtdb.firebaseio.com/ca.json).E16E18E19E21
  • Tech check: the site mentions trading / swaps / bots, but we found nothing behind it in what its public page loads.E12
  • We saw no known analytics or advertising services load on the first visit.E1

Tech check

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

Nothing found on the public page

Trading / swaps / bots

“PIKA FEES Long Monero Claims the pump.fun XMR fees, swaps them to SOL, and sends that SOL into the XMR long on H…”E12

No matching code, calls or services in what loaded for us.

Calls its own backend /api/xmrE10
Wallet code none seen
Contract calls in its code none seen
Talks to AI services none seen
Live connections receives a live stream of updates from a serverE9

What the AI agent tried

An AI agent (claude-opus-5-5) used the site in our sandbox for 8 steps and saw 1 of 2 claimed features working. It can't connect a wallet, pay, sign or log in, so those features count as "couldn't test". What it reports is what it observed, not a verdict.

Not seen working

Claims the pump.fun XMR fees, swaps them to SOL, and sends that SOL into the XMR long on Hyperliquid.

The page and its /api/xmr endpoint showed live data: claimable fees rose from 0.000097 to 0.000232 XMR, plus the XMR price and Hyperliquid market stats. Across a full 'NEXT CLAIM' countdown, though, the fees were not claimed or reset, collateral stayed at $0.00, the Hyperliquid address field was empty, and position was null ('No XMR long open'). I could not see the swap to SOL or any long positionE14E16E18E19E21

Seen working

Extra observation: live market and fee data

Each page load called www.xlooong.fun/api/xmr, which returned live XMR price, funding rate, open interest, max leverage 5 and a claimable fee amount that went up over time. The page also read a contract address from a Firebase database (eccomerceapp-4c533-default-rtdb.firebaseio.com/ca.json).E16E18E19E21

What it is

  • The Internet Archive has never saved this site, so it is probably new.E13
  • The site describes itself as: “Pika fees into an XMR long on Hyperliquid.”E2
  • It's built with Next.js and React (common tools for building web apps).E7E8
  • In your browser it receives a live stream of updates from a server.E9
  • While loading, it called 1 endpoint on its own servers, such as /api/xmr.E10

Where your data goes

Backend & data servicesDatabases, search and APIs the app runs on. 1
eccomerceapp-4c533-default-rtdb.firebaseio.comFirebase / Google Cloud: app database and hosting 1×E6

How key features work

Live updates

It keeps live connections open (server-sent events) so content updates without reloading.E9

event_source

Loading its content

Its content loads from its own API while you browse (/api/xmr).E10

/api/xmr

Pages and API calls

Endpoints

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

www.xlooong.fun/api/xmrseenE10
/api/xmrcodeE11

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: Long Monero
page title · https://www.xlooong.fun/
E2
Page description: Pika fees into an XMR long on Hyperliquid.
page description · https://www.xlooong.fun/
E3
Site name: Long Monero
page site_name · https://www.xlooong.fun/
E4
Main heading: Long Monero
page h1 · https://www.xlooong.fun/
E5
12 request(s) to www.xlooong.fun
types: 5 script, 3 stylesheet, 2 image
GET https://www.xlooong.fun/ · script · 12 requests · network recording
E6
1 request(s) to eccomerceapp-4c533-default-rtdb.firebaseio.com
types: 1 eventsource
GET https://eccomerceapp-4c533-default-rtdb.firebaseio.com/ca.json · eventsource · network recording
E7
Next.js detected by the code reader (next-runtime)
confidence: high
www.xlooong.fun/ · “next-runtime” · The code reader analyze-web-bundle 6.4.0
E8
React detected by the code reader (react-runtime)
confidence: medium
www.xlooong.fun/_next/static/chunks/4bd1b696-f6bedae49f0827a5.js · “react-runtime” · The code reader analyze-web-bundle 6.4.0
E9
Uses the browser ability: event_source
receives a live stream of updates from a server
www.xlooong.fun/_next/static/chunks/app/page-cd407a81bf8cf199.js @ 1:637 · “new EventSource(” · pattern scan
E10
The page called /api/xmr on www.xlooong.fun (GET)
GET https://www.xlooong.fun/api/xmr · fetch · network recording
E11
Code reader found the endpoint /api/xmr
how: call:fetch
www.xlooong.fun/_next/static/chunks/app/page-cd407a81bf8cf199.js @ 1:548 · “/api/xmr” · The code reader analyze-web-bundle 6.4.0
E12
The site says: “PIKA FEES Long Monero Claims the pump.fun XMR fees, swaps them to SOL, and sends that SOL into the XMR long on H…”
page text · https://www.xlooong.fun/ · PIKA FEES Long Monero Claims the pump.fun XMR fees, swaps them to SOL, and sends that SOL into the XMR long on H…
E13
The Internet Archive has no saved copy of xlooong.fun
page web archive · https://web.archive.org/web/*/xlooong.fun
E14
Agent step 1: view
AI agent step 1 · view on /
E15
Agent step 2: view
AI agent step 2 · view on /
E16
Agent step 3: go /
AI agent step 3 · go on / · page called GET www.xlooong.fun/api/xmr, GET eccomerceapp-4c533-default-rtdb.firebaseio.com/ca.json
E17
Agent step 4: view
AI agent step 4 · view on /
E18
Agent step 5: go /api/xmr
AI agent step 5 · go on /api/xmr
E19
Agent step 6: go /
AI agent step 6 · go on / · page called GET www.xlooong.fun/api/xmr, GET eccomerceapp-4c533-default-rtdb.firebaseio.com/ca.json
E20
Agent step 7: view
AI agent step 7 · view on /
E21
Agent step 8: go /api/xmr
AI agent step 8 · go on /api/xmr

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.
  • The code reader hit its size budget on parts of 2 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 jLQ5NQp6.