The Inter-Blockchain Communication protocol (IBC) 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, or our docs.
For an overview of upcoming changes to ibc-go take a look at the roadmap.
This roadmap is also available as a project board.
For the latest expected release timelines, please check here.
For the latest information on the progress of the work or the decisions made that might influence the roadmap, please follow our engineering updates.
The release lines currently supported are v4, v5, v6 and v7.
Please refer to the Stable Release Policy section of RELEASES.md for more details.
Please refer to our versioning guide for more information on how to understand our release versioning.
Discover more applications and middleware in the cosmos/ibc-apps repository.
We have active, helpful communities on Discord and Telegram.
For questions and support please use the developers
channel in the Cosmos Network Discord server or join the IBC Gang Discord server. 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.
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. 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
should be pretty well defined and are best suited for developers new to ibc-go. - Issues with the label
help wanted
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.
To report a security vulnerability, see our Coordinated Vulnerability Disclosure Policy.
The following audits have been performed on the ibc-go
source code:
- ICS27 Interchain Accounts by Trail of Bits
-
1.1 ICS 02 Client
1.3 ICS 04 Channel
1.4 ICS 05 Port
1.6 ICS 24 Host
-
Applications
-
Middleware
-
Light Clients
4.3 ICS 09 Localhost