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

forks.wiki

“$DOGE · doge · forks”

Template-written 36 evidence items Code reader analysed 6 scripts
What this means for you

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

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

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 /api/market, /api/coin, /api/reposE10E11E12E13
Wallet code PhantomE6E34E35
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

The real tech may live elsewhere. This page links to: github.com/dogecoin/dogecoin · check the code github.com/forkwiki/fork · check the code

What it is

  • The Internet Archive first saved this site on 2022-01-02 (1774 days ago).E36
  • The site describes itself as: “A token's terminal on forks: chart, trades, holders, and buy or sell from your own wallet.”E2
  • In your browser it can copy text to your clipboard and saves small bits of data in your browser.E7E8
  • It has sections such as /market, /launch, /guide, jupiter and pump.E31E32
  • While loading, it called 5 endpoints on its own servers, such as /api/market, /api/coin, /api/repos and 2 more.E10E11E12E13

Where your data goes

On a first visit the page only talked to its own servers (forks.wiki).

Crypto and wallets

  • Wallet tools in the code: Phantom.E6
  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E34
  • signMessage: asks a wallet to sign a message.E35

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

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

PhantomsignTransactionsignMessage

Loading its content

Its content loads from its own API while you browse (/api/market, /api/coin, /api/repos, /api/trades and 1 more).E10E11E12E13E14

/api/market/api/coin/api/repos/api/trades/api/chart

Drawing and editing in the browser

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

canvas

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

//market/launch/guidejupiterpump

Endpoints

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

