Update docs CAIP-350 #395
Open
Update docs CAIP-350 #395
Conversation
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
This reverts commit 084ba91.
bumblefudge
reviewed
Jan 21, 2026
| - [ERC-7930]'s Interoperable Address and [ERC-7930]'s Interoperable Name of the ecosystem's chain references | ||
| - [ERC-7930]'s Interoperable Address and [ERC-7930]'s Interoperable Name of the ecosystem's addresses *for all address formats of said ecosystem* | ||
| Chain References: | ||
| - **customary text ↔ standard text**: Between customary chain reference text formats of the ecosystem (which may also be described in [CAIP-2]) and a standard text representation |
Collaborator
There was a problem hiding this comment.
This is kind of confusing because [CAIP-2] profiles per namespace already unambiguously convert between customary text and [a slightly different, in some cases] standard text... I think it would help to better explain that the "standard text" here is a slight variant of CAIP-2 that is identical for many namespaces but for others less lossy.
Author
There was a problem hiding this comment.
I added a new section titled “CAIP-2/CAIP-10 Compatibility.”
bumblefudge
requested changes
Jan 21, 2026
Collaborator
bumblefudge
left a comment
bumblefudge
left a comment
There was a problem hiding this comment.
Other than making more explicit the relationship between CAIP-2 and CAIP-350 in the ## Specification section, I think the changes are an improvement on the existing text and seem R2G
CAIP-350 has been updated based on the feedback
bumblefudge
reviewed
Jan 29, 2026
| #### CAIP-2/CAIP-10 Compatibility | ||
| The "standard text" in CAIP-350 profiles is a variant of [CAIP-2]/[CAIP-10] that is identical for most namespaces, but less lossy for those where length restrictions cause truncation (e.g., Solana's genesis blockhash). | ||
|
|
||
| Each CAIP-350 profile MUST state whether its standard text differs from [CAIP-2]/[CAIP-10], and how. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This update includes two main changes:
<namespace>:<chainReference>. This improves clarity and ensures consistency across all namespace profiles, where each profile now defines only the<chainReference>portion.