架构决策记录（ADR）
这里用于记录 ibc-go 项目中的所有高层架构决策。 你可以在这篇博客文章中了解更多关于 ADR 概念的内容。 一份 ADR 应当提供：- 相关目标及当前状态的背景
- 为实现目标而提出的变更
- 优缺点总结
- 参考资料
- 变更日志
目录
| ADR 编号 | 描述 | 状态 |
|---|---|---|
| 001 | ICS-20 代币面额格式 | 已接受，已实施 |
| 002 | Go 模块版本控制 | 已接受 |
| 003 | ICS27 确认格式 | 已接受 |
| 004 | ICS29 模块在托管余额失衡时锁定 | 已接受 |
| 005 | UpdateClient 事件 - ClientState 共识高度 | 已接受 |
| 006 | ICS02 客户端重构 | 已接受 |
| 007 | ICS06 Solo machine 签名字节 | 已接受 |
| 008 | 对 IBC 参与方的回调 | 已接受 |
| 009 | ICS27 消息服务器新增 | 已接受 |
| 010 | 将 IBC 轻客户端作为 SDK 模块 | 已接受 |
| 011 | 用于记录托管中代币总量的 ICS20 状态条目 | 已接受 |
| 015 | IBC 数据包路由 | 已接受 |
| 025 | IBC 被动通道 | 已弃用 |
| 026 | IBC 客户端恢复机制 | 已接受 |
| 027 | 基于 Wasm 的轻客户端 | 已接受 |
Architecture Decision Records (ADR)
This is a location to record all high-level architecture decisions in the ibc-go project. You can read more about the ADR concept in this blog post. An ADR should provide:- Context on the relevant goals and the current state
- Proposed changes to achieve the goals
- Summary of pros and cons
- References
- Changelog
Table of Contents
| ADR # | Description | Status |
|---|---|---|
| 001 | ICS-20 coin denomination format | Accepted, Implemented |
| 002 | Go module versioning | Accepted |
| 003 | ICS27 acknowledgement format | Accepted |
| 004 | ICS29 module locking upon escrow out of balance | Accepted |
| 005 | UpdateClient events - ClientState consensus heights | Accepted |
| 006 | ICS02 client refactor | Accepted |
| 007 | ICS06 Solo machine sign bytes | Accepted |
| 008 | Callback to IBC Actors | Accepted |
| 009 | ICS27 message server addition | Accepted |
| 010 | IBC light clients as SDK modules | Accepted |
| 011 | ICS20 state entry for total amount of tokens in escrow | Accepted |
| 015 | IBC Packet Routing | Accepted |
| 025 | IBC passive channels | Deprecated |
| 026 | IBC client recovery mechanisms | Accepted |
| 027 | Wasm based light clients | Accepted |