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

burn.claims

“BURN — Burn the tokens. Keep the upside.”

Template-written 15 evidence items Code reader analysed 3 scripts
What this means for you

burn.claims talked to 1 outside service on a first visit.E5

  • 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.E14

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

Calls its own backend none seen
Wallet code signTransaction, personal_sign, eth_requestAccountsE14E13E12
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What it is

  • The Internet Archive has never saved this site, so it is probably new.E15
  • The site describes itself as: “Burn the tokens. Keep the upside. Open a BURN position, track its PnL in SOL and USD, and claim your profit once.”E2
  • It's built with React (common tools for building web apps).E6
  • Notable building blocks in its code: Supabase client.E7
  • In your browser it can copy text to your clipboard and saves small bits of data in your browser.E8E9

Where your data goes

Backend & data servicesDatabases, search and APIs the app runs on. 1
jcabfydqhcyausmsirpm.supabase.coSupabase: app database and API 4×E5

Crypto and wallets

  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E14
  • personal_sign: asks you to sign a text message (often to log in; moves no funds by itself).E13
  • eth_requestAccounts: asks to connect your wallet, which shows the site your address.E12

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

signTransaction

Connecting your wallet

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

signTransactionpersonal_signeth_requestAccounts

Saving data on your device

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

local_storage

Pages and API calls

Endpoints

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

/api/broadcastcodeE11

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: BURN — Burn the tokens. Keep the upside.
page title · https://burn.claims/
E2
Page description: Burn the tokens. Keep the upside. Open a BURN position, track its PnL in SOL and USD, and claim your profit once.
page description · https://burn.claims/
E3
Main heading: BURN ✦
page h1 · https://burn.claims/
E4
8 request(s) to burn.claims
types: 3 script, 3 font, 1 document
GET https://burn.claims/ · script · 8 requests · network recording
E5
4 request(s) to jcabfydqhcyausmsirpm.supabase.co
types: 4 fetch
GET https://jcabfydqhcyausmsirpm.supabase.co/functions/v1/burn-api/app-config · fetch · 4 requests · network recording
E6
React detected by the code reader (react-runtime)
confidence: medium
burn.claims/assets/index-C0LlAVuv.js · “react-runtime” · the code reader
E7
Supabase client found in the code
burn.claims/assets/supabase-CelhU-Wa.js @ 1:32 · “supabase-js” · pattern scan
E8
Uses the browser ability: clipboard_write
can copy text to your clipboard
burn.claims/assets/index-C0LlAVuv.js @ 17:7840 · “clipboard.writeText(” · pattern scan
E9
Uses the browser ability: local_storage
saves small bits of data in your browser
burn.claims/assets/supabase-CelhU-Wa.js @ 13:2576 · “localStorage.setItem(” · pattern scan
E10
Uses the browser ability: web_worker
runs work in a background thread
burn.claims/assets/supabase-CelhU-Wa.js @ 12:6194 · “new Worker(” · pattern scan
E11
The code names the endpoint /api/broadcast
burn.claims/assets/supabase-CelhU-Wa.js @ 6:6170 · “/api/broadcast” · pattern scan
E12
Wallet request in code: eth_requestAccounts
asks to connect your wallet, which shows the site your address
burn.claims/assets/supabase-CelhU-Wa.js @ 28:24206 · “eth_requestAccounts” · pattern scan
E13
Wallet request in code: personal_sign
asks you to sign a text message (often to log in; moves no funds by itself)
burn.claims/assets/supabase-CelhU-Wa.js @ 28:25209 · “personal_sign” · pattern scan
E14
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
burn.claims/assets/index-C0LlAVuv.js @ 17:703 · “signTransaction” · pattern scan
E15
The Internet Archive has no saved copy of burn.claims
page web archive · https://web.archive.org/web/*/burn.claims

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 3 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 kjfo10xs.