Conversation
Adds an asset specification to the existing chia namespace, covering 4 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
chianamespace. The CAIP-2 profile is already ratified and is not touched.Who wrote this
I do not represent the chia ecosystem. I maintain FAR, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name 4 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 chia community to correct, adopt or replace.
Asset namespaces
slip44, cat, nftWhat this profile establishes
Each asset kind is written the way its own standard writes it. CHIP-0005 makes the
nft1…bech32m string normatively the NFT's id and its checksum catches transcription errors; CAT asset ids have no standardised bech32m form, so inventing acat1…encoding would be making up a Chia standard.A collision inherited from the chain, which the profile cannot repair. The CAT1→CAT2 migration changed the outer puzzle, not the TAIL — and the asset id is the TAIL hash. So one asset id names both a token's CAT1 and CAT2 coins, and CAT1 coins still exist on chain.
catis scoped to CAT2 and consumers are required to confirm the outer puzzle.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.