sovereign-ibc
sovereign-ibc copied to clipboard
informalsystems
Implementation of IBC modules by `ibc-rs` that can run with Sovereign SDK rollups
## Description This study aims to determine the information that Hermes needs from the DA layer (in our case Celestia) to perform its relaying job. As well as how to...
## Context To enable relayers to craft **`MsgUpdateClient`**, it's essential to query the aggregated proof data from the DA layer at intervals corresponding to the number of headers it covers....
## Background Right now, there are ambiguities about the best way to fit a ZK verifier into Sovereign light clients. This issue is about figuring out how to smoothly add...
## Background To properly support Sovereign SDK rollups, we require client-serving libraries akin to **`tendermint-rs`**. This library should provide integration kits and cater to the specific needs of IBC operators,...
## Background We have made significant progress on implementing the Sovereign IBC module, with most of its functionality already in place and maintained within the `sov-ibc` and `sov-ibc-transfer` crates. However,...
## Background This issue tracks the implementation of essential integration tests (As outlined in the following task list) aimed at comprehensively covering various IBC relaying scenarios between Sovereign Rollups and...
## Background `sov-ibc-mocks` implementation is aligned with the design pattern of context generic programming (CGP) which is used by Hermes SDK and this approach inspired from implementation of [`relayer-cosmos-mock`](https://github.com/informalsystems/hermes-sdk/tree/main/crates/relayer-cosmos-mock) there....
## Background Right now, it’s not clear if anything pertaining to the ZK part of light client should get stored (within the IBC store of Cosmos SDK chains) and updated...
### Background To effectively engage with the WASM file of the Sovereign light client on Cosmos SDK chains, we should set up a WASM-enabled Cosmos node and come up with...
## Problem Statement Ideally, the `sov-ibc` module should be divided into two distinct modules, e.g., `sov-ibc-core` and `sov-ibc-router`. This separation ensures that `sov-ibc-core` remains integrated with any IBC application without...
Metadata
Owner
Metadata
Implementation of IBC modules by `ibc-rs` that can run with Sovereign SDK rollups