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

[Routing] Permissions for registries #4442

Closed
Tracked by #4344
nicolaslara opened this issue Feb 27, 2023 · 0 comments · Fixed by #4553
Closed
Tracked by #4344

[Routing] Permissions for registries #4442

nicolaslara opened this issue Feb 27, 2023 · 0 comments · Fixed by #4553
Assignees

Comments

@nicolaslara
Copy link
Contributor

Background

Epic: #4344

We should allow chains to update their registries directly.

For example, if juno is upgrading their default channel to stargaze, then their governance should be allowed to send an ibc-hooks message to the registries for getting that updated.

Suggested Design

Open to design changes, but some considerations:

  • Osmosis governance should always be allowed to control these
  • There should be a waiting period for these changes to take effect where it could be "appealed"
  • Adding new information should be easy, but changing should be either not allowed or harder (for security purposes)

Acceptance Criteria

  • All existing tests pass
  • Updates have been tested
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants