CIP-68

Overview

CIP-68 defines a Cardano metadata pattern using paired native assets and an output carrying an inline datum. A reference token identifies and controls the metadata state, while a user token represents the asset held or transferred by users. Unlike transaction-metadata approaches, the datum can be inspected by Plutus validators and updated under rules enforced by a smart contract. Token labels help wallets and indexers classify the reference and user assets, but correct interpretation requires following the standard’s encoding.

Applications should verify policy IDs, token labels, the reference NFT, datum schema, and controlling script before displaying metadata. Mutability must be communicated clearly, because an image or property may change after purchase if the script permits an authorized update.

Conformance to CIP-68 requires more than matching a field name or example. Implementations should validate normative requirements, encodings, error behavior, security conditions, and test vectors, including malformed and boundary inputs that ordinary happy-path tests miss. A published standard does not prove universal adoption, safe implementation, or activation on a particular blockchain or payment network. Teams adopting CIP-68 should track errata, compatibility changes, and the deployed software versions that enforce it.

Operational records for CIP-68 should retain the version and configuration used for each relevant transaction or message. This allows reproducible debugging when a later upgrade changes parsing, validation, signing, or interoperability behavior. Draft, final, optional, and network-activated specifications have different authority, and similarly named deployments may support different subsets or extensions. CIP-68 should be implemented against an exact document revision, status, and activation context.