[Bug]: `public_key` in `signing_infos` is NULL for a celestia mainnet transaction

[udit-gulati]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

The signing_infos has public_key as NULL for transaction https://www.mintscan.io/celestia/tx/B928B3B0E35DDCB233B312CB628A4961C5CDB1D2C5867BA2F3B0F8A3B51336A6?height=713480&sector=json

The signing_infos in this txn is as follows:

[
  {
    "public_key": null,
    "mode_info": {
      "single": {
        "mode": "SIGN_MODE_DIRECT"
      }
    },
    "sequence": "56"
  }
]

Is this an expected behaviour or there should some addition checks in place to prevent this kind of txns from being included?

The account looks like an EOA and not a multisig or a module account.

Cosmos SDK Version

main

How to reproduce?

No response

[tac0turtle]

Hey were you able to recreate this in this repo on main? Celestia has a fork of the sdk today. We can check with them on the changes to the fork