Attempt to fix ibc.fun for dydx #61
Closed
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
This was indirectly resolved by one of Grikos PR so I'm going to close |
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.
Added dydx to chain registry manually since the latest version on npm doesn't have it yet. Ideally we should get this information from the chains endpoint. If something is missing, please let me know so Skip API can add.
There was an issue where ibc.fun looked like it was calling some public nodes and was failing to get a response, and I was not able to send a transaction. I suspect this is attempting to get information needed to prepare the messages, we should figure out a better solution around this that is easier to customize.
Created this PR for reference to what I attempted.