Skip to content
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.

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

solana-ibc: restrict port identifier and use more compact representation #116

Merged
merged 3 commits into from
Nov 24, 2023

Conversation

mina86
Copy link
Collaborator

@mina86 mina86 commented Nov 21, 2023

Restrict port identifier to be 12 alphanumeric characters. With that
restriction it’s now possible to decode the port using base64 encoding
to get 9 bytes. Those bytes can then serve as an internal port
identifier used with the trie and maps in private storage.

Issue: #35

Restrict port identifier to be 12 alphanumeric characters.  With that
restriction it’s now possible to decode the port using base64 encoding
to get 9 bytes.  Those bytes can then serve as an internal port
identifier used with the trie and maps in private storage.

Issue: #35
@mina86 mina86 requested a review from blasrodri November 21, 2023 15:44
Copy link
Contributor

@blasrodri blasrodri left a comment

Choose a reason for hiding this comment

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

Can this also be extended to IBC go?

@mina86
Copy link
Collaborator Author

mina86 commented Nov 24, 2023

This is purely on the implementation side so the same approach works
under ibc-go. The spec describes this under ‘Identifier validation’
section of ICS
005
.

As far as I understand, by introducing this restriction we’re simply
restricting what ports can be bound but that’s just a matter for
whoever creates new connections to pick a supported port name.

@mina86 mina86 merged commit 4385d63 into master Nov 24, 2023
5 checks passed
@mina86 mina86 deleted the mpn/b branch November 24, 2023 17:08
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.

2 participants