Conversation
Adds an asset specification to the existing mvx namespace, covering 35 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
mvxnamespace. The CAIP-2 profile is already ratified and is not touched.Who wrote this
I do not represent the mvx ecosystem. I maintain FAR, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name 35 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 mvx community to correct, adopt or replace.
Asset namespaces
slip44, esdtWhat this profile establishes
Zero percent-encoding, with the arithmetic: an ESDT identifier is ≤17 characters against a 128-character budget and every character is already in the charset. The reference is byte-identical to the on-chain string.
Verified by sweep, not by sample: 2,000/2,000 mainnet fungible tokens and 500/500 collections match the identifier regex, and 1,500/1,500 NFT/SFT instances have a third segment that decodes to exactly the API's
nonce.EGLD-000000is a real trap. The API serves it, described as "the identifier used when wanting to transfer EGLD via a MultiESDTNFTTransfer" — zero supply, no issuer. It satisfies the profile's own regex, so no validator rejects it; the exclusion had to be written as an explicit rule. Native EGLD MUST beslip44:508.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.