Null index for nested messages

[czarcas7ic]

v ✰ Thanks for creating an issue! ✰
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->

Background

See https://www.mintscan.io/osmosis/tx/AB8E8EB111D6711F9F36355F6B8A3622FFCD154B0DA24F1B311A428794CBD22C?height=15662413§or=message

The contract swap and action has message index 0 for the first message, but message index null for the second message

Lucas from Numia explained that this is causing issues with the indexer.

Suggested Design

First, understand why this is the message index here is null. If unexpected, determine what the fix must be to ensure the message index is always filled out.

Assumption

• we changed the event emission in v24 this could have something to do with this ask

Acceptance Criteria

Numia indexer functions properly due to message index's being properly filled out.

Reach out to Mintscan to verify this.