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

pcli ux: display counterparty client ids in ibc queries #4667

Open
conorsch opened this issue Jun 26, 2024 · 0 comments
Open

pcli ux: display counterparty client ids in ibc queries #4667

conorsch opened this issue Jun 26, 2024 · 0 comments
Labels
A-client Area: Design and implementation for client functionality _P-low Priority: low

Comments

@conorsch
Copy link
Contributor

Is your feature request related to a problem? Please describe.
When I run pcli query ibc channels I want to compare client ids for the host (i.e. Penumbra) and counterparty (e.g. Osmosis testnet) chains. Currently, pcli only shows the host client ids, not the counterparty's. Let's fix that.

Describe the solution you'd like
Add a column to pcli query ibc channel{,s} to display client id for counterparty chains.

Describe alternatives you've considered
Today during Testnet 78 hermes maint (#4582) we used the cuiloa block explorer https://cuiloa.testnet.penumbra.zone/ibc/channels to figure out the counterparty channel id.

Additional context
This is a nice-to-have, it's not critical. But oh man would it make interacting with ibc easier.

@github-actions github-actions bot added the needs-refinement unclear, incomplete, or stub issue that needs work label Jun 26, 2024
@conorsch conorsch added A-client Area: Design and implementation for client functionality _P-low Priority: low and removed needs-refinement unclear, incomplete, or stub issue that needs work labels Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-client Area: Design and implementation for client functionality _P-low Priority: low
Projects
Status: Backlog
Development

No branches or pull requests

1 participant