Learn

How NFT Inspector measures on-chain resilience

A transparent account of how NFT Inspector separates data permanence from contract control, what the scores mean, and where the analysis has limits.

What does on-chain resilience mean?

An NFT is more than its contract address. Its metadata may come from contract storage, IPFS, Arweave, or a web server. Its media can introduce another storage dependency. An owner, role, proxy admin, or external resolver may also retain the ability to change what the token returns.

NFT Inspector uses on-chain resilience to describe how likely the NFT is to remain accessible and recognizable over time, and how little continuing trust it requires. The score is diagnostic, not a judgment of artistic quality, market value, or project legitimacy.

The two parts of the score

Data permanence

Data permanence evaluates where the token metadata and media live, whether their addresses are immutable, and whether they were accessible during inspection. Inline contract data has the fewest external storage dependencies. Content-addressed storage protects integrity, but availability still depends on copies remaining online. Ordinary HTTPS hosting can disappear or serve different bytes at the same URL.

Trustlessness

Trustlessness evaluates who can alter contract behavior, metadata resolution, or rendered content. The inspection looks for ownership and privileged roles, multisig and timelock controls, proxy patterns, source verification, and dependencies such as ENS, CCIP-Read, or another contract. A delay or multisig can reduce control risk without removing it.

How evidence is classified

NFT Inspector resolves the token from the selected EVM chain and records evidence at several layers:

  1. The token standard and contract interfaces.
  2. The original metadata URI and the resolved metadata document.
  3. Primary media, animation, and dependencies referenced inside supported SVG or HTML.
  4. Ownership, role, proxy, implementation, and source-verification signals.
  5. Chain-level infrastructure assumptions relevant to retrieval.

Each finding retains its underlying URI, address, or observed state where practical. The interface presents the component scores separately so a strong storage result cannot hide upgrade authority, and an ownerless contract cannot hide centralized media hosting.

How to read the result

Treat the overall score as a summary and the findings as the useful part. Two NFTs can receive similar totals for different reasons. One may use immutable IPFS metadata behind an upgradeable proxy; another may have fixed contract logic while serving its image from a mutable domain. Their remediation paths and failure modes are different.

Re-run an inspection after a contract upgrade, ownership transfer, metadata reveal, base-URI change, or migration. Results describe the state observed at analysis time, not a guarantee about future availability.

Known limits

  • Private, novel, or deliberately obscured control or proxy patterns may not be detectable.
  • Results show current accessibility; data, chain and gateway availability can change after the inspection.
  • The analysis does not audit security, licensing, provenance claims, or creator identity.