Add RGB++ Assets Convention Rules doc #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Flouse
requested changes
Jul 2, 2024
|
|
||
| ## Background | ||
|
|
||
| xUDT (RGB++) assets on CKB similar to ERC20 assets on Ethereum in that they lack protocol-level uniqueness constraints for token names. |
There was a problem hiding this comment.
Suggested change
| xUDT (RGB++) assets on CKB similar to ERC20 assets on Ethereum in that they lack protocol-level uniqueness constraints for token names. | |
| xUDT (RGB++) assets on CKB are similar to ERC20 assets on Ethereum in that they lack protocol-level uniqueness constraints for token names. |
Comment on lines
+7
to
+8
| Considering the conventions of the Bitcoin ecosystem, Considering the conventions of the Bitcoin ecosystem, it is necessary to introduce | ||
| standards regarding uniqueness and length. |
There was a problem hiding this comment.
Suggested change
| Considering the conventions of the Bitcoin ecosystem, Considering the conventions of the Bitcoin ecosystem, it is necessary to introduce | |
| standards regarding uniqueness and length. | |
| Considering the conventions of the Bitcoin ecosystem, it is necessary to introduce standards regarding uniqueness and length. |
| - 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: |
There was a problem hiding this comment.
Suggested change
| - For browsers: | |
| - For blockchain explorers: |
|
|
||
| ## Letters | ||
| - For exchanges, only the ASCII visible character subset is supported. | ||
| - For wallets and browsers, the supported character range includes: |
There was a problem hiding this comment.
Suggested change
| - For wallets and browsers, the supported character range includes: | |
| - For wallets and explorers, the supported character range includes: |
|
|
||
| ## Verification | ||
| - Whitelisted assets are set to bypass the rules mentioned above. | ||
| - To get whiltelist, To get on the whitelist, project owners should submit their token information to Cell Studio’s GitHub repository. |
There was a problem hiding this comment.
Suggested change
| - To get whiltelist, To get on the whitelist, project owners should submit their token information to Cell Studio’s GitHub repository. | |
| - To get on the whitelist, project owners should submit their token information to [TODO]. |
| - Issuance mark: `L1 issue` / `L2 issue` to identify where the coins are issued, on Bitcoin with `rpgpp_lock` or CKB with normal lock; | ||
| - Supply mark: `Limited supply` / `Unlimited supply` to identify whether a coin could be issued arbitrarily. | ||
|
|
||
| > Note: The [issue For Support tags of xudt #620](https://github.com/Magickbase/ckb-explorer-public-issues/issues/620) defines the |
There was a problem hiding this comment.
Suggested change
| > Note: The [issue For Support tags of xudt #620](https://github.com/Magickbase/ckb-explorer-public-issues/issues/620) defines the | |
| > Note: The [issue For Support tags of xudt #620](https://github.com/Magickbase/ckb-explorer-public-issues/issues/620#issuecomment-2060182586) defines the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2.Add this doc to the Readme