BCMR on Bitcoin Cash
Make CashTokens easier for people to recognize and use.
BCMR gives Bitcoin Cash wallets and apps a structured way to show token names, symbols, icons, and other useful information. This guide explains how metadata connects an on-chain token to a better product experience.
Specification status: draft application-layer standard.
Reference metadata flow · Client behavior can vary
What BCMR contributes
Turn token IDs into useful product experiences.
A category identifies a CashToken, but people need more context than a long identifier. BCMR gives wallets and apps a structured way to turn that identifier into useful information without putting every display field directly into each transaction.
On-chain reference
Use the category ID as the protocol-level reference for tokens belonging to that category.
Display fields
Names, symbols, decimals, and descriptions help a wallet explain what a user holds.
Media and links
Icons and resource URIs can connect a token entry to a richer product experience.
Resolution behavior
Clients need validation, caching, and fallback behavior when a registry document is unavailable.
Metadata resolution
From an on-chain ID to a name users understand.
Wallets and indexers connect the on-chain category to the information a user sees. A resilient implementation validates registry data, handles unavailable sources, and keeps the asset reference separate from its display name.
A token-bearing output provides the category that identifies the asset on-chain.
A wallet or indexer can obtain metadata from an embedded, imported, DNS-resolved, or chain-resolved BCMR source.
Validate the registry according to its resolution method, verify published content hashes where applicable, and cache metadata using an explicit update policy.
The application shows the metadata when available and falls back to the category when it is not.
BCMR in the product stack
From token creation to a clear wallet experience.
Issuance
Choose the token category and the metadata publication strategy the product intends to use.
Registry
Publish a discoverable document that clients can resolve and validate.
Indexer
Associate token-bearing UTXOs with balances, holders, and metadata for application queries.
Wallet
Turn the resolved data into a clear asset list, history, and transaction preview.
Metadata and transaction authority
Two layers with different jobs.
BCMR enriches the wallet experience with token identity and display information. The on-chain category remains the asset reference, and BCH consensus determines whether a transaction is valid.
Metadata does not change whether a transaction meets BCH consensus rules.
Wallets should remain useful when a document, image, or registry endpoint cannot be reached.
Clients should define which registries or resolution methods they trust, how updates are authenticated, when cached data expires, and how the interface falls back when metadata is unavailable.
Continue the technical path
Move from metadata to the CashToken primitive, infrastructure, wallet behavior, or implementation resources.
Related reading
Building a token-aware BCH product?
Bring the category, wallet surface, metadata, and integration problem. We can help connect the layers.