CashTokens

CashTokens are native tokens on Bitcoin Cash, meaning that they are validated by each full node on the network and their transaction rules checked by each miner when constructing new blocks. CashTokens added fungible and non-fungible token primitives. CashTokens was first proposed in February of 2022 and actived on Bitcoin Cash mainchain in May of 2023.

tip

The specification for CashTokens is the 'CHIP-2022-02-CashTokens: Token Primitives for Bitcoin ' document.

CashTokens Utxo data

To understand CashTokens it is helpful to start with the layout of the UTXO data. In the networkProvider data from the SDK, the token property contains the new CashTokens fields:

interface Utxo {
  txid: string;
  vout: number;
  satoshis: bigint;
  token?: TokenDetails;
}

interface TokenDetails {
  amount: bigint;
  category: string;
  nft?: {
    capability: 'none' | 'mutable' | 'minting';
    commitment: string;
  };
}

Note that a UTXO can hold both an amount of fungible tokens as well as an nft, as long as both have the same category (also reffered to as "tokenId").

CashTokens introspection data

While CashTokens might seem overwhelming at first, realize that in contracts you will only use it through the following introspection details

• bytes tx.inputs[i].tokenCategory - tokenCategory + tokenCapability of a specific input.
• bytes tx.inputs[i].nftCommitment - NFT commitment data of a specific input.
• int tx.inputs[i].tokenAmount - Amount of fungible tokens of a specific input.

and their equivalent for outputs:

• bytes tx.outputs[i].tokenCategory - tokenCategory + tokenCapability of a specific output.
• bytes tx.outputs[i].nftCommitment - NFT commitment data of a specific output
• int tx.outputs[i].tokenAmount - Amount of fungible tokens of a specific output.

CashTokens Gotchas

There are two important "gotchas" to be aware of when developing with CashTokens in smart contracts for the first time

1) tokenCategory contains the nft-capability

bytes tx.inputs[i].tokenCategory

When accessing the tokenCategory through introspection the result returns 0x when that specific item does not contain tokens. If the item does have tokens it returns the bytes32 tokenCategory. When the item contains an NFT with a capability, the 32-byte tokenCategory is concatenated together with 0x01 for a mutable NFT and 0x02 for a minting NFT.

2) tokenCategory encoding

The tokenCategory introspection variable returns the tokenCategory in the original unreversed order, this is unlike wallets and explorers which use the reversed byte-order. So be careful about the byte-order of tokenCategory when working with BCH smart contracts.

// when using a standard encoded tokenId, reverse the hex before using it in your contract
const contract = new Contract(artifact, [reverseHex(tokenId)], { provider })

generally not recommended to do the byte-reversal in script

  // NOT THIS
  require(tx.inputs[0].tokenCategory == providedTokenId.reverse());

3) "invisibe" empty nfts

Because the nft-capability has no separate introspection item, and nothing is appended to the tokenCategory in case of capability none, empty nfts can be "invisibe" when combined with fungible tokens.

  // Input 0 has an empty nft (commitment 0x) with providedTokenId
  // If there was no empty nft the tokenCategory would return 0x
  require(tx.inputs[0].nftCommitment == 0x);
  require(tx.inputs[0].tokenAmount == 0);
  require(tx.inputs[0].tokenCategory == providedTokenId);

contrast this with the following scenario where there is also fungible tokens of the same category:

  // Input 0 might or might not have an empty nft (commitment 0x) with providedTokenId
  // Either way, the tokenCategory would return providedTokenId
  require(tx.inputs[0].nftCommitment == 0x);
  require(tx.inputs[0].tokenAmount == 10);
  require(tx.inputs[0].tokenCategory == providedTokenId);