Conversation
Adds an asset specification to the existing iota 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
iotanamespace. The CAIP-2 profile is already ratified and is not touched.Who wrote this
I do not represent the iota 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 iota community to correct, adopt or replace.
Asset namespaces
slip44, coin, objectWhat this profile establishes
Aligned deliberately with the sibling
suiprofile — same namespace names, same padded-address rule, same escape table — so a Move identifier does not acquire two spellings across two Move chains.A measured unrepresentable asset. The live generic type
0x107a::nft_output::NftOutput<0x2::iota::IOTA>normalises and encodes to 191 characters, over CAIP-19's 128-char cap. Implementations must fail rather than truncate or hash. Three possible resolutions are listed and handed to the IOTA community and the editors rather than decided unilaterally.A struct-name collision, live:
…::btc::BTCis published by three distinct packages on mainnet, one account holding what a struct-name matcher would read as "21,000,000 BTC".Related: #210 fixes a JSON-RPC method name in this namespace's CAIP-2 profile.
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.