Allow Hermes to relay wasm messages

[ljoss17]

Summary

Hermes only detects ibc* events. By detecting wasm events it would be possible to relay wasm messages.

Acceptance Criteria

• Hermes can relay wasm messages

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[ancazamfir]

I think the solution here is to allow the configuration of desired message.module query strings.
Currently we have (defaults):
"ibc_client" - for client events
"ibc_connection" - for connection events
"ibc_channel" - for channel and packet events

[alpe]

I have found this issue while researching the neutron wasmd patch. Now I have some better context for the patch but I am wondering what the best solution would be?

In wasmd we keep only the root "message" event that started the process. Therefore "close channel" or ics-20 "transfer" messages emitted by a contract will not show up.

In my current understanding, hermes is looking at the message events emitted from ibc module operations for relayer work.
For example message.module = ibc_connection would cover
connection_open_init || connection_open_try || connection_open_ack || connection_open_confirm operations.
So I am thinking that it may make more sense to not rely on "message" events and "module" attribute but use the concrete events defined in ibc-go.
By doing this, the event queries would become a bit more complex but there would not be any need to make this "customizable" or patch wasmd.

[romac]

In wasmd we keep only the root "message" event that started the process. Therefore "close channel" or ics-20 "transfer" messages emitted by a contract will not show up.
So I am thinking that it may make more sense to not rely on "message" events and "module" attribute but use the concrete events defined in ibc-go.

@alpe I am not sure I understand what you mean here, could you please expand a bit on what's the problem and what you would suggest we do instead?

[alpe]

tldr: there is no ibc 'message' event when the channel was created via CosmWasm submessage. Same for IBC packet send.

If hermes would query the non "message" events types instead then it should all work nicely.

[ancazamfir]

@alpe is it possible to show us and example of the /block_results output for a block that includes the wasm emitted events, for example for packets sent/received?

[alpe]

@ancazamfir I don't have an example.
But as I tried to outline before: don't look at the wasm events but the ibc-go events instead.