You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the handshake is completed, the version is done being negotiated and is set in the channel state. The current design of middleware recommends to wrap the underlying applications version into your own metadata. This becomes problematic when an application wants to reference its own version during the packet lifecycle.
Opening for discussion as this is problematic to any existing applications which currently make use of the version (none of our applications do for the packet life cycle)
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged/assigned
The text was updated successfully, but these errors were encountered:
Last I discussed with @AdityaSripal, there were two options he presented:
Add a GetChannelVersion to the ICS4Wrapper interface
Expect IBC applications to do extra storing to account for this issue
I think we should go with the first option as it isn't much overhead. We are consistently running into issues with middleware wrapping the underlying applications, so we should investigate a longer term fix
Summary
After the handshake is completed, the version is done being negotiated and is set in the channel state. The current design of middleware recommends to wrap the underlying applications version into your own metadata. This becomes problematic when an application wants to reference its own version during the packet lifecycle.
Opening for discussion as this is problematic to any existing applications which currently make use of the version (none of our applications do for the packet life cycle)
For Admin Use
The text was updated successfully, but these errors were encountered: