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

Add support for custom client ids #360

Open
4 tasks
srdtrk opened this issue Mar 4, 2025 · 0 comments · May be fixed by #362
Open
4 tasks

Add support for custom client ids #360

srdtrk opened this issue Mar 4, 2025 · 0 comments · May be fixed by #362
Assignees
Labels
solidity Issues related to the solidity contracts type: feature Feature request

Comments

@srdtrk
Copy link
Member

srdtrk commented Mar 4, 2025

Summary

Right now, every client has a universal client id such as client-0. This proposes letting an authority use custom client ids such as cosmoshub. Similar to PORT_CUSTOMIZER_ROLE in ICS26Router.sol.

Permissionless users would still be able to register their light clients using the universal client ids.

Constraints

The custom client ids must not be allowed to be prefixed with client- or channel-. They must go through the same string validation as port ids.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
  • Estimate provided
@srdtrk srdtrk added solidity Issues related to the solidity contracts type: feature Feature request labels Mar 4, 2025
@srdtrk srdtrk self-assigned this Mar 4, 2025
@srdtrk srdtrk added this to IBC Mar 4, 2025
@github-project-automation github-project-automation bot moved this to Backlog in IBC Mar 4, 2025
@srdtrk srdtrk moved this from Backlog to In progress in IBC Mar 4, 2025
@srdtrk srdtrk linked a pull request Mar 4, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solidity Issues related to the solidity contracts type: feature Feature request
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

1 participant