An AI-generated collectible can change its preview, attributes or associated media while retaining the same token ID. This creates a gap between what a buyer saw and what a marketplace displays later. Two mature Ethereum standards clarify parts of that problem: ERC-721 identifies the NFT interface, while ERC-4906 helps consumers detect certain metadata changes. Neither standard by itself proves artistic provenance, copyright ownership or the accuracy of a seller’s marketing. Buyers and marketplaces need an evidence layer above the event stream.
Separate token ownership from creative rights
ERC-721, created in January 2018, defines a standard interface for tracking and transferring non-fungible tokens. The token can identify a scarce on-chain object without transferring copyright, trademark rights or every right to the media to which its metadata points. A marketplace listing must therefore distinguish the current token owner, the creator of the image or model output, and the license a buyer receives. For AI-generated art, capture the uploader’s authorization to use relevant inputs and the policy for likenesses, logos or borrowed works. Do not infer rights from a tokenURI that resolves successfully. A buyer should be able to see a compact license summary before purchase and retrieve the complete terms afterward. Changing a preview must not silently rewrite the rights promised at sale.
Read ERC-4906 events as change notices, not truth proofs
ERC-4906, created in March 2022, specifies MetadataUpdate and BatchMetadataUpdate events for notifying listeners when token JSON metadata changes. It is an optional extension to ERC-721. A supporting marketplace can respond by fetching tokenURI information again, validating its schema and updating a cached preview. Yet an emitted event is not cryptographic proof that every off-chain field is trustworthy. A dishonest issuer can publish a deceptive description, and an off-chain host may serve changing bytes. Build a monitoring rule that records the old and new metadata hashes, the event block, the resolved URL and the fetch result. If the fetch fails, show a stale-state label rather than quietly displaying the previous image as fresh. Tell buyers which facts are on-chain and which depend on external services.
Design a provenance record that survives CDN changes
A robust record captures the media digest, model or workflow label where appropriate, a creator declaration, versioned licensing terms and the metadata JSON digest. A CDN URL or an IPFS pointer can help locate content, but location and content integrity are different questions. Use content hashes where available and describe any mutable gateway mapping. Record who approved the initial listing and who can authorize later changes. Compare media hashes before and after a metadata event so a simple description correction is distinguishable from replacement artwork. Where personal data or confidential prompts are involved, keep the sensitive inputs out of public blockchain storage; link to a consent-controlled evidence file instead. An immutable record of an impermissibly disclosed portrait would compound the harm. Good provenance is selective and rights-aware, not an excuse to publish every prompt.
Model buyer-facing change severity
Not all metadata changes justify the same alert. A corrected typo, a changed thumbnail crop, a new attribute affecting utility, and a swapped underlying video carry different economic implications. Define severity before launch using an explicit matrix: informational change, material presentation change, rights or access change, and identity or asset replacement. Trigger user notice for material categories, identify the old and new values, and preserve the listing snapshot seen when a purchase occurred. A marketplace should not imply that every refresh is suspicious, but it should resist silent edits to economic terms or licensing. Provide an appeal path for sellers to explain legitimate corrections. Review whether automated AI-generated metadata descriptions incorrectly claimed a feature or rarity. Independent moderation should be possible without deleting the evidence of what was originally shown.
Test broken indexers and contradictory copies
A realistic QA plan creates a token, reads tokenURI, modifies the JSON, emits MetadataUpdate, and verifies that the marketplace refreshes. Next, remove the event, send a duplicate event, update a contiguous range, return an invalid JSON response, and deliberately serve different content from two endpoints. A resilient indexer should de-duplicate events, apply block-order rules, record fetch failures and eventually reconcile state. One environment may see a newer cached preview than another: tell the user which version and timestamp they are viewing. Run permission checks on any function that emits metadata events; ERC-4906’s security notes emphasize appropriate authorization for off-chain changes. These tests examine consistency and disclosure, not investment performance. They also identify where a buyer could be misled by a perfectly valid token transfer paired with stale off-chain content.
Build an audit receipt for every material revision
For each material change, store the token contract and ID, previous content digest, new digest, revision reason, signer or authorized publisher, block reference and buyer notification status. Maintain a read-only history that a marketplace customer can inspect without exposing private personal data. In a hypothetical scenario, a buyer pays for an AI-generated video with commercial-use rights; a later metadata update removes that right. An event alert alone does not resolve the contractual dispute. The evidence ledger must identify the version purchased and the relevant contract or terms accepted. Measure how many revisions were correctly classified, how quickly pages refreshed and whether any purchase occurred while a material change was undisclosed. These operational measures are more defensible than promising that NFT infrastructure guarantees authenticity.
Illustrative process recommendations are editorial analysis, not protocol guarantees or measured production results.