Refactor client-related APIs for modularity and allow independent ICS-02 integration #1114
Labels
A: breaking
Admin: breaking change that may impact operators
O: decoupling
Objective: aims to separate concerns and cause to independent, reusable components
O: usability
Objective: aims to enhance user experience (UX) and streamline product usability
Summary
Reorganizing and simplifying client-related APIs under the various
ValidationContext
andExecutionContext
traits at different levels in ICS-24, ICS-02, and ICS-07 crates, and consolidating them primarily under the ICS-02 client validation and execution contexts.Objective
Enhance API delineation to facilitate modular integration of specific client state implementation based on ibc-rs without mandating to implement all the IBC stack. (Namely not requiring to implementing all the methods under the top-level
Validation/ExecutionContext
traits. This change would result in:Remark
Given the scope of this issue which will include a substantial number of breaking changes, it would be more efficient to communicate and execute this enhancement through an ADR.
The text was updated successfully, but these errors were encountered: