Aditya

Well, we could just use the version of the go repo as well. For modules in ibc-go this would be ibc-go versions, but other modules may have their own versions

> together with the previous value and height at which it was updated Does it need to store both? Or only the previous height of last update. Seems like checking...

cc @alexanderbez

cc: @mpoke @schnetzlerjoe could you detail how the synchronous situation is affecting you?

Nice work, I think from a backwards compatibility standpoint. It is easier for the applications to still only create and process opaque bytes as the acknowledgement. Regardless of what version...

In order to keep things even easier for relayers to integrate this, we could keep the proto definiton of `Acknowledgement` still have `bytes` in all the relayer messages. It is...

> On write acknowledgement, app returns ack bytes and ICS-4 places it in ack struct along with forward relayer address. Note that this requires some storage in core IBC in...

Thanks for the catch! @hu55a1n1 Yes I think we should update the spec to add the check on the sending side. Disabling timeouts for a packet is certainly something we...

I think we can just transfer the issue to the spec repo

Hmm, but even if height `0` is valid it would still be sensible to error if it was passed as the timeoutHeight correct? Since `-1` is not a valid height,...