While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined. On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state. On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant). This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it. A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information. The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity. After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself. Read more on Kas-Smiths: kas-smiths.org/t/kcc-23-conv… Or read the KCC draft: github.com/kaspanet/kccs/pul…