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.

Sign up for GitHub

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

Jump to bottom

runtime panicked with Transaction has a bad signature at #8077849 #3487

Closed
EclesioMeloJunior opened this issue Sep 19, 2023 · 1 comment · Fixed by #3494
Closed

runtime panicked with Transaction has a bad signature at #8077849 #3487

EclesioMeloJunior opened this issue Sep 19, 2023 · 1 comment · Fixed by #3494
Assignees
@EclesioMeloJunior

Comments

@EclesioMeloJunior
Copy link
Member

Describe the bug

  • Gossamer sync stalls at block #8077849 with runtime panicking as shown in the image
image
@EclesioMeloJunior EclesioMeloJunior changed the title runtime panicked with 'Transaction has a bad signature' at #8077849 runtime panicked with Transaction has a bad signature at #8077849 Sep 19, 2023
@EclesioMeloJunior EclesioMeloJunior self-assigned this Sep 19, 2023
@EclesioMeloJunior EclesioMeloJunior mentioned this issue Sep 25, 2023
Merged
@q9f
Copy link
Contributor

q9f commented Sep 25, 2023

caused by go-schnorrkel fix in response to the 2021 trail of bits audit, ref ChainSafe/go-schnorrkel#39

this fix is not present in rust schnorrkel and since these transactions made it to mainnet, we need to deal with them in a special case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EclesioMeloJunior EclesioMeloJunior

Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@EclesioMeloJunior @q9f