Chain Tech Catcher / Knowledge library · Foundations · 2 min read
An NFT identifies a token
A non-fungible token records ownership or another defined relationship for a particular token identifier within a contract. Its metadata can describe a name, image, attributes, or other content. The token, metadata document, media file, and associated legal rights are separate things.
A marketplace image is an interface rendering, not the entire asset specification. It may be cached, transformed, or served from a gateway. To investigate durability, follow the token’s metadata reference and inspect where each referenced file comes from.
A hypothetical artwork reference
A collection’s tokenURI points to a JSON document on a web server, which points to an image on another server. The token remains onchain if either server stops responding, but the convenient description or image may become unavailable. Onchain ownership does not keep every external server running.
Now suppose the JSON and image use content-addressed identifiers. Those identifiers help verify the retrieved content and distinguish versions. They do not force someone to retain and serve the bytes forever. Persistence still requires storage and distribution arrangements.
If an administrator can change the base URI, the referenced metadata may change despite the token identifier remaining constant. That can support intended updates, or conflict with a buyer’s expectation of a fixed artifact. Read the contract’s metadata controls and any freeze mechanism rather than assuming immutability from the word NFT.
| Layer | Question |
|---|---|
| Token | Which network, contract, and identifier? |
| Metadata | Where is it and can it change? |
| Media | Who stores and serves the referenced bytes? |
| Rights | What license or other terms apply? |
Content and rights require separate evidence
Owning a token does not automatically transfer copyright or grant unrestricted commercial use of the referenced work. Terms depend on the specific arrangement. Read the applicable license and identify whether it can change, instead of importing rights from a marketplace’s visual presentation.
Counterfeit collections can copy images, names, and descriptions. Contract identity and provenance matter more than appearance. Even a known contract can reference content hosted elsewhere with different durability assumptions. Authenticity and persistence therefore need separate checks.
A collection review checklist
- Verify network, contract, token identifier, and relevant ownership record.
- Retrieve the metadata and inspect all external references.
- Identify mutable URI settings and who controls them.
- Check storage persistence, pinning, gateways, and independent retrieval options.
- Save the license and terms associated with the intended use.
For a practical test, retrieve the same content through a second independent route and record identifiers. Preserve your own copy if the content matters to you, while recognizing that a personal copy does not establish global availability or additional legal rights.
Frequently asked questions
Does an IPFS link guarantee permanent availability?
No. Content addressing helps identify content. Nodes or services still need to retain and serve it, often through deliberate pinning arrangements.
Is the marketplace thumbnail the definitive original?
Not necessarily. It may be a cached or resized rendering. Follow the contract’s metadata and media references to understand the intended source.