🎒 NFT Viewer Suite

🤓 the nerd stuff

My NFTs (wallet mode): connects via window.ethereum or WalletConnect, then discovers holdings per collection using the appropriate strategy for that collection's capabilities (enumerable ERC-721 walk, offline index lookup, or ERC-1155 probe), and verifies every result on-chain before display.

Browse (wallet-free): renders every token in a collection plus its current owner and a whale/top-holder list, entirely from precomputed data — zero chain calls to open the grid. Deep-link directly to a collection with a ?collection=<address> query parameter.

🤓 the nerd stuff

Rarity is computed with a trait-frequency method, the same general approach popularized by rarity.tools: rarer trait values (lower frequency across the collection) contribute more to a token's rank. Data comes from a lazily-loaded per-collection sidecar file, fetched only when a card is opened — browsing the grid itself makes no chain calls and loads no trait data up front.

An absent trait (a trait type the token simply doesn't have) is tracked as its own distinct counter, and is not conflated with a trait that is literally valued the string "None" — some collections genuinely have a trait value called "None" (e.g. a "Back" slot that can be empty), and treating that the same as "trait absent" would misrepresent both.

Collections with fewer than 2 rankable trait types (effectively, collections of unique 1-of-1 art with nothing comparable across tokens) are marked unrankable rather than assigned an arbitrary rank. Tokens whose metadata could not be resolved from any gateway are left unranked rather than shown as falsely rare.

🤓 the nerd stuff

Derpe Dewdz (99 tokens) and toona bros (35 tokens) are both ERC-1155 collections where every token id has supply exactly 1 and a single owner — genuine 1-of-1s, not multi-edition prints.

Both browse (via the owner-per-token index, ids discovered from on-chain Transfer logs) and wallet mode (via the same index-backed lookup used for non-enumerable ERC-721) route these collections through the ordinary single-owner path rather than a multi-edition view.

A pasted/unindexed ERC-1155 collection still falls back to a direct balanceOf probe against the registry's sample ids.

🤓 the nerd stuff

Share buttons generate links to static share/<slug>.html unfurl pages carrying the correct Open Graph / Twitter Card metadata for that specific token, so link previews on social platforms and chat apps render the actual artwork rather than a generic site card. A collection can also be reached directly with a ?collection=<address> deep link into browse mode.

🤓 the nerd stuff

The transfer form opens a confirm panel anchored to the specific card, showing the recipient address grouped for easy visual verification, before the actual on-chain transfer transaction is sent. This is deliberately a two-step confirm rather than a single click, because token transfers are irreversible.

🤓 the nerd stuff

IPFS gateways: a pool of five (filebase, pinata, dweb, w3s.link, nftstorage.link) — the runtime does one full pass across the pool plus a single retry pass, capped by an overall time budget per token so a hanging gateway can't stall a card indefinitely.

RPC endpoints: every read on every BLAZE page goes through one shared read-only provider backed by four verified Sonic RPC endpoints (soniclabs primary, then drpc / publicnode / tenderly), with automatic failover so a single endpoint outage doesn't blank the page.

🤓 the nerd stuff

Standings are precomputed offline and shipped as static data with an "as of block N" freshness stamp — that per-tribe scoreboard makes zero chain calls. As of 2026-08-05 the page ALSO shows a small live ticker strip (three GLOBAL view calls, polled every 30s) so the numbers never look frozen between rebuilds; it fails silently to hidden if the chain is unreachable, and it never touches the tribe standings themselves.

Score = all-time BLAZE burned (transfers to 0x0 / 0x…dEaD) by wallets holding each collection, per the shipped owner indexes. Game loss-burns are re-attributed to the losing player via the flip event in the same transaction.

Burns from project wallets (treasury, faucet, game ops) sit in a visible, non-competing "🏛️ The House" row so totals still reconcile with the token's totalBurned(); wallets holding none of the tribed collections appear as "🌫️ lone wolves".

A tribe exists in the Arena exactly when a shipped owner index exists for it, so a newly registered collection joins the standings when its index is built, not the moment it is added to the registry. (Tribes follow the gallery list, not the faucet whitelist — $HEDGY Hogs 🦔 is a tribe without being whitelisted.) Multi-tribe wallets credit every tribe they hold — a stated feature, which is why the tribe columns intentionally sum to slightly more than the unique total.