Website blueprint · 27 Oct 2026

rulesonsf.fun

“RULES — Make the rules. Set the tone.”

Template-written 29 evidence items REA analysed 35 scripts
What this means for you

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

  • Tech check: the site claims wallet connection and trading / swaps / bots, and its public page shows matching evidence.E27E28E10E25E26
  • We saw no known analytics or advertising services load on the first visit.E1
  • 3 cookies were set in your browser, all by the site itself.E5E6E7
  • Its code can ask your wallet to sign transactions. Read every wallet pop-up before approving.E25

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

“Skip to content RULES Home Tokens Rules Connect wallet Create a token + BUILT FOR STONK. RUN BY YOUR RULES. G…”E27

Wallet libraries in its code: PhantomE10

Wallet requests in its code: signTransaction, signMessageE25E26

Evidence found

Trading / swaps / bots

“…come through Stonk ↗ 64A1…Rzd5 buys 2.58 SOL via Other DEX ILLUSTRATIVE TRADE 64A1…Rzd5 buys 2.58 SOL · checking…”E28

Transaction requests to your wallet: signTransactionE25

Calls its own backend /api/coinsE13
Wallet code PhantomE10E25E26
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.E29
  • The site describes itself as: “Create your token through Stonk. Choose your community guidelines and fee mode, with live mint pages and wallet-approved transactions.”E2
  • It's built with React and Next.js (common tools for building web apps).E8E9
  • In your browser it can copy text to your clipboard and saves small bits of data in your browser.E11E12
  • It has sections such as /live, /launch, /c, /how, /burns and /drafts.E23E24
  • While loading, it called 1 endpoint on its own servers, such as /api/coins.E13

Where your data goes

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

Crypto and wallets

  • Wallet tools in the code: Phantom.E10
  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E25
  • signMessage: asks a wallet to sign a message.E26

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

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

PhantomsignTransactionsignMessage

Sign-in and accounts

Sign-in and account features show up in its code or traffic (/api/auth).E18

/api/auth

Loading its content

Its content loads from its own API while you browse (/api/coins).E13

/api/coins

Saving data on your device

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

local_storage

Cookies and storage

Names only. We never store the values.

CookieSet forKeptWhose
__Host-appgarden-visitorE5rulesonsf.fun about 90 daysthe site
cf_clearanceE6rulesonsf.fun about 365 daysthe site
__cf_bmE7rulesonsf.fun about 0 daysthe site

Pages and API calls

Pages it links to

//live/launch/c/how/burns/drafts/callsRequire buys to come through Stonk. Buys routed elsewhere are returned; this condition does not by itself restrict sells.

Endpoints

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

