Keep track of Sovereign light client implementation

[Farhad-Shabani]

Background

This issue serves as a record of the evolving challenges and milestones in our ongoing pursuit of implementing a Sovereign light client running on Cosmos chains. As we progress, we will update the following list of essential steps:

Tasks

Beta Give feedback

1. Draft ADR for Sovereign IBC light client implementation #149
   documentation +1
   
2. Initial CosmWasm client implementation for Sovereign rollups on cosmos chains #18
   sov-light-client +1
   
3. Resolve "unsupported import" error for Sovereign light client WASM file #20
   bug sov-light-client +2
4. Determine aggregated proof data structure #53
   relayer sov-light-client +2
5. Implement verify_membership and verify_non_membership methods #98
   2 of 2
   sov-light-client +1
   
6. Implement verify_client_message method for DA (Celestia) part #115
   1 of 1
   sov-light-client +1
   
7. Implement check_misbehaviour method for DA(Celestia) part #116
   1 of 1
   sov-light-client +1
   
8. Implement verify_upgrade_client method #120
   sov-light-client +1
   
9. Implement client recovery methods #124
   3 of 3
   sov-light-client +1
   
10. Ensure light client uniqueness for each rollup using code_commitment and genesis_state_root #129
    sov-light-client +1
    
11. Implement consensus state pruning on client updates #131
    sov-light-client +1
12. Enhancing light client implementation to address shortfalls #139
    sov-light-client +1
    
13. Migrate CosmWasm integration codebase to ibc-rs and import Context from there #143
    sov-light-client +1
    
14. Determine how to integrate ZK Verifier into Sovereign Light Clients #27
    explore sov-light-client +2
15. Implement naive ZK Wasm client that allows state transition with a trivial ZK program #28
    explore sov-light-client +2
16. Requirements from Sovereign SDK for provisioning client-side libraries #55
    sov-sdk +1