You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
If I query a
QueryClientStateRequest
I get back aQueryClientStateResponse
- but without the proofs.Is this expected behavior? The comments do say:
... 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?
The text was updated successfully, but these errors were encountered: