Skip to content

Docs update namespace profiles for solana and eip155 to align with the new template#155

Merged
bumblefudge merged 2 commits intoChainAgnostic:mainfrom
0xMonoAx:docs--update-caip350-solana-eip155
Nov 7, 2025
Merged

Docs update namespace profiles for solana and eip155 to align with the new template#155
bumblefudge merged 2 commits intoChainAgnostic:mainfrom
0xMonoAx:docs--update-caip350-solana-eip155

Conversation

@0xMonoAx
Copy link
Copy Markdown
Contributor

  • Updates the EIP-155 profile with the new CAIP-350 structure and cleans up deprecated references
  • Applies the new CAIP-350 template to the Solana profile with updated sections for conversions and structure

Copy link
Copy Markdown
Contributor

@0xteddybear 0xteddybear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you implement the suggestion of removing the 'extra considerations' section, make sure to also remove it here. other than that lgtm

Comment thread eip155/caip350.md

## References

[^1]: This makes it possible to represent some chains using the full word as their chainid, which CAIP-2 does not support since the set of values representable with 32 `a-zA-Z0-9` characters has less than `type(uint256).max` elements. This is done in an effort to support chains whose ID is the output of `keccak256`, as proposed in [ERC-7785].
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this no longer the case? 👀

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ERC-7785 idea was dropped, and the decision was made to move forward with ERC-7930. You can read more here.

Comment thread eip155/caip350.md
See [EIP-55].

### Error handling

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are these placeholders for future error handling and implementation considerations? i'd rather have no sections than empty sections (I should probably add that to the CASA style guide and template files).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, since these are for future implementations, it makes sense to keep them only in the template for now to avoid having empty sections

@0xMonoAx 0xMonoAx requested a review from 0xteddybear November 2, 2025 22:08
@bumblefudge bumblefudge merged commit 9dfc61d into ChainAgnostic:main Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants