Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate UAN #683

Closed
Keith-CY opened this issue Jun 5, 2024 · 4 comments
Closed

Deprecate UAN #683

Keith-CY opened this issue Jun 5, 2024 · 4 comments
Assignees
Labels

Comments

@Keith-CY
Copy link
Member

Keith-CY commented Jun 5, 2024

The name convention at https://github.com/janx/rfcs/blob/universal-asset-notation/rfcs/0000-universal-asset-notation/0000-universal-asset-notation.md will be deprecated.

There are two groups of token named in UAN

  1. Tokens issued before UAN, their UANs are marked by the explorer team;
  2. Tokens issued after UAN, their UANs are specified by their issuers;

For type 1, their display name could be reset to the original one;
For type 2, their display name can remain unchanged because they are specified by the owners/issuers.

@Sven-TBD
Copy link
Contributor

Sven-TBD commented Jun 5, 2024

@Keith-CY Hi, Chen, Is there any announcement for this change by CKB official channel? Coz some assets' name may change following the explorer which I think worth an announcement.
We can help change the name backend here. cc @zmcNotafraid

@Keith-CY
Copy link
Member Author

Keith-CY commented Jun 5, 2024

@Keith-CY Hi, Chen, Is there any announcement for this change by CKB official channel? Coz some assets' name may change following the explorer which I think worth an announcement. We can help change the name backend here. cc @zmcNotafraid

It can be held on until the PR of this proposal is closed
nervosnetwork/rfcs#335

@Keith-CY
Copy link
Member Author

Updated on the mainnet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants