Closed b-j-roberts closed 4 hours ago
@b-j-roberts please can i work on this
Hey @Kaminar-i! Thanks for showing interest. We've created an application for you to contribute to shinigami. Go check it out on OnlyDust!
Hey @ShantelPeters! Thanks for showing interest. We've created an application for you to contribute to shinigami. Go check it out on OnlyDust!
Hey @b-j-roberts I want to work on this
Hey @PavitraAgarwal21! Thanks for showing interest. We've created an application for you to contribute to shinigami. Go check it out on OnlyDust!
This bug is happening due to the way PUSHONLY OPCODE was implemented
A quick log along the execution path should show what is happening
@b-j-roberts kindly assigned
@b-j-roberts please can i work on this
@Kaminar-i Yes, I can assign you. Welcome to the project. Please let me know if you have any questions, I will reach out in a couple days to check on progress 🚀
@Kaminar-i Any luck debugging this script yet? Did you have any questions?
Hi @Kaminar-i @b-j-roberts I think that the problem of this issue might be in the pull_data function, you could check it after #221 it is integrated
This was resolved as part of this PR, thank you for looking into it.
Issue
The following bitcoin-core test is failing to give the correct result :
This code should be failing with a
p2sh not pushonly
error within the engine, but is passing. This is most likely due to the NOP8 opcode execution in the Script sig not giving thep2sh not pushonly
error like it should.Replicate
To replicate the issue you can use the latest
main
branch with the following command:This comment might help some with how to debug : https://github.com/keep-starknet-strange/shinigami/pull/192#issuecomment-2322981566