Conversation
Adds an asset specification to the existing cosmos namespace, covering 299 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
cosmosnamespace. The CAIP-2 profile is already ratified and is not touched.Who wrote this
I do not represent the cosmos ecosystem. I maintain FAR, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name 299 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 cosmos community to correct, adopt or replace.
Asset namespaces
slip44, bank, ics20, factory, cw20, cw721, snip20, snip721What this profile establishes
An IBC denom hash is chain-relative. The same underlying asset has a different
ibc/…hash on every chain, because the hash covers the full trace path. Socosmos:osmosis-1/ics20:<hash>andcosmos:juno-1/ics20:<other hash>can be the same economic asset and neither identifier reveals it. The profile states plainly that it cannot express that relationship, and why: SHA-256 is one-way, the counterparty chain-id needs a channel→connection→client walk, and unwinding is not uniquely defined. Equivalence has to be curated metadata.A measured design decision. The
factory/prefix is stripped rather than carried. Across a 2,000-denom live sample from Osmosis, 7 encode to 130 characters with the prefix retained — over CAIP-19's 128-char limit — and stripping brings every one of them under it.slip44:118is overloaded and made unrepresentable by restriction rather than discouraged by convention: chain-registry declares coin type 118 for Osmosis, Juno, Celestia, Archway, Neutron and Stargaze, socosmos:osmosis-1/slip44:118would be ambiguous between OSMO and ATOM-on-Osmosis.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.