rulesonsf.fun/api/coinsseenE13
solanacompass.com/api/feescodeE14
/api/imagecodeE15
/apicodeE16
/v3/main/AvailabilityCheckAPIcodeE17
/api/authcodeE18
/api/rpccodeE19
/api/stonk/configcodeE20
/api/launch-assetscodeE21
/api/fee-plancodeE22

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: RULES — Make the rules. Set the tone.
page title · https://rulesonsf.fun/
E2
Page description: Create your token through Stonk. Choose your community guidelines and fee mode, with live mint pages and wallet-approved transactions.
page description · https://rulesonsf.fun/
E3
Main heading: Good tokens. Ground rules.
page h1 · https://rulesonsf.fun/
E4
40 request(s) to rulesonsf.fun
types: 15 script, 13 image, 4 font
GET https://rulesonsf.fun/ · script · 40 requests · network recording
E5
Cookie '__Host-appgarden-visitor' set for rulesonsf.fun
kept for about 90 days
cookie __Host-appgarden-visitor on rulesonsf.fun · value not stored
E6
Cookie 'cf_clearance' set for rulesonsf.fun
kept for about 365 days
cookie cf_clearance on rulesonsf.fun · value not stored
E7
Cookie '__cf_bm' set for rulesonsf.fun
kept for about 0 days
cookie __cf_bm on rulesonsf.fun · value not stored
E8
React detected by REA (react-runtime)
confidence: medium
rulesonsf.fun/_next/static/chunks/framework-D_rUT4EX.js · “react-runtime” · REA analyze-web-bundle 6.4.0
E9
Next.js found in the code
rulesonsf.fun/ (page HTML) @ 1:180 · “/_next/static/” · pattern scan
E10
Phantom found in the code
rulesonsf.fun/chain.js @ 49:537816 · “window.phantom” · pattern scan
E11
Uses the browser ability: clipboard_write
can copy text to your clipboard
rulesonsf.fun/app.js @ 347:879 · “clipboard.writeText(” · pattern scan
E12
Uses the browser ability: local_storage
saves small bits of data in your browser
rulesonsf.fun/chain.js @ 49:530362 · “localStorage.setItem(” · pattern scan
E13
The page called /api/coins on rulesonsf.fun (GET)
GET https://rulesonsf.fun/api/coins · fetch · network recording
E14
REA found the endpoint solanacompass.com/api/fees
how: call:Iu.get
rulesonsf.fun/chain.js @ 49:92009 · “solanacompass.com/api/fees” · REA analyze-web-bundle 6.4.0
E15
The code names the endpoint /api/image
rulesonsf.fun/app.js @ 175:525 · “/api/image” · pattern scan
E16
The code names the endpoint /api
rulesonsf.fun/app.js @ 219:57 · “/api” · pattern scan
E17
The code names the endpoint /v3/main/AvailabilityCheckAPI
rulesonsf.fun/chain.js @ 49:528067 · “/v3/main/AvailabilityCheckAPI” · pattern scan
E18
The code names the endpoint /api/auth
rulesonsf.fun/chain.js @ 49:537314 · “/api/auth” · pattern scan
E19
The code names the endpoint /api/rpc
rulesonsf.fun/chain.js @ 49:537720 · “/api/rpc” · pattern scan
E20
The code names the endpoint /api/stonk/config
rulesonsf.fun/chain.js @ 49:540637 · “/api/stonk/config” · pattern scan
E21
The code names the endpoint /api/launch-assets
rulesonsf.fun/chain.js @ 49:540968 · “/api/launch-assets” · pattern scan
E22
The code names the endpoint /api/fee-plan
rulesonsf.fun/chain.js @ 49:542223 · “/api/fee-plan” · pattern scan
E23
10 links to pages on the same site
page links · https://rulesonsf.fun/ · /, /live, /launch, /c, /how, /burns, /drafts, /calls
E24
REA found the route Require buys to come through Stonk. Buys routed elsewhere are returned; this con
rulesonsf.fun/rules/rule-content.mjs @ 6:214 · “Require buys to come through Stonk. Buys routed elsewhere are returned; this con” · REA analyze-web-bundle 6.4.0
E25
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
rulesonsf.fun/chain.js @ 49:91469 · “signAllTransactions” · pattern scan
E26
Wallet request in code: signMessage
asks a wallet to sign a message
rulesonsf.fun/chain.js @ 49:541790 · “signMessage” · pattern scan
E27
The site says: “Skip to content RULES Home Tokens Rules Connect wallet Create a token + BUILT FOR STONK. RUN BY YOUR RULES. G…”
page text · https://rulesonsf.fun/ · Skip to content RULES Home Tokens Rules Connect wallet Create a token + BUILT FOR STONK. RUN BY YOUR RULES. G…
E28
The site says: “…come through Stonk ↗ 64A1…Rzd5 buys 2.58 SOL via Other DEX ILLUSTRATIVE TRADE 64A1…Rzd5 buys 2.58 SOL · checking…”
page text · https://rulesonsf.fun/ · …come through Stonk ↗ 64A1…Rzd5 buys 2.58 SOL via Other DEX ILLUSTRATIVE TRADE 64A1…Rzd5 buys 2.58 SOL · checking…
E29
The Internet Archive has no saved copy of rulesonsf.fun
page web archive · https://web.archive.org/web/*/rulesonsf.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.
  • REA 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 KOpY4OX0.