v7.3.0 版本的说明。
本文档根据四类可能的用户群体分为以下四个部分：
注意： ibc-go 遵循 golang 语义化版本控制，因此在主版本发布时必须更新所有 import。
链
- 此版本没有相关变更。
IBC 应用
新增了一组接口，IBC 应用可以选择性实现。希望将其应用与callbacks 中间件集成的开发者，应实现这些接口，以便 callbacks 中间件能够获取源链和目标链上所需的回调地址，并在数据包生命周期事件中执行相应操作。这些接口包括PacketDataUnmarshaler、PacketDataProvider 和 PacketData。
提供了可供参考的示例实现。对于 transfer：
对于 27-interchain-accounts：
中继器
- 此版本没有相关变更。
IBC 轻客户端
06-solomachine
现在，solo machine 需要在满足以下条件的路径上对数据进行签名：1）不包含连接前缀（例如ibc）；2）不对任何字符进行转义。更多细节请参见 PR #4429。我们建议不要使用低于 v7.3.0 版本的 solo machine 轻客户端。
This guide provides instructions for migrating to version
v7.3.0 of ibc-go.
There are four sections based on the four potential user groups of this document:
Note: ibc-go supports golang semantic versioning and therefore all imports must be updated on major version releases.
Chains
- No relevant changes were made in this release.
IBC Apps
A set of interfaces have been added that IBC applications may optionally implement. Developers interested in integrating their applications with the callbacks middleware should implement these interfaces so that the callbacks middleware can retrieve the desired callback addresses on the source and destination chains and execute actions on packet lifecycle events. The interfaces arePacketDataUnmarshaler, PacketDataProvider and PacketData.
Sample implementations are available for reference. For transfer:
For 27-interchain-accounts:
Relayers
- No relevant changes were made in this release.
IBC Light Clients
06-solomachine
Solo machines are now expected to sign data on a path that 1) does not include a connection prefix (e.gibc) and 2) does not escape any characters. See PR #4429 for more details. We recommend NOT using the solo machine light client of versions lower than v7.3.0.