Each Cosmos connection includes one primary node and 0 or more fallback nodes. Generally, we only use the fallback nodes when there's an issue with the primary nodes. However, recently, we've observed an issue with Osmosis where occasionally:

• Our primary node is working as far as we can tell: queries work, blocks don't lag, etc.
• Broadcasting transactions to our primary node works, meaning that the broadcast itself succeeds
• However, the node has issues with its peers and is unable to continue propagating our transaction to validator nodes

One mitigation I thought of: each time we broadcast a transaction, automatically broadcast to all of our fallback nodes too, or at least the ones still marked as healthy. We can ignore any errors that happen during this broadcast. But in theory, this would allow us to route around a primary node that's having peer issues.

The CosmosNetwork enum has manually written FromStr and Display impls right now. The problem with this is that, when adding a new variant, it's easy to forget to add it to the FromStr impl. Instead, it would be nice to use a crate that provides macros for deriving those impls, and potentially others (e.g., providing a CosmosNetwork::all helper function).

I've never used either of these, but they're potential crates to investigate:

• https://lib.rs/crates/derive_more
• https://lib.rs/crates/strum

It would be convenient to be able to sign transactions using a Ledger hardware wallet. Currently such signing tends to happen in web apps instead. A very quick investigation pointed me to this:

https://lib.rs/crates/ledger-cli