Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 task done
udit-gulati opened this issue Sep 1, 2024 · 1 comment
Open
1 task done
Labels
S:needs more info This bug can't be addressed until more information is provided by the reporter. T:Bug

Comments

@udit-gulati
Copy link

udit-gulati commented Sep 1, 2024

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

@udit-gulati udit-gulati changed the title [Bug]: [Bug]: public_key in signing_infos is NULL for a celestia mainnet transaction Sep 1, 2024
@tac0turtle
Copy link
Member

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

@julienrbrt julienrbrt added the S:needs more info This bug can't be addressed until more information is provided by the reporter. label Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S:needs more info This bug can't be addressed until more information is provided by the reporter. T:Bug
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants