Add Packet-Forward-Middleware #187
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jim380
changed the title
hacheigriega
approved these changes
Jan 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR attempts to add support for packet-forward-middleware in the Seda chain to enable multi-hop transactions, reducing the need for each ibc chain to maintain direct connections and infrastructure for every other chain. It simplifies transaction tracking by using asynchronous acknowledgements, allowing users to monitor only the chain where the initial transfer was sent for the entire process response.
Testing
SedaExponentto 6 inapp/params/config.go. This is because in interchaintest v8.0.0 the default only has hardcoded values now which were tailored toe6.