You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: