shib.io

• The site describes itself as: “Join the Shiba Inu’s ShibArmy. Explore an innovative crypto ecosystem empowering a global community with utility-based tokens and decentrali”E2
• It's built with Next.js and React (common tools for building web apps).E35E36
• Notable building blocks in its code: Socket.IO (live connection).E37
• In your browser it can copy text to your clipboard, installs a background script (offline use, push messages), saves small bits of data in your browser, runs compiled WebAssembly code in your browser and 1 more.E52E53E54E55E56
• It has sections such as /ecosystem, /sns, /shibarium, /dapps, /tokens and /news.E65E66
• While loading, it called 3 endpoints on its own servers, such as /page-view, /sou/dashboard and /defi/shibaswap/ethereum/cross-chain-swap.E58E59E60

Our sandbox blocked requests to analytics.shib.io, app.tryroll.com because they pointed to private or internal addresses.

• Wallet tools in the code: WalletConnect / Reown, RainbowKit, wagmi, viem, ethers.js, Coinbase Wallet SDK and 3 more.E43E44E45E46E47E48
• eth_sign: can ask for a raw 'eth_sign' signature, an old method that signs data you can't read.E90
• approve: has code to ask for a token spending approval (lets a contract move that token from your wallet).E97
• eth_signTypedData: asks you to sign structured data (can be a login, an order or an off-chain token approval).E91
• eth_sendTransaction: asks your wallet to send a transaction (can move funds and costs a fee).E92
• wallet_sendCalls: asks your wallet to send a batch of transactions in one go.E96
• signTransaction: asks a wallet to sign transactions (often Solana wallets).E98
• Contract functions the app calls by name: aggregate3, addr, resolveWithGateways, findResolver, eip712Domain, balanceOf, decimals, tokenURI and 7 more.E99E100E101E102E103E104
• Chains named in the code: Ethereum, Foundry, Shib Alpha Layer, Polygon, Polygon Mumbai, Shibarium, Puppynet, Arbitrum Sepolia and 12 more.E144E145E146E147E148E149
• 30 contract or wallet addresses are written into the code, including Multicall3 (batches read calls) and WETH on Ethereum.E115E129

Names only. We never store the values.

localStorageE32: user_tracking_id, loglevel:torus.js, rk-version, @appkit/connection_status, redux_localstorage_simple_transactions, redux_localstorage_simple_lists, loglevel:customauth, loglevel:mpc-core-kit, redux_localstorage_simple_user, sns_cart, wagmi.store, @appkit/active_caip_network_id, @appkit/active_namespace, loglevel:fnd, loglevel:auth, @appkit/disconnected_connector_ids, loglevel:http-helpers

sessionStorageE33: session_id, lastTrackedPathname

IndexedDBE34: WALLET_CONNECT_V2_INDEXED_DB

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.

• 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 55 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 LYRuj0ET.