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
Packets can disable usage of a timeout height by setting the revision number and height both to 0.
The relayer was never architected to support revision numbers. The revision number feature was added fairly last minute to IBC. A lot of places assume the existence of a timeout height. State based relaying needs to obtain the timeout in the revision form when parsing past txs, instead of only parsing the revision height and assuming the revision number based on chain-id
Alternatively, a quicker fix is to add a check if the timeout height is 0 and set the revision number to 0 as well
I'm not sure if relaying based on streaming accounts for this.
The text was updated successfully, but these errors were encountered:
Packets can disable usage of a timeout height by setting the revision number and height both to 0.
The relayer was never architected to support revision numbers. The revision number feature was added fairly last minute to IBC. A lot of places assume the existence of a timeout height. State based relaying needs to obtain the timeout in the revision form when parsing past txs, instead of only parsing the revision height and assuming the revision number based on chain-id
Alternatively, a quicker fix is to add a check if the timeout height is 0 and set the revision number to 0 as well
I'm not sure if relaying based on streaming accounts for this.
The text was updated successfully, but these errors were encountered: