$GRDGEARnew
$Cornellnew
$ELUNnew
$ELUNnew
$Claudenew
$USEOnew
$姆巴羊new
$CATnew
$1wiknew
$GTAnew
$BCKROOMnew
$LUMINAnew
$大Anew
$Groknew
$AMAZONnew
$HOODSVnew
$USOE🇺🇸new
$reneiwnew
$VEIL
$PAID
$BATON
$DARK
$XTO
$MISTAKE
$HOOKED
$E/ACC
Website blueprint · 18 Oct 2026
nivra.fun
“NIVRA — Your Place in the NIVRA Ecosystem on Solana”
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 site describes itself as: “Complete the required steps, verify your eligibility and register your allocation of 500,000 $NIVRA.”E2
- It's built with React (common tools for building web apps).E9
- Notable building blocks in its code: Supabase client.E10
- In your browser it saves small bits of data in your browser.E11
- It has sections such as /500k, /security, /privacy and /terms.E15
- While loading, it called 1 endpoint on its own servers, such as /__l5e/trackevents.E13
Where your data goes
Crypto and wallets
How key features work
Connecting your wallet
It connects to crypto wallets using personal_sign and eth_requestAccounts. Connecting shows the site your wallet address; it doesn't move funds by itself.E16
personal_signeth_requestAccountsLoading its content
Its content loads from its own API while you browse (/__l5e/trackevents).E13
/__l5e/trackeventsSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E11
local_storageCookies and storage
Names only. We never store the values.
Pages and API calls
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: NIVRA — Your Place in the NIVRA Ecosystem on Solana
page title · https://nivra.fun/
E2
Page description: Complete the required steps, verify your eligibility and register your allocation of 500,000 $NIVRA.
page description · https://nivra.fun/
E3
Main heading: Your Place in the NIVRA Ecosystem Starts Here.
page h1 · https://nivra.fun/
E4
23 request(s) to nivra.fun
types: 18 script, 2 image, 1 document
GET https://nivra.fun/ · script · 23 requests · network recording
E5
1 request(s) to fonts.googleapis.com
types: 1 stylesheet
GET https://fonts.googleapis.com/css2 · stylesheet · network recording
E6
3 request(s) to fonts.gstatic.com
types: 3 font
GET https://fonts.gstatic.com/s/sora/v17/xMQ9uFFYT72X5wkB_18qmnndmSdSnh2BAfO5mnuyOo1lfiQwV6-x.woff2 · font · 3 requests · network recording
E7
Cookie '__dpl' set for nivra.fun
kept for about 1 days
cookie __dpl on nivra.fun · value not stored
E8
Cookie '__cf_bm' set for nivra.fun
kept for about 0 days
cookie __cf_bm on nivra.fun · value not stored
E9
React detected by REA (react-runtime)
confidence: medium
nivra.fun/assets/index-CZ3M0BFC.js · “react-runtime” · REA analyze-web-bundle 6.4.0
E10
Supabase client found in the code
nivra.fun/assets/index-CZ3M0BFC.js @ 13:47632 · “supabase-js” · pattern scan
E11
Uses the browser ability: local_storage
saves small bits of data in your browser
nivra.fun/assets/index-CZ3M0BFC.js @ 20:2497 · “localStorage.setItem(” · pattern scan
E12
Uses the browser ability: web_worker
runs work in a background thread
nivra.fun/assets/index-CZ3M0BFC.js @ 19:6124 · “new Worker(” · pattern scan
E13
The page called /__l5e/trackevents on nivra.fun (POST)
POST https://nivra.fun/__l5e/trackevents · fetch · network recording
E14
The code names the endpoint /api/broadcast
nivra.fun/assets/index-CZ3M0BFC.js @ 13:75350 · “/api/broadcast” · pattern scan
E15
6 links to pages on the same site
page links · https://nivra.fun/ · /, /500k, /security, /privacy, /terms
E16
Wallet request in code: eth_requestAccounts
asks to connect your wallet, which shows the site your address
nivra.fun/assets/index-CZ3M0BFC.js @ 22:23334 · “eth_requestAccounts” · pattern scan
E17
Wallet request in code: personal_sign
asks you to sign a text message (often to log in; moves no funds by itself)
nivra.fun/assets/index-CZ3M0BFC.js @ 22:24055 · “personal_sign” · pattern scan
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.
- REA hit its size budget on parts of 7 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 UyIJ8YSC.