Conversation
Adds an asset specification to the existing tron namespace, covering 92 assets that a cross-reference project needs to name. The CAIP-2 profile is unchanged.
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a CAIP-19 asset profile to the existing
tronnamespace. The CAIP-2 profile is already ratified and is not touched.Who wrote this
I do not represent the tron ecosystem. I maintain FAR, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name 92 assets on this chain. CASA's README invites profiles added to an existing namespace, so this documents how assets are addressed rather than claiming to speak for anyone. Offered for the tron community to correct, adopt or replace.
Asset namespaces
slip44, trc10, trc20, trc721, trc1155What this profile establishes
No percent-encoding is required anywhere — base58check and decimal are already inside the reference charset. Stated as a positive finding.
Base58Check is canonical, decided by the namespace's own existing work: the ratified
tron/caip10.mdalready mandates exactly that regex for accounts, so a different asset form would leave one namespace describing the same 20 bytes two ways. It also carries a checksum, where the hex form has 2^40 spellings and no EIP-55 equivalent.TRC-10 names are massively duplicated, verified live.
getassetissuelistbyname("BitTorrent")returns 13 distinct assets all named BitTorrent/BTT with different issuers;SEEDreturns 7. AndBTTspans standards — TRC-10 id 1002000 at 6 decimals and a TRC-20 contract at 18 decimals are different assets with different scaling. That is the argument fortrc10as its own namespace.Every example was verified against a live node or explorer; anything that could not be verified is marked as such in the document rather than asserted.
discussions-topoints at 0xcounting/FAR#1.