BRC-92 Tokens

Mandala Token Protocol (Withdrawn)

Withdrawal notice This standard has been withdrawn and its normative content removed. It defined a minimalist token protocol: outputs prefixed with ! ( 0x21 ), followed by a genesis-outpoint assetId and an amount, all dropped before an arbitrary locking script. Issuance, redemption and recovery were managed through a chain of issuer-authorized outpoints. The

Deggen (deggen@kschw.com) Status: Withdrawn by the author.

How it connects

Relationships

Authoritative content mirror

Full upstream text

View source ↗
Rendered from tokens/0092.md at the indexed upstream commit

Withdrawal notice

This standard has been withdrawn and its normative content removed. It defined a minimalist token protocol: outputs prefixed with ! (0x21), followed by a genesis-outpoint assetId and an amount, all dropped before an arbitrary locking script. Issuance, redemption and recovery were managed through a chain of issuer-authorized outpoints.

The author withdrew it in favor of a single fungible token specification. The name Mandala tokens now refers to BRC-162, which keeps this protocol's push-and-drop prefix and uses the BSV-21 token model. New fungible tokens SHOULD be issued under BRC-162.

The formats are not compatible on-chain. A BRC-92 output's first push is the 1-byte ! marker, which is not a valid BRC-162 token id, so BRC-92 outputs are not BRC-162 outputs. The NFT and BoundKey constructions described here are not carried forward.

BRC-107 and the documents that extend it build on the format defined here. The last version of this document with its full content is available in the repository history.