Open daniel-savu opened 5 months ago
Is it because the default one in mainnet3_config.json was used? https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/rust/config/mainnet3_config.json#L485
Turns out it was because we were still using https
instead of http
and the default that @tkporter pointed out is a plaintext URL. Wondering if there's a way to make it more clear in the error message
Problem
It's possible to run an agent for a cosmos chain and specify a gRPC URL with the wrong http protocol (e.g.
https
for plaintext ones). The agent will successfully run past the config parsing step, then print a bunch of "invalid message" / "corrupt message" errors and crash, which doesn't make it obvious what the issue isLogs:
Solution
Somehow return a better error message to have the user check the url prefix