Christopher Goes
Christopher Goes
> Loopback will be handled when multi-hop is supported? Ah, let's do that now (no reason not to), excellent point.
What needs to be in the store key? @mossid asked. @cwgoes - I think we can keep it as is, since handshake will set up hops.
Alternatively, channel identifiers could be unique per-port - that seems to make more sense... Then the channel key = `port id || channel id`
Note also points raised in https://github.com/cosmos/ics/issues/65#issuecomment-479362081 (closed in favor of this issue).
Connections can never be closed, so if a connection is not in OPEN state the connection handshake has not completed and the channel handshake should not have been completed either....
The application wants to close the connection, or the application wants to close the channel? If the connection has never been opened, the packets can never be received, either way,...
Optimistic sends come with the risk of unrecoverable packets, but this is true regardless of whether a channel close is attempted.
Yes, that scenario is possible. Applications may wish to deny or block channel closure for this reason. Perhaps we should consider implementing a "graceful" closure process which is multi-step and...
@ancazamfir Would you like any changes to be made, or any points to be clarified in the spec?
As I understand your proposal, the `Socket` object is not first-class within IBC - none of the logic will change - it's just the combination of a channel identifier and...