Closed jackzampolin closed 4 years ago
As these queries require proofs, they must all be direct store queries and can be performed using the existing store query logic, so no additional modifications are needed on the SDK side, correct?
@cwgoes thats the plan, and the way it is currently implemented. All queries from the relayer return proofs. See QueryConnection
https://github.com/cosmos/relayer/blob/master/relayer/query.go#L153
Currently we are debugging the proofs not returning properly
Closing in favour of https://github.com/iqlusioninc/relayer/issues/30
The following queries for IBC need to be implemented on the relayer. All of these queries should also return proofs. They will be mainly useful for use in
tx
commands (as a way to query the chain for the necessary on-chain data) but should also be exposed to the user:header [chain-id] [height]
- Query the header at a given heightnode-state [chain-id] [height]
- Query the node state at a given height or latest if height not passedclient [chain-id] [client-id]
- Query details for an individual clientclients [chain-id]
- Query the list of clients on a given chainconnection [chain-id] [connection-id]
- Query details for an individual connectionconnections [chain-id] [client-id]
- Query the list of connections associated with a clientchannel [chain-id] [connection-id] [channel-id]
- Query details for an individual channelchannels [chain-id] [connection-id]
- Query the list of channels associated with a clientseq-send [chain-id] [channel-id]
- Query theseq-send
for the configured key on a given chain and channelseq-recv [chain-id] [channel-id]
- Query theseq-recv
for the configured key on a given chain and channelpacket-commitment
packet-ack
packet-timeout
packet-data
- NOTE: This should be implemented by querying a full node with specific indices setup