www.collectorinu.fun
“Collector Inu — The collectible index meme.”
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.E29
- The site describes itself as: “Collect cards. Open packs. Earn drops. Explore collectible inventory, Collector Packs, the treasury and verified reward records.”E2
- It's built with Next.js and React (common tools for building web apps).E7E8
- In your browser it can copy text to your clipboard and saves small bits of data in your browser.E9E10
- It has sections such as /packs, /rewards, /treasury, /collectibles, /collector-index and /wallet.E25E26
- While loading, it called 5 endpoints on its own servers, such as /api/state, /api/rewards, /api/treasury and 2 more.E11E12E13E14
Where your data goes
Not identifiedServices we don't have in our list yet. 1
| nft.collectorcrypt.com | not identified | 14×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.E27
signTransactionLoading its content
Its content loads from its own API while you browse (/api/state, /api/rewards, /api/treasury, /api/collector/cards and 1 more).E11E12E13E14E15
/api/state/api/rewards/api/treasury/api/collector/cards/api/collector/inventorySaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E10
local_storagePages and API calls
Pages it links to
//packs/rewards/treasury/collectibles/collector-index/wallet/wishlist/docs/draws/ci/ledger/market/_next/imageEndpoints
Called while loading (seen) or named in the code (code).
| www.collectorinu.fun/api/state | seenE11 |
| www.collectorinu.fun/api/rewards | seenE12 |
| www.collectorinu.fun/api/treasury | seenE13 |
| www.collectorinu.fun/api/collector/cards | seenE14 |
| www.collectorinu.fun/api/collector/inventory | seenE15 |
| /api/collector/cards | codeE16 |
| /api/ledger | codeE17 |
| /api/packs | codeE18 |
| /api/holder | codeE19 |
| /api/cnft/owner | codeE20 |
| /api/claims/redemptions | codeE21 |
| /api/claims/burn | codeE22 |
| /api/claims/burn/prepare | codeE23 |
| /api/claims/burn/submit | codeE24 |
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 21 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 F0fbBOEn.