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

QueryClientStateResponse (and maybe more RPC structs) #233

Open
dakom opened this issue Sep 3, 2024 · 0 comments
Open

QueryClientStateResponse (and maybe more RPC structs) #233

dakom opened this issue Sep 3, 2024 · 0 comments

Comments

@dakom
Copy link
Contributor

dakom commented Sep 3, 2024

If I query a QueryClientStateRequest I get back a QueryClientStateResponse - but without the proofs.

Is this expected behavior? The comments do say:

QueryClientStateResponse is the response type for the Query/ClientState RPC
method. Besides the client state, it includes a proof and the height from
which the proof was retrieved.

... but, I'm not sure what this means. Should this not be used over gRPC, only RPC? Do the proofs intentionally disappear depending on where this type is used?

It seems both Hermes and the Go relayer rely on strictly RPC for quering IBC client state, but it's not clear to me why since this type exists - unless - it's knowingly broken, or am I completely missing part of the picture here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant