CIP-25

Overview

CIP-25 defines a widely used metadata structure for Cardano native assets, especially NFTs and media tokens. The metadata is placed under label 721 in a minting transaction and organized by policy ID and asset name, with fields such as name, image, media type, and additional properties. The asset itself remains a native ledger object; the metadata association is interpreted by wallets, marketplaces, and indexers. CIP-25 is best suited to mostly static metadata and is not directly inspectable by Plutus validators in the same way as datum-based state.

Implementers should follow the active version’s encoding rules, preserve exact policy and asset identifiers, and validate referenced content. They should not assume off-chain URLs remain available or that metadata proves copyright, authenticity, or issuer identity.

CIP-25 should be implemented against an exact document revision, status, and activation context. Draft, final, optional, and network-activated specifications have different authority, and similarly named deployments may support different subsets or extensions. Implementations should validate normative requirements, encodings, error behavior, security conditions, and test vectors, including malformed and boundary inputs that ordinary happy-path tests miss. Conformance to CIP-25 requires more than matching a field name or example.

Teams adopting CIP-25 should track errata, compatibility changes, and the deployed software versions that enforce it. A published standard does not prove universal adoption, safe implementation, or activation on a particular blockchain or payment network. This allows reproducible debugging when a later upgrade changes parsing, validation, signing, or interoperability behavior. Operational records for CIP-25 should retain the version and configuration used for each relevant transaction or message.