trenchcoat
Free · no sign-up
Website report · 2 h ago

useprivate.fun

“Private · Public coins. Private payouts.”

Template-written 45 evidence items Code reader analysed 1 scripts
What this means for you

Private only talked to its own servers while we watched.E1

  • An AI agent used the site and saw 1 of 2 claimed features working.E43E45E42E44
  • Staking / yield: The coin list and the 'Top yield' tab loaded from /api/coins. Top yield was empty, and the ZCAT coin page showed 0 ZEC paid to holders and an empty pot. Getting hourly ZEC payouts would mean buying and holding coins with a wallet, so I couldn't test it.E43E45
  • A working app / platform: The platform pages loaded live data from its API: market caps, a list of recent trades with Solscan links, a safety check and a buy/sell panel, which asks you to connect a wallet. The $PRIVATE buyback-and-burn section showed 0 ZEC spent and 0 tokens burned, so I didn't see any burns.E42E44E45
  • Also noticed, Payout stats are all zero: The homepage shows 1 coin live, 0 ZEC paid to holders and 0 wallets paid. The 'Private payouts' feature is labelled 'Coming soon'.E42
  • Tech check: the site claims a working app / platform, and its public page shows matching evidence.E40E11E12E13
  • Tech check: the site mentions staking / yield, but we found nothing behind it in what its public page loads.E39
  • 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.E37

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

Staking / yield

“…random minutes, from $10 held. Coins New Trending Top yield About to graduate Graduated Biggest payouts Watchlist…”E39

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

Evidence found

A working app / platform

“…aid to holders 0wallets paid $1,271.23per ZEC $PRIVATE Platform coin A cut of every trade here buys it back and burns…”E40

Calls to its own backend: /api/health, /api/stats, /api/coinsE11E12E13E14

Live connections: receives a live stream of updates from a serverE9

Calls its own backend /api/health, /api/stats, /api/coinsE11E12E13E14
Wallet code signTransaction, signMessageE37E38
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 4 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.

Couldn't test

Staking / yield

The coin list and the 'Top yield' tab loaded from /api/coins. Top yield was empty, and the ZCAT coin page showed 0 ZEC paid to holders and an empty pot. Getting hourly ZEC payouts would mean buying and holding coins with a wallet, so I couldn't test it.E43E45

Seen working

A working app / platform

The platform pages loaded live data from its API: market caps, a list of recent trades with Solscan links, a safety check and a buy/sell panel, which asks you to connect a wallet. The $PRIVATE buyback-and-burn section showed 0 ZEC spent and 0 tokens burned, so I didn't see any burns.E42E44E45

Also noticed

Things the agent saw along the way that aren't among the site's claims. Not counted above.

Noticed

Payout stats are all zero

The homepage shows 1 coin live, 0 ZEC paid to holders and 0 wallets paid. The 'Private payouts' feature is labelled 'Coming soon'.E42

What it is

  • The Internet Archive has never saved this site, so it is probably new.E41
  • The site describes itself as: “Launch a coin on pump.fun. Its holders are paid in ZEC every hour, nothing to claim.”E2
  • It's built with React and Remix / React Router (common tools for building web apps).E6E7
  • In your browser it saves small bits of data in your browser, receives a live stream of updates from a server and can open your device's share menu.E8E9E10
  • It has sections such as /leverage, /wallet, /token, /launch and /coin.E36
  • While loading, it called 7 endpoints on its own servers, such as /api/health, /api/stats, /api/coins and 4 more.E11E12E13E14

Where your data goes

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

Crypto and wallets

  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E37
  • signMessage: asks a wallet to sign a message.E38

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

signTransaction

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/health, /api/stats, /api/coins, /api/fees and 2 more).E11E12E13E14E15

/api/health/api/stats/api/coins/api/fees/api/payouts/recent/api/featured

Search

Search runs through /api/coins/search.E18

/api/coins/search

Saving data on your device

It saves data in your browser (localStorage), so some things persist between visits.E8

local_storage

Pages and API calls

Pages it links to

//leverage/wallet/token/launch/coin

Endpoints

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

