-
Notifications
You must be signed in to change notification settings - Fork 620
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
test(callbacks): simplified mock contract keeper's processCallback lo…
…gic (backport #4375) (#5882) * test(callbacks): simplified mock contract keeper's processCallback logic (#4375) * imp(callbacks/mock/contract_keeeper): improved contract keeper logic * imp(callbacks_test): fixed transfer_test.go * imp(callbacks_test): fixed ica_test.go * imp(callbacks_test): fixed fee_transfer_test.go * style(callbacks_test): removed unneeded gas_limit * style: ran golangci-lint * imp(callbacks_test): implemented simplified logic * imp(callbacks_test): removed unneeded variable * imp(callbacks): implemented some review feedback * docs(callbacks/simapp): updated godocs of mock contract keeper functions (cherry picked from commit ce3cfc0) # Conflicts: # modules/apps/callbacks/ibc_middleware_test.go * fix conflicts * fixing dead links * dead links * fix link --------- Co-authored-by: srdtrk <59252793+srdtrk@users.noreply.github.com> Co-authored-by: Carlos Rodriguez <carlos@interchain.io>
- Loading branch information
3 people
authored
Mar 22, 2024
1 parent
1b0372e
commit 7b03cfe
Showing
7 changed files
with
450 additions
and
111 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,153 @@ | ||
| <div align="center"> | ||
| <h1>ibc-go</h1> | ||
| </div> | ||
|
|
||
|  | ||
|
|
||
| <div align="center"> | ||
| <a href="https://github.com/cosmos/ibc-go/releases/latest"> | ||
| <img alt="Version" src="https://img.shields.io/github/tag/cosmos/ibc-go.svg" /> | ||
| </a> | ||
| <a href="https://github.com/cosmos/ibc-go/blob/main/LICENSE"> | ||
| <img alt="License: Apache-2.0" src="https://img.shields.io/github/license/cosmos/ibc-go.svg" /> | ||
| </a> | ||
| <a href="https://pkg.go.dev/github.com/cosmos/ibc-go?tab=doc"> | ||
| <img alt="GoDoc" src="https://godoc.org/github.com/cosmos/ibc-go?status.svg" /> | ||
| </a> | ||
| <a href="https://goreportcard.com/report/github.com/cosmos/ibc-go"> | ||
| <img alt="Go report card" src="https://goreportcard.com/badge/github.com/cosmos/ibc-go" /> | ||
| </a> | ||
| <a href="https://codecov.io/gh/cosmos/ibc-go"> | ||
| <img alt="Code Coverage" src="https://codecov.io/gh/cosmos/ibc-go/branch/main/graph/badge.svg" /> | ||
| </a> | ||
| </div> | ||
| <div align="center"> | ||
| <a href="https://github.com/cosmos/ibc-go"> | ||
| <img alt="Lines Of Code" src="https://tokei.rs/b1/github/cosmos/ibc-go" /> | ||
| </a> | ||
| <a href="https://discord.gg/AzefAFd"> | ||
| <img alt="Discord" src="https://img.shields.io/discord/669268347736686612.svg" /> | ||
| </a> | ||
| <a href="https://sourcegraph.com/github.com/cosmos/ibc-go?badge"> | ||
| <img alt="Imported by" src="https://sourcegraph.com/github.com/cosmos/ibc-go/-/badge.svg" /> | ||
| </a> | ||
| <img alt="Tests / Code Coverage Status" src="https://github.com/cosmos/ibc-go/workflows/Tests%20/%20Code%20Coverage/badge.svg" /> | ||
| <img alt="E2E Status" src="https://github.com/cosmos/ibc-go/workflows/Tests%20/%20E2E/badge.svg" /> | ||
| </div> | ||
|
|
||
| The [Inter-Blockchain Communication protocol (IBC)](https://ibcprotocol.dev/) allows blockchains to talk to each other. This end-to-end, connection-oriented, stateful protocol provides reliable, ordered, and authenticated communication between heterogeneous blockchains. | ||
|
|
||
| This IBC implementation in Golang is built as a Cosmos SDK module. To understand more about how to use the `ibc-go` module as well as about the IBC protocol, please check out the Interchain Developer Academy [section on IBC](https://tutorials.cosmos.network/academy/3-ibc/), or [our docs](https://ibc.cosmos.network/main/ibc/overview.html). | ||
|
|
||
| ## Roadmap | ||
|
|
||
| For an overview of upcoming changes to ibc-go take a look at the [roadmap](./docs/roadmap/roadmap.md). | ||
|
|
||
| This roadmap is also available as a [project board](https://github.com/orgs/cosmos/projects/7/views/25). | ||
|
|
||
| For the latest expected release timelines, please check [here](https://github.com/cosmos/ibc-go/wiki/Release-timeline). | ||
|
|
||
| For the latest information on the progress of the work or the decisions made that might influence the roadmap, please follow our [engineering updates](https://github.com/cosmos/ibc-go/wiki/Engineering-updates). | ||
|
|
||
| ## Releases | ||
|
|
||
| The release lines currently supported are v2, v3, v4, v5 and v6. | ||
|
|
||
| Please refer to the [Stable Release Policy section of RELEASES.md](https://github.com/cosmos/ibc-go/blob/main/RELEASES.md#stable-release-policy) for more details. | ||
|
|
||
| Please refer to our [versioning guide](https://github.com/cosmos/ibc-go/blob/main/RELEASES.md) for more information on how to understand our release versioning. | ||
|
|
||
| ## Ecosystem | ||
|
|
||
| Discover the applications, middleware and light clients developed by other awesome teams in the ecosystem: | ||
|
|
||
| In the table below | ||
| `app` refers to IBC application modules for custom use cases and | ||
| `middleware` refers to modules that wrap an IBC application enabling custom logic to be executed. | ||
|
|
||
|
|
||
| |Description|Repository|Type| | ||
| |----------|----------|----| | ||
| |An application that enables on chain querying of another IBC enabled chain utilizing `baseapp.Query`. Both chains must have implemented the query application and ICA (for queries requiring consensus).|[async-icq](https://github.com/strangelove-ventures/async-icq)|`app`| | ||
| |An application that enables on chain querying of another IBC enabled chains state without the need for the chain being queried to implement the application.|[interchain-queries](https://github.com/ingenuity-build/interchain-queries)|`app`| | ||
| |An application that enables on chain querying of another IBC enabled chains state without the need for the chain being queried to implement the application. Similar to the interchain-queries application in the row above but without callbacks.|[query](https://github.com/defund-labs/defund/tree/main/x/query)|`app`| | ||
| |An application that enables cross chain NFT transfer.|[NFT Transfer (ICS 721)](https://github.com/bianjieai/nft-transfer)|`app`| | ||
| |Middleware enabling a packet to be sent to a destination chain via an intermediate chain, e.g. going from Juno to Osmosis via the Hub.|[packet-forward-middleware](https://github.com/strangelove-ventures/packet-forward-middleware)|`middleware`| | ||
| |Middleware that limits the in or out flow of an asset in a certain time period to minimise the risks of cross chain token transfers. This is implemented as a middleware wrapping ICS20 with the rate limiting logic implemented by cosmwasm contracts|[ibc-rate-limit](https://github.com/osmosis-labs/osmosis/tree/main/x/ibc-rate-limit)|`middleware`| | ||
|
|
||
| ## Support | ||
|
|
||
| We have active, helpful communities on Discord and Telegram. | ||
|
|
||
| For questions and support please use the `developers` channel in the [Cosmos Network Discord server](https://discord.com/channels/669268347736686612/1019978171367559208) or join the [IBC Gang Discord server](https://discord.gg/RdpdkaXKpZ). The issue list of this repo is exclusively for bug reports and feature requests. | ||
|
|
||
| To receive announcements of new releases or other technical updates, please join the [Telegram group that we administer](https://t.me/ibc_is_expansive). | ||
|
|
||
| ## Contributing | ||
|
|
||
| If you're interested in contributing to ibc-go, please take a look at the contributing guidelines. We welcome and appreciate community contributions! | ||
|
|
||
| This project adheres to ibc-go's [code of conduct](./CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. | ||
|
|
||
| To help contributors understand which issues are good to pick up, we have the following two categories: | ||
| - Issues with the label [`good first issue`](https://github.com/cosmos/ibc-go/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) should be pretty well defined and are best suited for developers new to ibc-go. | ||
| - Issues with the label [`help wanted`](https://github.com/cosmos/ibc-go/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) are a bit more involved and they usually require some familiarity already with the codebase. | ||
|
|
||
| If you are interested in working on an issue, please comment on it; then we will be able to assign it to you. We will be happy to answer any questions you may have and help you out while you work on the issue. | ||
|
|
||
| If you have any general questions or feedback, please reach out to us in the [IBC Gang Discord server](https://discord.com/channels/955868717269516318/955883113484013578). | ||
|
|
||
| ## Request for maintainership | ||
|
|
||
| We have a document that describes the process for [submitting a feature for maintainership](./MAINTAINERSHIP.md) in the ibc-go codebase. | ||
|
|
||
| ## Security | ||
|
|
||
| To report a security vulnerability, see our [bug bounty program](https://hackerone.com/cosmos). | ||
|
|
||
| ## Audits | ||
|
|
||
| The following audits have been performed on the `ibc-go` source code: | ||
|
|
||
| - ICS27 Interchain Accounts by Trail of Bits | ||
|
|
||
| ## Quick Navigation | ||
|
|
||
| 1. **[Core IBC Implementation](https://github.com/cosmos/ibc-go/tree/main/modules/core)** | ||
|
|
||
| 1.1 [ICS 02 Client](https://github.com/cosmos/ibc-go/tree/main/modules/core/02-client) | ||
|
|
||
| 1.2 [ICS 03 Connection](https://github.com/cosmos/ibc-go/tree/main/modules/core/03-connection) | ||
|
|
||
| 1.3 [ICS 04 Channel](https://github.com/cosmos/ibc-go/tree/main/modules/core/04-channel) | ||
|
|
||
| 1.4 [ICS 05 Port](https://github.com/cosmos/ibc-go/tree/main/modules/core/05-port) | ||
|
|
||
| 1.5 [ICS 23 Commitment](https://github.com/cosmos/ibc-go/tree/main/modules/core/23-commitment/types) | ||
|
|
||
| 1.6 [ICS 24 Host](https://github.com/cosmos/ibc-go/tree/main/modules/core/24-host) | ||
|
|
||
| 2. **Applications** | ||
|
|
||
| 2.1 [ICS 20 Fungible Token Transfers](https://github.com/cosmos/ibc-go/tree/main/modules/apps/transfer) | ||
|
|
||
| 2.2 [ICS 27 Interchain Accounts](https://github.com/cosmos/ibc-go/tree/main/modules/apps/27-interchain-accounts) | ||
|
|
||
| 3. **Middleware** | ||
|
|
||
| 3.1 [ICS 29 Fee Middleware](https://github.com/cosmos/ibc-go/tree/main/modules/apps/29-fee) | ||
|
|
||
| 4. **Light Clients** | ||
|
|
||
| 4.1 [ICS 07 Tendermint](https://github.com/cosmos/ibc-go/tree/main/modules/light-clients/07-tendermint) | ||
|
|
||
| 4.2 [ICS 06 Solo Machine](https://github.com/cosmos/ibc-go/tree/main/modules/light-clients/06-solomachine) | ||
|
|
||
| 5. **[E2E Integration Tests](https://github.com/cosmos/ibc-go/tree/main/e2e)** | ||
|
|
||
| ## Documentation and Resources | ||
|
|
||
| - [IBC Website](https://ibcprotocol.dev/) | ||
| - [IBC Protocol Specification](https://github.com/cosmos/ibc) | ||
| - [Documentation](https://ibc.cosmos.network/main/ibc/overview.html) | ||
| - [Interchain Developer Academy](https://tutorials.cosmos.network/academy/3-ibc/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| --- | ||
| order: 1 | ||
| --- | ||
|
|
||
| # Roadmap ibc-go | ||
|
|
||
| _Lastest update: December 21st, 2022_ | ||
|
|
||
| This document endeavours to inform the wider IBC community about plans and priorities for work on ibc-go by the team at Interchain GmbH. It is intended to broadly inform all users of ibc-go, including developers and operators of IBC, relayer, chain and wallet applications. | ||
|
|
||
| This roadmap should be read as a high-level guide, rather than a commitment to schedules and deliverables. The degree of specificity is inversely proportional to the timeline. We will update this document periodically to reflect the status and plans. For the latest expected release timelines, please check [here](https://github.com/cosmos/ibc-go/wiki/Release-timeline). | ||
|
|
||
| ## v7.0.0 | ||
|
|
||
| ### 02-client refactor | ||
|
|
||
| This refactor will make the development of light clients easier. The ibc-go implementation will finally align with the spec and light clients will be required to set their own client and consensus states. This will allow more flexibility for light clients to manage their own internal storage and do batch updates. See ADR 006 for more information. | ||
|
|
||
| Follow the progress with the [beta](https://github.com/cosmos/ibc-go/milestone/25) and [RC](https://github.com/cosmos/ibc-go/milestone/27) milestones or in the [project board](https://github.com/orgs/cosmos/projects/7/views/14). | ||
|
|
||
| ### Upgrade Cosmos SDK v0.47 | ||
|
|
||
| Follow the progress with the [milestone](https://github.com/cosmos/ibc-go/milestone/36). | ||
|
|
||
| ### Add `authz` support to 20-transfer | ||
|
|
||
| Authz goes cross chain: users can grant permission for their tokens to be transferred to another chain on their behalf. See [this issue](https://github.com/cosmos/ibc-go/issues/2431) for more details. | ||
|
|
||
| ## v7.1.0 | ||
|
|
||
| Because it is so important to have an ibc-go release compatible with the latest Cosmos SDK release, a couple of features will take a little longer and be released in [v7.1.0](https://github.com/cosmos/ibc-go/milestone/37). | ||
|
|
||
| ### Localhost connection | ||
|
|
||
| This feature will add support for applications on a chain to communicate with applications on the same chain using the existing standard interface to communicate with applications on remote chains. This is a powerful UX improvement, particularly for those users interested in interacting with multiple smart contracts on a single chain through one interface. | ||
|
|
||
| For more details, see the design proposal and discussion [here](https://github.com/cosmos/ibc-go/discussions/2191). | ||
|
|
||
| A special shout out to Strangelove for their substantial contribution on this feature. | ||
|
|
||
| ### Support for Wasm light clients | ||
|
|
||
| We will add support for Wasm light clients. The first Wasm client developed with ibc-go/v7 02-client refactor and stored as Wasm bytecode will be the GRANDPA light client used for Cosmos <> Substrate IBC connections. This feature will be used also for a NEAR light client in the future. | ||
|
|
||
| This feature was developed by Composable and Strangelove but will be upstreamed into ibc-go. | ||
|
|
||
| ## v8.0.0 | ||
|
|
||
| ### Channel upgradability | ||
|
|
||
| Channel upgradability will allow chains to renegotiate an existing channel to take advantage of new features without having to create a new channel, thus preserving all existing packet state processed on the channel. | ||
|
|
||
| Follow the progress with the [alpha milestone](https://github.com/cosmos/ibc-go/milestone/29) or the [project board](https://github.com/orgs/cosmos/projects/7/views/17). | ||
|
|
||
| ### Path unwinding | ||
|
|
||
| This feature will allow tokens with non-native denoms to be sent back automatically to their native chains before being sent to a final destination chain. This will allow tokens to reach a final destination with the least amount possible of hops from their native chain. | ||
|
|
||
| For more details, see this [discussion](https://github.com/cosmos/ibc/discussions/824). | ||
|
|
||
| --- | ||
|
|
||
| This roadmap is also available as a [project board](https://github.com/orgs/cosmos/projects/7/views/25). | ||
|
|
||
| For the latest expected release timelines, please check [here](https://github.com/cosmos/ibc-go/wiki/Release-timeline). | ||
|
|
||
| For the latest information on the progress of the work or the decisions made that might influence the roadmap, please follow our [engineering updates](https://github.com/cosmos/ibc-go/wiki/Engineering-updates). | ||
|
|
||
| --- | ||
|
|
||
| **Note**: release version numbers may be subject to change. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.