bawsaq.fund
“BAWSAQ”
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).
What it is
- The Internet Archive has never saved this site, so it is probably new.E31
- The site describes itself as: “Explore BAWSAQ’s fictional company stocks and launch coins on Solana.”E2
- It's built with React and Remix / React Router (common tools for building web apps).E7E8
- Notable building blocks in its code: Supabase client.E9
- 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 /goods, /explore, /launch, /ledger, /earnings and /docs.E17E18
- While loading, it called 1 endpoint on its own servers, such as /api/public-read.E14
Where your data goes
Crypto & walletsConnect wallets, read blockchains or fetch token prices. 1
| api.dexscreener.com | DexScreener: token prices and pools | 1×E5 |
Backend & data servicesDatabases, search and APIs the app runs on. 1
| bjjbpggvfgvijpfutotl.supabase.co | Supabase: app database and API | 5×E6 |
Crypto and wallets
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.E29
signTransactionConnecting 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.E10E5
PhantomsignTransactionsignMessageLoading its content
Its content loads from its own API while you browse (/api/public-read).E14
/api/public-readSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E12
local_storagePages and API calls
Pages it links to
//goods/explore/launch/ledger/earnings/docs/adminPanelgoodsgoods/officialgoods/:sluggoods/reward/:mintexploreexplore/:mintledgerlaunchearningsdocs*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.
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 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 oHYkzVvs.