petix.fun
“Petix”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
AI / agents
“…d earn extra $PETIX coins from farming with your army! AI-Driven Battleground Sign In to create your pet $PETIX…”E23
No matching code, calls or services in what loaded for us.
The real tech may live elsewhere. This page links to: github.com/kdmi/Petix · check the code
What it is
- The site describes itself as: “Create your pets, participate in AI-driven competitions, and claim rewards.”E2
- It's built with React (common tools for building web apps).E6
- In your browser it saves small bits of data in your browser.E9
- It has sections such as /transparency.E18
- While loading, it called 1 endpoint on its own servers, such as /api/auth/evm/me.E10
Where your data goes
Crypto and wallets
- Wallet tools in the code: WalletConnect / Reown and EIP-6963 wallet discovery.E7E8
- personal_sign: asks you to sign a text message (often to log in; moves no funds by itself).E20
- eth_requestAccounts: asks to connect your wallet, which shows the site your address.E19
- 2 contract or wallet addresses are written into the code.E21E22
2 addresses found in the code
0xb79ec3cdffefe0ec6c806d715e4082d6be4dbf550x0e8caf9eca5e45df0e6f50f58a5bf664db1740c1Paste any of these into the box on the home page to get the contract's blueprint.
How key features work
Connecting your wallet
It connects to crypto wallets using WalletConnect / Reown, EIP-6963 wallet discovery, personal_sign and eth_requestAccounts. Connecting shows the site your wallet address; it doesn't move funds by itself.E7E8E19
WalletConnect / ReownEIP-6963 wallet discoverypersonal_signeth_requestAccountsSign-in and accounts
Sign-in and account features show up in its code or traffic (/api/auth/evm/me, /api/auth/solana/me and /api/auth/evm/challenge).E10E12E14
/api/auth/evm/me/api/auth/solana/me/api/auth/evm/challengeLoading its content
Its content loads from its own API while you browse (/api/auth/evm/me).E10
/api/auth/evm/meSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E9
local_storagePages and API calls
Pages it links to
/transparency/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.
- 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 nfYb1oJO.