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
hermes query clients cosmoshub-4 outputs a list of all clients registered on the chain, but it's just the client ids, which isn't that helpful, especially since they're lexicographically ordered:
Of course the ordering is because these are strings, and we don't read the suffix number. It might be good to read the suffix number so we can order properly.
But more important would be to include the ChainID information, otherwise we don't really get anything valuable here since we don't know what each client corresponds to, but if we output the ChainID along with the ClientID it would at least be easier to find clients for particular chains.
Acceptance Criteria
Output of hermes query clients is ordered numerically and includes ChainID along with ClientID
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate milestone (priority) applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Crate
relayer-cli
Summary
hermes query clients cosmoshub-4
outputs a list of all clients registered on the chain, but it's just the client ids, which isn't that helpful, especially since they're lexicographically ordered:Of course the ordering is because these are strings, and we don't read the suffix number. It might be good to read the suffix number so we can order properly.
But more important would be to include the ChainID information, otherwise we don't really get anything valuable here since we don't know what each client corresponds to, but if we output the ChainID along with the ClientID it would at least be easier to find clients for particular chains.
Acceptance Criteria
Output of
hermes query clients
is ordered numerically and includes ChainID along with ClientIDFor Admin Use
The text was updated successfully, but these errors were encountered: