disclosed.run
“Disclosed”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
On-chain / smart contracts
“…on Ticker: $DISCLOSED Venue: StonkFun Paired with: SOL CA: 9XzZ…jRPc Dev wallet: APuR…vnh1 Pays in: xStocks (Sola…”E41
No matching code, calls or services in what loaded for us.
Trading / swaps / bots
“…Yakym R-IN Jackson D-IL Rulli R-OH Lee R-FL A CONGRESS COPY-TRADE FUND ON SOLANA Congress buys. You get paid. When membe…”E42
No matching code, calls or services in what loaded for us.
What it is
- The Internet Archive has never saved this site, so it is probably new.E43
- The site describes itself as: “Congress buys. You get paid.”E2
- It's built with Next.js and React (common tools for building web apps).E6E7
- In your browser it can copy text to your clipboard and receives a live stream of updates from a server.E8E9
- It has sections such as /filings, /members, /index, /dividends, /docs and /treasury.E39E40
- While loading, it called 5 endpoints on its own servers, such as /api/filings, /api/members, /api/index/history and 2 more.E10E11E12E13
Where your data goes
On a first visit the page only talked to its own servers (disclosed.run).
How key features work
Live updates
It keeps live connections open (server-sent events) so content updates without reloading.E9
event_sourcePages and API calls
Pages it links to
//filings/members/index/dividends/docs/treasury/holders/buy/_next/imageEndpoints
Called while loading (seen) or named in the code (code).
| disclosed.run/api/filings | seenE10 |
| disclosed.run/api/members | seenE11 |
| disclosed.run/api/index/history | seenE12 |
| disclosed.run/api/filings/status | seenE13 |
| disclosed.run/api/snapshot | seenE14 |
| /api/snapshot | codeE15 |
| /api/members/A000383/photo | codeE16 |
| /api/members/I000056/photo | codeE17 |
| /api/members/F000110/photo | codeE18 |
| /api/members/B001236/photo | codeE19 |
| /api/members/H001047/photo | codeE20 |
| /api/members/Y000067/photo | codeE21 |
| /api/members/J000309/photo | codeE22 |
| /api/members/R000619/photo | codeE23 |
| /api/members/L000597/photo | codeE24 |
| /api/img/XsEH7wWfJJu2ZT3UCFeVfALnVA6CP5ur7Ee11KmzVpL | codeE25 |
| /api/members/D000032/photo | codeE26 |
| /api/img/Xs6B6zawENwAbWVi7w92rjazLuAr5Az59qgWKcNb45x | codeE27 |
| /api/members/M001218/photo | codeE28 |
| /api/members/S000168/photo | codeE29 |
| /api/img/XsafvsGtzFqqHgTnA3aPC83EAMkacU5mcGtcSayhpVV | codeE30 |
| /api/members/C001123/photo | codeE31 |
| /api/members/A000372/photo | codeE32 |
| /api/events | codeE33 |
| /api/holders | codeE34 |
| /api/wallet | codeE35 |
| /api/rounds | codeE36 |
| /api/payouts | codeE37 |
| /api/index | codeE38 |
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).
- 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 26 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 QO4G2HjL.