Skip to content
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

[lc/starknet] verify membership methods don't have access to CosmWasm context #229

Open
rnbguy opened this issue Jan 23, 2025 · 1 comment · May be fixed by #242
Open

[lc/starknet] verify membership methods don't have access to CosmWasm context #229

rnbguy opened this issue Jan 23, 2025 · 1 comment · May be fixed by #242
Assignees
Milestone

Comments

@rnbguy
Copy link
Member

rnbguy commented Jan 23, 2025

To avoid wasm blob size bloating, we are using cosmwasm's secp256k1 verifier as part of their native environment import. We successfully added this for client update in #205.

Now, similar to #228, we need to validate the commitment proofs too.

But to verify this commitment proof inside the cosmwasm light client, we implement them on ClientStateCommon -- but this trait doesn't pass the ClientValidationContext. So, we can't really use the cosmwasm's native secp256k1 verifier.

Currently, we are considering forking https://github.com/informalsystems/cosmwasm-ibc and adding the signature verifier calls directly at Context implementation.

PS. this issue is redundant if #40 is resolved.

@rnbguy
Copy link
Member Author

rnbguy commented Jan 27, 2025

resolving at informalsystems/cosmwasm-ibc#8

@rnbguy rnbguy changed the title [cw/light-client] verify membership methods don't have access to CosmWasm context [lc/starknet] verify membership methods don't have access to CosmWasm context Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants