Acknowledgement is the recommended acknowledgement format to be used by
app-specific protocols.
NOTE: The field numbers 21 and 22 were explicitly chosen to avoid accidental
conflicts with other protobuf message formats used for acknowledgements.
The first byte of any message with this format will be the non-ASCII values
0xaa (result) or 0xb2 (error). Implemented as defined by ICS:
https://github.com/cosmos/ibc/tree/master/spec/core/ics-004-channel-and-packet-semantics#acknowledgement-envelope
Channel defines pipeline for exactly-once packet delivery between specific
modules on separate blockchains, which has at least one end capable of
sending packets and one end capable of receiving packets.
ErrorReceipt defines a type which encapsulates the upgrade sequence and error associated with the
upgrade handshake failure. When a channel upgrade handshake is aborted both chains are expected to increment to the
next sequence.
MsgChannelOpenAck defines a msg sent by a Relayer to Chain A to acknowledge
the change of channel state to TRYOPEN on Chain B.
WARNING: a channel upgrade MUST NOT initialize an upgrade for this channel
in the same block as executing this message otherwise the counterparty will
be incapable of opening.
MsgChannelOpenInit defines a msg sent by a Relayer to try to open a channel
on Chain B. The version field within the Channel field has been deprecated. Its
value will be ignored by core IBC.
MsgChannelUpgradeInit defines the request type for the ChannelUpgradeInit rpc
WARNING: Initializing a channel upgrade in the same block as opening the channel
may result in the counterparty being incapable of opening.
PacketId is an identifer for a unique Packet
Source chains refer to packets by source port/channel
Destination chains refer to packets by destination port/channel
PacketState defines the generic type necessary to retrieve and store
packet commitments, acknowledgements, and receipts.
Caller is responsible for knowing the context necessary to interpret this
state as a commitment, acknowledgement, or a receipt.
QueryChannelResponse is the response type for the Query/Channel RPC method.
Besides the Channel end, it includes a proof and the height from which the
proof was retrieved.
QueryPacketAcknowledgementResponse defines the client query response for a
packet which also includes a proof and the height from which the
proof was retrieved
QueryPacketCommitmentResponse defines the client query response for a packet
which also includes a proof and the height from which the proof was
retrieved
QueryPacketReceiptResponse defines the client query response for a packet
receipt which also includes a proof, and the height from which the proof was
retrieved
Timeout defines an execution deadline structure for 04-channel handlers.
This includes packet lifecycle handlers as well as the upgrade handshake handlers.
A valid Timeout contains either one or both of a timestamp and block height (sequence).
Upgrade is a verifiable type which contains the relevant information
for an attempted upgrade. It provides the proposed changes to the channel
end, the timeout for this upgrade attempt and the next packet sequence
which allows the counterparty to efficiently know the highest sequence it has received.
The next sequence send is used for pruning and upgrading from unordered to ordered channels.