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

Extract light client implementations into separate crates #2335

Closed
5 tasks
hu55a1n1 opened this issue Jun 24, 2022 · 0 comments · Fixed by #2483
Closed
5 tasks

Extract light client implementations into separate crates #2335

hu55a1n1 opened this issue Jun 24, 2022 · 0 comments · Fixed by #2483
Assignees

Comments

@hu55a1n1
Copy link
Member

Summary

The module and relayer code relies heavily on enums such as AnyClientState, AnyClient, etc. which define one variant per type of light-client supported. As we look to add support for more light-clients, it would be great for the module code to be agnostic to the light-client implementation. This will also light-client implementations to be hosted outside of the ibc-rs repo and maintained independently.

Problem Definition

Tight coupling with Any* types and circular dependency between light-client code and module code.

Proposal

Remove all occurrences of Any* enums and solve circular dependencies between crates if any.

Acceptance Criteria

Light clients can be hosted outside of the ibc-rs repo.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
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 a pull request may close this issue.

1 participant