Christopher Goes

It should be recreated anyways, it was never very clear.

- Add DataType from signature

Types of multi-hop routing:  1. "Application-layer multihop" `A` talks to `H`, `H` talks to `B` No routing at IBC protocol layer, just two connections / channels. We can do...

What we need to think about immediately is just what data structure alterations will be required for (3).

- Channel opening handshake will specify a list of connection hops instead of a single connection - Packets will specify a list of connection hops instead of single origination &...

> If the system is end to end, do I show validaty proofs in consensus for all the intermediary hops to the end hops or just the validity proofs? In...

> How does A know the connections/ hops to reach B? `A` doesn't know anything in particular (although it may have existing connections). The user or module creating the channel...

> Aren't packets over a channel following the same route as the channel itself? why do they need again the source route? They need the connection identifiers to distinguish between...

> I understand this but I have a feeling the intermediate connection info is redundant and only source and destination connections are required; since the source route has been previously...

Data structure changes for future compatibility: - Channels are created with list of connection "hops" instead of source / dest connection identifiers. - Channel opening handshake datagrams altered to contain...