Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bumblefudge merged 2 commits into from
Nov 7, 2025
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
08ad356
docs: update CAIP-350 namespace profile and remove deprecated ERC-778…
0xMonoAx Oct 28, 2025
46844d4
docs: update CAIP-350 namespace profile to align with the new template
0xMonoAx Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions eip155/caip350.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,11 +65,11 @@ For text representation, the 20 bytes of EVM addresses should be hexadecimal-enc
This standard deliberately does not define the text representation of EVM addresses if they are extended in the future, since it's not possible to know which human-readable representation will be more familiar to users in such hypothetical scenario.
This profile should be amended in the future to reflect it in such a case.

##### Text representation -> customary text address formats conversion
##### Text representation -> native representation conversion

See [EIP-55].

##### Customary text addresses -> text representation conversion
##### Native representation -> text representation conversion

See [EIP-55].

Expand All @@ -90,13 +90,17 @@ Specified in [EIP-55].

See [EIP-55].

### Error handling

Copy link
Copy Markdown
Collaborator

@bumblefudge bumblefudge Oct 31, 2025

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

@0xMonoAx 0xMonoAx Nov 2, 2025

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

### Implementation considerations

### Extra considerations

Wallets and other software are expected to be able to fetch the extra information needed to convert from [CAIP-2] to this standard.

## 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

@0xteddybear 0xteddybear Oct 28, 2025

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

@0xMonoAx 0xMonoAx Oct 28, 2025

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.

[^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.
[^2]: With EVM Object Format as a prerequisite, Address Space Expansion could be implemented. If that happens, expanded addresses may be represented in 32 bytes, but pre-expansion addresses must remain 20 bytes in order to preserve a consistent address.

[CAIP-2]: https://chainagnostic.org/CAIPs/caip-2
Expand Down
8 changes: 6 additions & 2 deletions solana/caip350.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,11 +63,11 @@ Solana addresses are 32-byte public keys, conventionally displayed to users as b

base58btc-encoded ASCII of the entire public key bytes.

##### Text representation -> customary text address formats conversion
##### Text representation -> native representation conversion

No transformation.

##### customary text addresses -> text representation conversion
##### native representation conversion -> text representation conversion

No transformation.

Expand All @@ -89,6 +89,10 @@ base58btc encoding

`DYw8jCTfwHNRJhhmFcbXvVDTqWMEVFBX6ZKUmG5CNSKK` -> `0xBA7A74F374AB05B70D114A78112EF0D3F0695A819572C79710B5372000D81AE2`

### Error handling

### Implementation considerations

### Extra considerations

Wallets and other software are expected to be able to fetch the extra information needed to convert from [CAIP-2] to produce the corresponding identifier defined by this standard.
Expand Down