Conversation
Adds an asset specification to the existing polkadot namespace, covering 175 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
polkadotnamespace. The CAIP-2 profile is already ratified and is not touched.Who wrote this
I do not represent the polkadot ecosystem. I maintain FAR, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name 175 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 polkadot community to correct, adopt or replace.
Asset namespaces
slip44, asset, pool, foreign, nfts, uniquesWhat this profile establishes
A total collision, not an incidental one. Enumerating the full id spaces on Asset Hub: 762
Assetsids and 84PoolAssetsids — and every one of the 84 pool ids is also a liveAssetsid.Assets:56is UNION;PoolAssets:56is an AMM share. A profile with a singleasset:namespace would mis-resolve every pool share on the chain. Hence one namespace per on-chain index.Bittensor subnet alpha is deliberately excluded, with reasons:
SubnetLimitis 128 and the chain reportsTotalNetworks = 129right now, so the table is full and every new registration recycles a dissolved subnet's netuid — and dissolution removes all its storage. Alpha is also a share in a per-subnet staking pool attached to a hotkey, not an entry in an asset index, so there is no index for a reference to key into. A constructive alternative is offered to the Bittensor community: pin the registration block alongside the slot.No percent-encoding, deliberately — the profile binds every reference to the on-chain storage key rather than a rendered name, because one live asset's name is
道阻且长，温暖坚定-爱情/love.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.