Conversation
Adds an asset specification to the existing starknet namespace, covering 40 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
starknetnamespace. The CAIP-2 profile is already ratified and is not touched.Who wrote this
I do not represent the starknet ecosystem. I maintain FAR, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name 40 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 starknet community to correct, adopt or replace.
Asset namespaces
erc20, erc721What this profile establishes
The normalisation rule is the contribution:
0x+ exactly 64 lowercase hex, non-canonical input rejected rather than repaired. A Starknet address is a field element and is not fixed width — the node itself emits class hashes at 62 and 63 digits.Proven live rather than asserted: four spellings of the ETH contract — 64-digit padded, 63-digit stripped, uppercase, and no
0xat all — return the same class hash from the same node, and all four use only characters theasset_referencecharset permits. It is a real CAIP-19 hazard.No
slip44, stated normatively. Starknet has no chain-native balance; STRK and ETH are both ordinary contracts. SLIP-0044 registering STRK as 9004 is not evidence otherwise — a coin type is a key-derivation path component, not a protocol-level balance.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.