useprivate.fun/api/healthseenE11
useprivate.fun/api/statsseenE12
useprivate.fun/api/coinsseenE13
useprivate.fun/api/feesseenE14
useprivate.fun/api/payouts/recentseenE15
useprivate.fun/api/featuredseenE16
useprivate.fun/api/zpadseenE17
/api/coins/searchcodeE18
/api/uploads/imagecodeE19
/api/launch/preparecodeE20
/api/launch/submitcodeE21
/api/trade/quotecodeE22
/api/trade/preparecodeE23
/api/trade/submitcodeE24
/api/private/noncecodeE25
/api/private/linkcodeE26
/api/private/unlinkcodeE27
/api/private/viewcodeE28
/api/lever/accesscodeE29
/api/lever/vaultcodeE30
/api/lever/listingscodeE31
/api/lever/quotecodeE32
/api/lever/preparecodeE33
/api/lever/submitcodeE34
/api/livecodeE35

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: Private · Public coins. Private payouts.
page title · https://useprivate.fun/
E2
Page description: Launch a coin on pump.fun. Its holders are paid in ZEC every hour, nothing to claim.
page description · https://useprivate.fun/
E3
Site name: Private
page site_name · https://useprivate.fun/
E4
Main heading: Public coins. Private payouts.
page h1 · https://useprivate.fun/
E5
17 request(s) to useprivate.fun
types: 10 fetch, 2 font, 1 document
GET https://useprivate.fun/ · fetch · 17 requests · network recording
E6
React detected by the code reader (react-runtime)
confidence: medium
useprivate.fun/assets/index-B-T71hvv.js · “react-runtime” · the code reader
E7
Remix / React Router found in the code
useprivate.fun/assets/index-B-T71hvv.js @ 11:12891 · “__reactRouterContext” · pattern scan
E8
Uses the browser ability: local_storage
saves small bits of data in your browser
useprivate.fun/assets/index-B-T71hvv.js @ 12:78809 · “localStorage.setItem(” · pattern scan
E9
Uses the browser ability: event_source
receives a live stream of updates from a server
useprivate.fun/assets/index-B-T71hvv.js @ 11:46308 · “new EventSource(” · pattern scan
E10
Uses the browser ability: web_share
can open your device's share menu
useprivate.fun/assets/index-B-T71hvv.js @ 13:13287 · “navigator.share(” · pattern scan
E11
The page called /api/health on useprivate.fun (GET)
GET https://useprivate.fun/api/health · fetch · network recording
E12
The page called /api/stats on useprivate.fun (GET)
GET https://useprivate.fun/api/stats · fetch · network recording
E13
The page called /api/coins on useprivate.fun (GET)
GET https://useprivate.fun/api/coins · fetch · network recording
E14
The page called /api/fees on useprivate.fun (GET)
GET https://useprivate.fun/api/fees · fetch · network recording
E15
The page called /api/payouts/recent on useprivate.fun (GET)
GET https://useprivate.fun/api/payouts/recent · fetch · network recording
E16
The page called /api/featured on useprivate.fun (GET)
GET https://useprivate.fun/api/featured · fetch · network recording
E17
The page called /api/zpad on useprivate.fun (GET)
GET https://useprivate.fun/api/zpad · fetch · network recording
E18
The code names the endpoint /api/coins/search
useprivate.fun/assets/index-B-T71hvv.js @ 11:27687 · “/api/coins/search” · pattern scan
E19
The code names the endpoint /api/uploads/image
useprivate.fun/assets/index-B-T71hvv.js @ 11:28106 · “/api/uploads/image” · pattern scan
E20
The code names the endpoint /api/launch/prepare
useprivate.fun/assets/index-B-T71hvv.js @ 11:28224 · “/api/launch/prepare” · pattern scan
E21
The code names the endpoint /api/launch/submit
useprivate.fun/assets/index-B-T71hvv.js @ 11:28268 · “/api/launch/submit” · pattern scan
E22
The code names the endpoint /api/trade/quote
useprivate.fun/assets/index-B-T71hvv.js @ 11:28327 · “/api/trade/quote” · pattern scan
E23
The code names the endpoint /api/trade/prepare
useprivate.fun/assets/index-B-T71hvv.js @ 11:28370 · “/api/trade/prepare” · pattern scan
E24
The code names the endpoint /api/trade/submit
useprivate.fun/assets/index-B-T71hvv.js @ 11:28418 · “/api/trade/submit” · pattern scan
E25
The code names the endpoint /api/private/nonce
useprivate.fun/assets/index-B-T71hvv.js @ 11:28545 · “/api/private/nonce” · pattern scan
E26
The code names the endpoint /api/private/link
useprivate.fun/assets/index-B-T71hvv.js @ 11:28607 · “/api/private/link” · pattern scan
E27
The code names the endpoint /api/private/unlink
useprivate.fun/assets/index-B-T71hvv.js @ 11:28652 · “/api/private/unlink” · pattern scan
E28
The code names the endpoint /api/private/view
useprivate.fun/assets/index-B-T71hvv.js @ 11:28697 · “/api/private/view” · pattern scan
E29
The code names the endpoint /api/lever/access
useprivate.fun/assets/index-B-T71hvv.js @ 11:28741 · “/api/lever/access” · pattern scan
E30
The code names the endpoint /api/lever/vault
useprivate.fun/assets/index-B-T71hvv.js @ 11:28779 · “/api/lever/vault” · pattern scan
E31
The code names the endpoint /api/lever/listings
useprivate.fun/assets/index-B-T71hvv.js @ 11:28819 · “/api/lever/listings” · pattern scan
E32
The code names the endpoint /api/lever/quote
useprivate.fun/assets/index-B-T71hvv.js @ 11:28910 · “/api/lever/quote” · pattern scan
E33
The code names the endpoint /api/lever/prepare
useprivate.fun/assets/index-B-T71hvv.js @ 11:28953 · “/api/lever/prepare” · pattern scan
E34
The code names the endpoint /api/lever/submit
useprivate.fun/assets/index-B-T71hvv.js @ 11:29001 · “/api/lever/submit” · pattern scan
E35
The code names the endpoint /api/live
useprivate.fun/assets/index-B-T71hvv.js @ 11:44002 · “/api/live” · pattern scan
E36
6 links to pages on the same site
page links · https://useprivate.fun/ · /, /leverage, /wallet, /token, /launch, /coin
E37
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
useprivate.fun/assets/index-B-T71hvv.js @ 12:877 · “signTransaction” · pattern scan
E38
Wallet request in code: signMessage
asks a wallet to sign a message
useprivate.fun/assets/index-B-T71hvv.js @ 12:1944 · “signMessage” · pattern scan
E39
The site says: “…random minutes, from $10 held. Coins New Trending Top yield About to graduate Graduated Biggest payouts Watchlist…”
page text · https://useprivate.fun/ · …random minutes, from $10 held. Coins New Trending Top yield About to graduate Graduated Biggest payouts Watchlist…
E40
The site says: “…aid to holders 0wallets paid $1,271.23per ZEC $PRIVATE Platform coin A cut of every trade here buys it back and burns…”
page text · https://useprivate.fun/ · …aid to holders 0wallets paid $1,271.23per ZEC $PRIVATE Platform coin A cut of every trade here buys it back and burns…
E41
The Internet Archive has no saved copy of useprivate.fun
page web archive · https://web.archive.org/web/*/useprivate.fun
E42
Agent step 1: view
AI agent step 1 · view on /
E43
Agent step 2: click Top yield
AI agent step 2 · click on / · page called GET useprivate.fun/api/coins
E44
Agent step 3: go /token
AI agent step 3 · go on /token · page called GET useprivate.fun/api/health, GET useprivate.fun/api/stats, GET useprivate.fun/api/coins, GET useprivate.fun/api/zpad, GET useprivate.fun/api/live, GET useprivate.fun/api/coins/bFccLz9mSjijy6arzKWH3R8QAyA1qzwoqUh8zXLpump/candles
E45
Agent step 4: go /coin/GmiPXavFExNMGD6D2VGb55a1mHRnMTPDJiroZmQ1BNMP
AI agent step 4 · go on /coin/GmiPXavFExNMGD6D2VGb55a1mHRnMTPDJiroZmQ1BNMP · page called GET useprivate.fun/api/health, GET useprivate.fun/api/stats, GET useprivate.fun/api/coins, GET useprivate.fun/api/coins/GmiPXavFExNMGD6D2VGb55a1mHRnMTPDJiroZmQ1BNMP, GET useprivate.fun/api/lever/access, GET useprivate.fun/api/lever/listings, GET useprivate.fun/api/live, GET useprivate.fun/api/zpad,

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