trenchcoat
Free · no sign-up
Website report · 55 min ago

cloaks.fun

“Cloak: launch in the open, hold in the fog”

Template-written 30 evidence items Code reader analysed 19 scripts
What this means for you

cloaks.fun only talked to its own servers while we watched.E1

  • Tech check: the site claims wallet connection, and its public page shows matching evidence.E29E7E27E28
  • We saw no known analytics or advertising services load on the first visit.E1
  • Its code can ask your wallet to sign transactions. Read every wallet pop-up before approving.E27

Tech check

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

Evidence found

Wallet connection

“Cloak Coins Launch Your bag Vault How it works Connect wallet Coins Launch Your bag Vault How it works Launch in the…”E29

Wallet libraries in its code: PhantomE7

Wallet requests in its code: signTransaction, signMessageE27E28

Calls its own backend /api/configE12
Wallet code PhantomE7E27E28
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What it is

  • The Internet Archive first saved this site on 2026-11-05 (9 days ago).E30
  • The site describes itself as: “Launch Solana coins paired with wXMR on pump.fun. Every coin gets a hidden twin, so holders can hide how much they hold.”E2
  • It's built with Next.js and React (common tools for building web apps).E5E6
  • In your browser it stores data in your browser's built-in database, saves small bits of data in your browser and runs compiled WebAssembly code in your browser.E8E9E10
  • It has sections such as /coins, /launch, /bag, /vault, /how and /coin.E26
  • While loading, it called 1 endpoint on its own servers, such as /api/config.E12

Where your data goes

On a first visit the page only talked to its own servers (cloaks.fun).

Crypto and wallets

  • Wallet tools in the code: Phantom.E7
  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E27
  • signMessage: asks a wallet to sign a message.E28

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.E27

signTransaction

Connecting your wallet

It connects to crypto wallets using Phantom, signTransaction and signMessage. Connecting shows the site your wallet address; it doesn't move funds by itself.E7

PhantomsignTransactionsignMessage

Loading its content

Its content loads from its own API while you browse (/api/config).E12

/api/config

Drawing and editing in the browser

The page draws and edits graphics in your browser using WebAssembly and the canvas.E10E11

webassemblycanvas

Saving data on your device

It saves data in your browser (IndexedDB (a browser database) and localStorage), so some things persist between visits.E8E9

indexeddblocal_storage

Pages and API calls

Pages it links to

//coins/launch/bag/vault/how/coin/terms

Endpoints

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

cloaks.fun/api/configseenE12
/api/pulse/buildcodeE13
/api/configcodeE14
/api/imagecodeE15
/api/jupcodeE16
/api/launch/preparecodeE17
/api/metacodeE18
/api/launch/confirmcodeE19
/api/launch/finishcodeE20
/api/trade/buycodeE21
/api/trade/sellcodeE22
/api/faucetcodeE23
/api/sponsorcodeE24
/api/sendcodeE25

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: Cloak: launch in the open, hold in the fog
page title · https://cloaks.fun/
E2
Page description: Launch Solana coins paired with wXMR on pump.fun. Every coin gets a hidden twin, so holders can hide how much they hold.
page description · https://cloaks.fun/
E3
Main heading: Launch in the open. Hold in the fog.
page h1 · https://cloaks.fun/
E4
44 request(s) to cloaks.fun
types: 18 fetch, 15 script, 4 image
GET https://cloaks.fun/ · fetch · 44 requests · network recording
E5
Next.js detected by the code reader (next-runtime)
confidence: high
cloaks.fun/ · “next-runtime” · the code reader
E6
React detected by the code reader (react-runtime)
confidence: medium
cloaks.fun/_next/static/chunks/3794-04350b0fcecd82e5.js · “react-runtime” · the code reader
E7
Phantom found in the code
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 7:20494 · “phantom.app” · pattern scan
E8
Uses the browser ability: indexeddb
stores data in your browser's built-in database
cloaks.fun/_next/static/chunks/9114-a1fad3cf964bf891.js @ 1:1439 · “indexedDB.open(” · pattern scan
E9
Uses the browser ability: local_storage
saves small bits of data in your browser
cloaks.fun/ (page HTML) @ 1:2688 · “localStorage.setItem(” · pattern scan
E10
Uses the browser ability: webassembly
runs compiled WebAssembly code in your browser
cloaks.fun/_next/static/chunks/webpack-9a303b05c7739817.js @ 1:4437 · “WebAssembly.instantiate(” · pattern scan
E11
Uses the browser ability: canvas
draws graphics on a canvas
cloaks.fun/_next/static/chunks/app/page-b317e2209ae5048e.js @ 1:14523 · “getContext("2d"” · pattern scan
E12
The page called /api/config on cloaks.fun (GET)
GET https://cloaks.fun/api/config · fetch · network recording
E13
Code reader found the endpoint /api/pulse/build
how: call:fetch
cloaks.fun/_next/static/chunks/2704-eec1071ef6fd7ffb.js @ 1:36035 · “/api/pulse/build” · the code reader
E14
Code reader found the endpoint /api/config
how: call:fetch
cloaks.fun/_next/static/chunks/9114-a1fad3cf964bf891.js @ 1:28701 · “/api/config” · the code reader
E15
The code names the endpoint /api/image
cloaks.fun/_next/static/chunks/app/page-b317e2209ae5048e.js @ 1:5423 · “/api/image” · pattern scan
E16
The code names the endpoint /api/jup
cloaks.fun/_next/static/chunks/9114-a1fad3cf964bf891.js @ 1:5916 · “/api/jup” · pattern scan
E17
The code names the endpoint /api/launch/prepare
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 1:39557 · “/api/launch/prepare” · pattern scan
E18
The code names the endpoint /api/meta
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 1:39715 · “/api/meta” · pattern scan
E19
The code names the endpoint /api/launch/confirm
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 1:41307 · “/api/launch/confirm” · pattern scan
E20
The code names the endpoint /api/launch/finish
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 1:41633 · “/api/launch/finish” · pattern scan
E21
The code names the endpoint /api/trade/buy
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 1:42942 · “/api/trade/buy” · pattern scan
E22
The code names the endpoint /api/trade/sell
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 1:43473 · “/api/trade/sell” · pattern scan
E23
The code names the endpoint /api/faucet
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 1:55452 · “/api/faucet” · pattern scan
E24
The code names the endpoint /api/sponsor
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 7:2536 · “/api/sponsor” · pattern scan
E25
The code names the endpoint /api/send
cloaks.fun/_next/static/chunks/6842-ffbbef3277720423.js @ 7:2551 · “/api/send” · pattern scan
E26
9 links to pages on the same site
page links · https://cloaks.fun/ · /, /coins, /launch, /bag, /vault, /how, /coin, /terms
E27
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
cloaks.fun/_next/static/chunks/7168-1ad78fddd91f144d.js @ 1:25478 · “signTransaction” · pattern scan
E28
Wallet request in code: signMessage
asks a wallet to sign a message
cloaks.fun/_next/static/chunks/7168-1ad78fddd91f144d.js @ 1:26083 · “signMessage” · pattern scan
E29
The site says: “Cloak Coins Launch Your bag Vault How it works Connect wallet Coins Launch Your bag Vault How it works Launch in the…”
page text · https://cloaks.fun/ · Cloak Coins Launch Your bag Vault How it works Connect wallet Coins Launch Your bag Vault How it works Launch in the…
E30
The Internet Archive first saved cloaks.fun on 2026-11-05 and has snapshots from 2 different days
page web archive · https://web.archive.org/web/20261105043751/cloaks.fun

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 18 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 yN3qzomr.