-
Notifications
You must be signed in to change notification settings - Fork 32
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
feat/add_wasm_light_client #153
feat/add_wasm_light_client #153
Conversation
Important Auto Review SkippedDraft detected. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Looking good. Remember that you can always reference the IBC simapp, and that you should always give a description and link to the issue, if there is one. |
0e426f9
to
b37b5bf
Compare
@tungle-notional - when I did the merge, I also corrected version numbers. We want eve to use ibc v8.1.0 and the latest released version of the wasm client. |
@faddat Yeah, sure. But do you know this bug? It happens after I rebase from the main branch and change the version to make it compatible |
the bug you posted is from the version of wasmvm being used. If we use the same wasmvm as ibc that will be fine. Also, it might be needed to update wasmvm in ibc-go |
Closes: #122
This pull request implements the WASM light client