​
变更记录

  • 2022-02-04：新增内容
  • 2022-01-19：初始化
  • 2023-06-28：标记为已拒绝

​
状态

已拒绝，未实现 原因： IBC 团队决定将该功能直接集成到其代码库中并自行维护，因为有多个用户需要该功能。

​
摘要

这是核心跨链账户模块。它允许 Cosmos Hub 作为主机链，承载由外部 IBC 连接的“控制器”区块链控制的跨链账户。候选链包括 Umee、Quicksilver、Sommelier。它也是认证模块的必要组成部分，该模块还允许 Cosmos Hub 同时作为控制器链。该内容将在单独的 ADR 中记录。

​
设计依据

这使 Hub 能够参与高级跨链 DeFi 操作，例如流动性质押以及各种协议控制价值应用。

​
期望结果

Hub 可以在跨链账户配置中以无需信任的方式作为主机链使用。

​
影响后果

此前已进行初步工作，以了解这是否会增加 Cosmos Hub 的任何安全特性。一种观点认为，这种能力类似于虚拟机区块链（如 EVM 链）上可实现的合约间交互。这类交互曾引入一种新的攻击向量，即重入漏洞，而这正是“以太坊 The DAO 黑客事件”的成因。我们认为，跨链账户不存在这类攻击风险，因为这类攻击要求交互是原子的，而跨链账户是异步的。

​
向后兼容性

这是首个此类实现。

​
向前兼容性

未来发布的跨链账户版本预计将保持向后兼容。

​
技术规范

ICS-27 规范

​
开发

  • 集成要求
    • 开发工作已在 IBC-go 中开展，进展在该项目看板上跟踪。
  • 测试（模拟测试、核心团队测试、合作伙伴测试）
    • 模拟测试和核心团队已对该模块进行了测试
  • 审计（内部开发评审、第三方评审、漏洞赏金）
    • 已完成一次内部审计、一次 Informal Systems 审计和一次 Trail of Bits 审计，并已修复所有发现的问题。
  • 网络（测试网、生产网、主网）
    • 测试网

​
治理 [可选]

  • 需要信号提案
  • 核心社区治理
    • 不适用
  • 指导委员会
    • 不适用。可能是 Aditya Srinpal、Sean King、Bez？
  • 时间线与路线图
    • 预计作为 IBC 3.0 的一部分于 2022 年 2 月发布（当前处于 beta 版本发布）

​
项目集成 [可选]

  • Gaia 集成
  • 集成合作方
    • IBC 团队

​
下游用户影响报告

（待创建）

​
上游合作伙伴影响报告

（待创建）

​
模块间依赖报告

（待创建）

​
支持

文档

​
补充研究与参考资料

​
Changelog

  • 2022-02-04: added content
  • 2022-01-19: init
  • 2023-06-28: mark as rejected

​
Status

REJECTED Not Implemented Reason: The IBC team decided to integrate this functionality directly into their codebase and maintain it, because multiple users require it.

​
Abstract

This is the Core Interchain Accounts Module. It allows the Cosmos Hub to act as a host chain with interchain accounts that are controlled by external IBC connected “Controller” blockchains. Candidate chains include Umee, Quicksilver, Sommelier. It is also a necessary component for a Authentication Module that allows the Cosmos Hub to act as a Controller chain as well. This will be recorded in a separate ADR.

​
Rationale

This allows the Hub to participate in advanced cross-chain defi operations, like Liquid Staking and various protocol controlled value applications.

​
Desired Outcome

The hub can be used trustlessly as a host chain in the configuration of Interchain Accounts.

​
Consequences

There has been preliminary work done to understand if this increases any security feature of the Cosmos Hub. One thought was that this capability is similar to contract to contract interactions which are possible on virtual machine blockchains like EVM chains. Those interactions introduced a new attack vector, called a re-entrancy bug, which was the culprit of “The DAO hack on Ethereum”. We believe there is no risk of these kinds of attacks with Interchain Accounts because they require the interactions to be atomic and Interchain Accounts are asynchronous.

​
Backwards Compatibility

This is the first of its kind.

​
Forward Compatibility

There are future releases of Interchain Accounts which are expected to be backwards compatible.

​
Technical Specification

ICS-27 Spec

​
Development

  • Integration requirements
    • Development has occurred in IBC-go and progress tracked on the project board there.
  • Testing (Simulations, Core Team Testing, Partner Testing)
    • Simulations and Core Team tested this module
  • Audits (Internal Dev review, Third-party review, Bug Bounty)
    • An internal audit, an audit from Informal Systems, and an audit from Trail of Bits all took place with fixes made to all findings.
  • Networks (Testnets, Productionnets, Mainnets)
    • Testnets

​
Governance [optional]

  • Needs Signaling Proposal
  • Core Community Governance
    • N/A
  • Steering Community
    • N/A. Possibly Aditya Srinpal, Sean King, Bez?
  • Timelines & Roadmap
    • Expected to be released as part of IBC 3.0 in Feb 2022 (currently in beta release)

​
Project Integrations [optional]

  • Gaia Integrations
  • Integration Partner
    • IBC Team

​
Downstream User Impact Report

(Needs to be created)

​
Upstream Partner Impact Report

(Needs to be created)

​
Inter-module Dependence Report

(Needs to be created)

​
Support

Documentation

​
Additional Research & References