Refine IBC Integrations

[ejmg]

Summary

Currently, there are extremely minimal offerings for IBC Clients, Channels, and Connections on Cuiloa. You can see a list of each type and which ones are associated with each other. However, this leaves users with little transparency w.r.t. the state of e.g. an IBC channel and any transactions that may have occurred over it. Similarly, nothing is shown for the state, response, and status of the counter-party. Other details, like the expiration of a given client are also completely unavailable.

In addition to this, details like individual connections and the explicit enumeration of all related IBC entities is largely unnecessary. IBC Channels are primarily the object of interest for a user that wants to see what IBC integrations are established between Penumbra and counter-party chains and the status of any previous/on-going IBC transactions.

Sub-tasks

• IBC Clients and Connections should be largely de-prioritized as individual routes
  • Views for all clients and connections are not a primary concern of client navigation
  • Redundant information should be removed from the existing views
    • It might be desirable to completely retire some or all of the views related to Clients and Connections
    • At minimum, "dumbing them down" to their bare minimum is a good start
• Channels should be expanded and re-worked to include the following:
  • Provide information on the relevant counter-party chain
  • Associated IBC transactions data, including:
    • Enumerating all transactions over a channel
    • Visualizing the state and progress of individual transactions
• (de)serialization support for IBC Events
  • IBC data include base64 raw JSON data that includes the js prototype for handling the respective e.g. token data
    • when an IBC event occurs, the associated transaction event will include the raw bytes representing e.g. the transfer
    • should be able to decode the inner bytes and use for application logic