We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In ibc-go, version negotiation is done synchronously, however, due to the asynchronous nature of Agoric chain, we'd want to do it asynchronously.
This issue has been addressed in IBC specification, but it's not yet implemented in ibc-go.
Once async version negotiation is implemented in ibc-go, we should:
In https://github.com/Agoric/agoric-sdk/blob/master/golang/cosmos/x/vibc/types/ibc_module.go, const AsyncVersions is permanently set to false, once async version negotiation is implemented in ibc-go, we should revisit this const and all the places that are using this const to determine if our code matches up with ibc-go's implementation of async version negotiation.
const AsyncVersions
false
const
N/A
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the Problem Being Solved?
In ibc-go, version negotiation is done synchronously, however, due to the asynchronous nature of Agoric chain, we'd want to do it asynchronously.
This issue has been addressed in IBC specification, but it's not yet implemented in ibc-go.
Once async version negotiation is implemented in ibc-go, we should:
Description of the Design
In https://github.com/Agoric/agoric-sdk/blob/master/golang/cosmos/x/vibc/types/ibc_module.go,
const AsyncVersions
is permanently set tofalse
, once async version negotiation is implemented in ibc-go, we should revisit thisconst
and all the places that are using thisconst
to determine if our code matches up with ibc-go's implementation of async version negotiation.Security Considerations
N/A
Scaling Considerations
N/A
Test Plan
N/A
Upgrade Considerations
N/A
The text was updated successfully, but these errors were encountered: