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] Client fails on block: 757739: Script validation failed on tx_idx: 1, input_idx: 0: Signature DER error #257

Open
maciejka opened this issue Oct 10, 2024 · 10 comments
Labels
advanced bug Something isn't working

Comments

@maciejka
Copy link
Collaborator

maciejka commented Oct 10, 2024

Description

In packages/client command:

scarb test --forceall --execute_scripts  tests/data/full_757738.json 

fails with:

Script validation failed on tx_idx: 1, input_idx: 0: Signature DER error
@maciejka maciejka added bug Something isn't working advanced labels Oct 10, 2024
@akintewe
Copy link

Hello can i be assigned this issue

@maciejka
Copy link
Collaborator Author

Hello can i be assigned this issue

How are you going to approach it?

@akintewe
Copy link

What ill do is I will analyze transaction 1, input 0 in block 757739. I'll verify the signature's DER encoding, ensuring compliance with BIP66. I'll add granular logging to the DER decoding process, comparing our output with a reference node. I'll scrutinize our recent commits affecting signature validation, implement necessary fixes, and create a targeted test case replicating this scenario. I'll then validate the fix by re-running the full_757738.json test.

@bloomingpeach
Copy link
Contributor

I tried and it seems to work, no more error. @maciejka

@akintewe
Copy link

@maciejka can i still work on it please

@maciejka
Copy link
Collaborator Author

I tried and it seems to work, no more error. @maciejka

The command in the description missed an execute_scripts. Bonus points for being alert.

@maciejka
Copy link
Collaborator Author

@maciejka can i still work on it please

Thanks for your readiness to work. We want to consult Shinigami project first.

@akintewe
Copy link

Thank you so much

@bloomingpeach
Copy link
Contributor

bloomingpeach commented Oct 14, 2024

@maciejka
image

It is most likely because witness checksig(for segwit) has not been implemented in Shinigami yet.

@SoarinSkySagar
Copy link

Hi @maciejka, can I work on this issue? Please give your telegram/discord username so I can propose my approach and/or discuss any other solutions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants