#blockchain #consensus #cosmos #ibc #tendermint


Implementation of the Inter-Blockchain Communication Protocol (IBC). This crate comprises the main data structures and on-chain logic

15 releases (7 breaking)

0.27.0 Jan 23, 2024
0.26.4 Dec 15, 2023
0.26.3 Nov 29, 2023
0.25.0 Jul 19, 2023
0.20.0 Oct 28, 2022

#987 in Magic Beans

Download history 748/week @ 2023-10-27 1493/week @ 2023-11-03 1276/week @ 2023-11-10 1302/week @ 2023-11-17 1204/week @ 2023-11-24 1209/week @ 2023-12-01 1392/week @ 2023-12-08 1433/week @ 2023-12-15 832/week @ 2023-12-22 457/week @ 2023-12-29 1059/week @ 2024-01-05 1064/week @ 2024-01-12 1464/week @ 2024-01-19 1285/week @ 2024-01-26 1342/week @ 2024-02-02 1126/week @ 2024-02-09

5,321 downloads per month
Used in 19 crates (8 directly)


14K SLoC

IBC module

Crate Docs Build Status End to End testing Apache 2.0 Licensed Rust Stable Rust 1.51+

See the ibc-rs repo root for more detailed information on how this crate can be used.

Implementation of the Inter-Blockchain Communication Protocol (IBC) module.


See documentation on docs.rs.

Divergence from the Interchain Standards (ICS)

This crate diverges from the ICS specification in a number of ways. See below for more details.

Module system: no support for untrusted modules

ICS 24 (Host Requirements) gives the following requirement about the module system that the host state machine must support:

The host state machine must support a module system, whereby self-contained, potentially mutually distrusted packages of code can safely execute on the same ledger [...].

This crate currently does not support mutually distrusted packages. That is, modules on the host state machine are assumed to be fully trusted. In practice, this means that every module has either been written by the host state machine developers, or fully vetted by them.

Port system: No object capability system

ICS 5 (Port Allocation) requires the host system to support either object-capability reference or source authentication for modules.

In the former object-capability case, the IBC handler must have the ability to generate object-capabilities, unique, opaque references which can be passed to a module and will not be duplicable by other modules. [...] In the latter source authentication case, the IBC handler must have the ability to securely read the source identifier of the calling module, a unique string for each module in the host state machine, which cannot be altered by the module or faked by another module.

This crate currently requires neither of the host system. Since modules are assumed to be trusted, there is no need for this object capability system that protects resources for potentially malicious modules.

For more background on this, see this issue.

Port system: transferring and releasing a port

ICS 5 (Port Allocation) requires the IBC handler to permit transferring ownership of a port and releasing a port.

We currently support neither.


Copyright © 2021 Informal Systems Inc. and ibc-rs authors.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use the files in this repository except in compliance with the License. You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.


~410K SLoC