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
Not so sure what is needed to be done here. In the normal case, I think we will relay all packets in order. Let's ensure they are sorted by (channel, sequence).
However, we will need to be careful (1) we filter out packets - we cannot skip on ordered channels and (2) if a packet is timed-out, we need to submit that before the packet to relay. So, most low-level primitives should work the same, but the higher-level ones may need some adjustment
The text was updated successfully, but these errors were encountered:
Would love to know more about when this feature might become available. it's a necessary feature for interchain accounts to be ale to use the ts-relayer (cc @seantking)
The priority depends on how urgently the interchain accounts will be on the cosmos hub. Or any mainnet actually.
Maybe we can chat a bit about all the schedule of the various external moving parts (outside of github). It could be the next non-bugfix feature we work on if this will be deployed soon.
Depends on #46 (blocked)
Not so sure what is needed to be done here. In the normal case, I think we will relay all packets in order. Let's ensure they are sorted by (channel, sequence).
However, we will need to be careful (1) we filter out packets - we cannot skip on ordered channels and (2) if a packet is timed-out, we need to submit that before the packet to relay. So, most low-level primitives should work the same, but the higher-level ones may need some adjustment
The text was updated successfully, but these errors were encountered: