#ibc #tendermint #consensus #cosmos #blockchain #data-structures

ibc-types-domain-type

Data types for the Inter-Blockchain Communication (IBC) protocol. This crate defines common data structures that can be reused by different IBC implementations or ecosystem tooling

15 releases (9 breaking)

new 0.13.0 Apr 4, 2024
0.12.0 Mar 1, 2024
0.11.1 Jan 31, 2024
0.11.0 Dec 15, 2023
0.10.0 Nov 27, 2023

#38 in #tendermint

Download history 672/week @ 2023-12-14 288/week @ 2023-12-21 353/week @ 2023-12-28 478/week @ 2024-01-04 437/week @ 2024-01-11 744/week @ 2024-01-18 857/week @ 2024-01-25 1198/week @ 2024-02-01 1114/week @ 2024-02-08 706/week @ 2024-02-15 803/week @ 2024-02-22 1507/week @ 2024-02-29 1003/week @ 2024-03-07 867/week @ 2024-03-14 1017/week @ 2024-03-21 755/week @ 2024-03-28

3,837 downloads per month
Used in 7 crates (6 directly)

Apache-2.0

4KB

ibc-types

This crate defines common data structures for Inter-Blockchain Communication (IBC) messages that can be reused by different IBC implementations or IBC ecosystem tooling.

Unlike ibc-rs, which provides a specific and opinionated implementation of IBC, ibc-types just defines Rust types that allow working with IBC messages, allowing an IBC implementation or IBC ecosystem tooling to be built on top using a common language.

In addition to defining Rust types for IBC messages, ibc-types also defines Rust types for IBC events, and provides code for parsing IBC events to and from ABCI messages. IBC events are de facto a critical part of IBC, in that they're needed to interoperate with relayers, but are not really specified anywhere. Providing event parsing code in ibc-types allows IBC implementations and relayer implementations to share common code for producing and consuming events.

The ibc-types crate is a top-level wrapper crate re-exporting the contents of subcrates scoped by IBC module. This structure means that external users of the library can use one catch-all crate, but allows dependency relationships between different IBC modules. For example, the ibc-types crate re-exports the client types defined in the ibc-types-core-client crate, as well as the types for the Tendermint light client defined in the ibc-types-lightclients-tendermint crate. But because these are separate crates, the Tendermint light client types can depend on the core IBC client types, preventing cyclic dependency issues.

Contributing

IBC is specified in English in the cosmos/ibc repo. Any protocol changes or clarifications should be contributed there.

This repo contains Rust datatypes modeling IBC messages.

Versioning

We follow Semantic Versioning, though APIs are still under active development.

Resources

License

Copyright © 2023 ibc-types authors.

This crate was originally forked from ibc-rs:

Copyright © 2022 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

https://www.apache.org/licenses/LICENSE-2.0

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.


lib.rs:

Provides a marker type capturing the relationship between a domain type and a protobuf type.

Dependencies

~390KB