-
Notifications
You must be signed in to change notification settings - Fork 586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe found a query bug in interchain-accounts #665
Comments
I found this bug while trying to see if I could see he status of a transaction that was submitted to the host chain from the controller chain. Would love to get something like a TX hash that I can use to see if my TX failed on the host chain. Or query the host chain with my account to see a list of transactions? |
thanks @okwme! I opened #666 which fixes the issue (but you'll need to restart your chain with the updated binary) As far as seeing the status of a tx. The ICA auth module will receive the acknowledgement result in OnAcknowledgement, it could log the result there or we can ensure the packet sequence used to send the transaction is returned to the user. Then you could query for the acknowledgement on the host chain. We could add a command to ica which parses the acknowledgement result |
Add lack of M1 support to README
) * fixing merge conflicts * fix breaking changes related to substore, prefixing, and keys * fix all the failing tests * test that is no longer needed * fix missing merge conflict * fixing golangci-lint errors * more lint errors * goimports fixes * fixing golangci-lint failures * changing from DataStore to TxnDatasource, cutting some LOC, prefix entires as iterator, etc Co-authored-by: Ganesha Upadhyaya <gupadhyaya@Ganeshas-MacBook-Pro-2.local>
Summary of Bug
When running a CLI query on the
interchain-accounts
module (host
andcontroller
subcommand) I see an error.Version
https://github.com/cosmos/gaia/tree/ica-acct-auth
Steps to Reproduce
I maybe also jsut mis-configured the
For Admin Use
The text was updated successfully, but these errors were encountered: