IBC Connection functionality

[adizere]

Context

IBC Connections in conjunction with Clients provide authorisation for messages transmitted between different chains in IBC.

Further reading

IBC Connection English spec: ics-003-connection-semantics
IBC Connection handlers TLA+ model: ICS03ConnectionHandlers.tla part of IBC-core TLA+ spec

Dependencies

For complete implementation & acceptance:

• ICS02: ics-002-client-semantics
• ICS26: ics-026-routing-module
• ICS18: ics-018-relayer-algorithms
• model-based testing (MBT) harness

Acceptance criteria

Component	Functionality	Criteria	Status
Module	Conn Open Handshake Handlers	Impl & unit tests	[X]
Module	Conn Open Handshake Handlers	MBT tests	[ ]
Module	Conn Open Handshake Handlers	TLA+ spec	[X]
CLI	Conn Open Handshake Steps	Impl & end-to-end tests	[X]
CLI	Conn Open Handshake Steps	Mock tests	[X]
CLI	Conn Open Handshake Command	Impl	[X]
CLI	Conn Open Handshake Command	End-to-end tests	[ ]
CLI	Conn Open Handshake Command	Mock tests	[ ]
CLI	Connection Delay Specification	Impl	[ ]

Related issues

The following ongoing issues provide a more fine-grained perspective on the different parts of IBC client functionality:

• Packet delays:
  • Implementation: Implement packet delay in packet relaying #640
  • TLA+ spec: TLA+ specification of packet delay #446
• Agoric's use case: Agoric's dynamic IBC use case #628
• CLI review: Introduce ADR to unify Hermes CLI options for v1 #594
• Modular logic for ICS3 Connection handshake protocol Modular logic for ICS3 Connection handshake protocol #92