Background
xUDT (RGB++) assets on CKB are similar with ERC20 assets on Ethereum, they lack protocol-level uniqueness constraints for token names. Considering the convention of the Bitcoin ecosystem, we need to introduce some standard regarding uniqueness and length.
Scope
-
The following conventions cover inscription info cell & unique cell, combining the two for processing. For example, they only allow one asset to use the same name among them.
-
These conventions only consider the
Symboland do not consider theNamefield.
# Unique cell
{
"code_hash": "0x2c8c11c985da60b0a330c61a85507416d6382c130ba67f0c47ab071e00aec628",
"hash_type": "data1",
"out_point": {
"tx_hash": "0x67524c01c0cb5492e499c7c7e406f2f9d823e162d6b0cf432eacde0c9808c2ad",
"index": "0x0"
},
"dep_type": "code"
}
Name confliction
- Only the first occurrence of a duplicate asset name on the chain is acknowledged; subsequent occurrences are marked as “duplicate”.
- Case sensitivity is ignored during duplicate comparison, meaning “Seal” is considered the same as “SEAL”.
- Any addition of invisible characters (including spaces) to the name, regardless of whether there are similar assets, is treated as a “duplicate”.
- For wallets and exchanges, duplicate assets are directly hidden.
- For browsers, “duplicate assets” are labeled as “Risk Asset - RGB++ incompatible”, while non-duplicate assets are labeled as “RGB++ Compatible”. In places where the aforementioned text is too long to display, symbols such as [!] and [+] are used for marking.
Letters
- For exchanges, only the ASCII visible character subset is supported.
- For wallets and browsers, the supported character range includes:
- ASCII visible characters subset
- A subset of emojis: to be determined
- For assets that use unsupported characters, the asset name is uniformly displayed as “INVALID”.
Length range
- Only assets with Symbol length of 4-5 characters are processed normally.
- Assets falling outside this range are treated as “duplicate assets”.
Verification
- There exists a whitelist that can override the above rules.
- This whitelist is hosted on Cell Studio’s GitHub repository. Project owners submit their token information, which is reviewed and released after verification. Assets listed on the whitelist are prioritized and displayed regardless of the above rules. Other assets with the same name are automatically marked as “duplicate assets”.
- As of now, there is no whitelist available.
Assets mark
Ecosystem apps should add label / mark for every asset to provide some critical information:
- Issuance mark:
L1 issue/L2 issueto identify where the coins are issued, on Bitcoin withrpgpp_lockor CKB with normal lock - Supply mark:
Limited supply/Unlimited supplyto identify whether a coin could be issued arbitrarily.