forks.wiki/api/marketseenE10
forks.wiki/api/coinseenE11
forks.wiki/api/reposseenE12
forks.wiki/api/tradesseenE13
forks.wiki/api/chartseenE14
/api/marketcodeE15
/api/mecodeE16
/api/ipfs/bafkreiapsivssfonnklk3siht3qfvph2tsbzq4zpmggsp4cdcor7na35p4codeE17
/api/balancecodeE18
/api/ipfscodeE19
/api/tokenscodeE20
/api/launch/plancodeE21
/api/launch/buildcodeE22
/api/launch/submitcodeE23
/api/launch/statuscodeE24
/api/tokens/recentcodeE25
/api/holderscodeE26
/api/trade/quotecodeE27
/api/trade/buildcodeE28
/api/trade/sendcodeE29
/api/txcodeE30

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: $DOGE · doge · forks
page title · https://forks.wiki/coin/HTaBmiNnLkMZEcgmpAFU76LG3akLKPSfJxfXu3pffork
E2
Page description: A token's terminal on forks: chart, trades, holders, and buy or sell from your own wallet.
page description · https://forks.wiki/coin/HTaBmiNnLkMZEcgmpAFU76LG3akLKPSfJxfXu3pffork
E3
Site name: forks
page site_name · https://forks.wiki/coin/HTaBmiNnLkMZEcgmpAFU76LG3akLKPSfJxfXu3pffork
E4
Main heading: $DOGE doge coin on forks
page h1 · https://forks.wiki/coin/HTaBmiNnLkMZEcgmpAFU76LG3akLKPSfJxfXu3pffork
E5
14 request(s) to forks.wiki
types: 5 script, 5 fetch, 1 document
GET https://forks.wiki/coin/HTaBmiNnLkMZEcgmpAFU76LG3akLKPSfJxfXu3pffork · script · 14 requests · network recording
E6
Phantom found in the code
forks.wiki/src/wallet.js @ 119:28 · “phantom.app” · pattern scan
E7
Uses the browser ability: clipboard_write
can copy text to your clipboard
forks.wiki/src/shell.js @ 71:89 · “clipboard.writeText(” · pattern scan
E8
Uses the browser ability: local_storage
saves small bits of data in your browser
forks.wiki/src/shell.js @ 31:11 · “localStorage.setItem(” · pattern scan
E9
Uses the browser ability: canvas
draws graphics on a canvas
forks.wiki/src/launch.js @ 188:31 · “getContext('2d'” · pattern scan
E10
The page called /api/market on forks.wiki (GET)
GET https://forks.wiki/api/market · fetch · network recording
E11
The page called /api/coin on forks.wiki (GET)
GET https://forks.wiki/api/coin · fetch · network recording
E12
The page called /api/repos on forks.wiki (GET)
GET https://forks.wiki/api/repos · fetch · network recording
E13
The page called /api/trades on forks.wiki (GET)
GET https://forks.wiki/api/trades · fetch · network recording
E14
The page called /api/chart on forks.wiki (GET)
GET https://forks.wiki/api/chart · fetch · network recording
E15
Code reader found the endpoint /api/market
how: call:fetch
forks.wiki/src/shell.js @ 152:62 · “/api/market” · the code reader
E16
Code reader found the endpoint /api/me
how: call:fetch
forks.wiki/src/launch.js @ 51:33 · “/api/me” · the code reader
E17
The code names the endpoint /api/ipfs/bafkreiapsivssfonnklk3siht3qfvph2tsbzq4zpmggsp4cdcor7na35p4
forks.wiki/ (page HTML) @ 43:38 · “/api/ipfs/bafkreiapsivssfonnklk3siht3qfvph2tsbzq4zpmggsp4cdcor7na35p4” · pattern scan
E18
The code names the endpoint /api/balance
forks.wiki/src/shell.js @ 74:30 · “/api/balance” · pattern scan
E19
The code names the endpoint /api/ipfs
forks.wiki/src/shell.js @ 167:114 · “/api/ipfs” · pattern scan
E20
The code names the endpoint /api/tokens
forks.wiki/src/launch.js @ 60:28 · “/api/tokens” · pattern scan
E21
The code names the endpoint /api/launch/plan
forks.wiki/src/launch.js @ 209:26 · “/api/launch/plan” · pattern scan
E22
The code names the endpoint /api/launch/build
forks.wiki/src/launch.js @ 391:28 · “/api/launch/build” · pattern scan
E23
The code names the endpoint /api/launch/submit
forks.wiki/src/launch.js @ 419:28 · “/api/launch/submit” · pattern scan
E24
The code names the endpoint /api/launch/status
forks.wiki/src/launch.js @ 433:31 · “/api/launch/status” · pattern scan
E25
The code names the endpoint /api/tokens/recent
forks.wiki/src/launch.js @ 477:26 · “/api/tokens/recent” · pattern scan
E26
The code names the endpoint /api/holders
forks.wiki/src/coin.js @ 194:188 · “/api/holders” · pattern scan
E27
The code names the endpoint /api/trade/quote
forks.wiki/src/coin.js @ 298:26 · “/api/trade/quote” · pattern scan
E28
The code names the endpoint /api/trade/build
forks.wiki/src/coin.js @ 316:28 · “/api/trade/build” · pattern scan
E29
The code names the endpoint /api/trade/send
forks.wiki/src/coin.js @ 324:28 · “/api/trade/send” · pattern scan
E30
The code names the endpoint /api/tx
forks.wiki/src/coin.js @ 332:32 · “/api/tx” · pattern scan
E31
4 links to pages on the same site
page links · https://forks.wiki/coin/HTaBmiNnLkMZEcgmpAFU76LG3akLKPSfJxfXu3pffork · /, /market, /launch, /guide
E32
Code reader found the route jupiter
forks.wiki/src/coin.js @ 324:71 · “jupiter” · the code reader
E33
Code reader found the route pump
forks.wiki/src/coin.js @ 324:130 · “pump” · the code reader
E34
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
forks.wiki/src/wallet.js @ 23:102 · “signTransaction” · pattern scan
E35
Wallet request in code: signMessage
asks a wallet to sign a message
forks.wiki/src/wallet.js @ 104:40 · “signMessage” · pattern scan
E36
The Internet Archive first saved forks.wiki on 2022-01-02 and has snapshots from 8 different days
page web archive · https://web.archive.org/web/20220102051130/forks.wiki

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.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id dLySA6aF.