Cosmos SDK HTTP API returns error when querying for a transaction hash

[fadeev]

Describe the Bug

https://zetachain.blockpi.network/lcd/v1/public/cosmos/tx/v1beta1/txs/6C86B759289ACB1BE2EEC35619B7F9227EC4AF4AC235BC70F366C1DCDF76539A

{"code":2, "message":"codespace sdk code 2: tx parse error: errUnknownField \"*types.MsgAddOutboundTracker\": {TagNum: 7, WireType:\"varint\"}", "details":[]}

Same with other RPC providers.

Interestingly enough, this tx exists in ZetaScan's indexer:

https://explorer.zetachain.com/cosmos/tx/6C86B759289ACB1BE2EEC35619B7F9227EC4AF4AC235BC70F366C1DCDF76539A

[lumtis]

It shows up in other explorer as well https://zetachain.explorers.guru/transaction/6C86B759289ACB1BE2EEC35619B7F9227EC4AF4AC235BC70F366C1DCDF76539A

I think we already reached out to blockpi about this

[CharlieMc0]

Just because it exists in an explorer doesn't mean this isn't an active bug in v23. It could have been indexed using v22 and retrieving the same TX does not work after v23.

[swift1337]

It's related to this PR (#3125); particularly this change in protos. reserved is placed validly, but seems there's an issue with decoding such messages

UPD: seems like we need to rollback reserved and keep legacy fields as deprecated. Will open a PR