-
Notifications
You must be signed in to change notification settings - Fork 30
Fix PushDrop.decode to support lockPosition='after' parameter #467
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
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
🏁 Benchmark Comparison (Node 22)Comparing this PR (303c958) against master (fe07829). ✅ No regressions over the 5% threshold detected.
|
🏁 Benchmark Comparison (Node 22)Comparing this PR (2a68c5f) against master (fe07829). Regressions
|
|
🏁 Benchmark Comparison (Node 22)Comparing this PR (55b3a97) against master (fe07829). ✅ No regressions over the 5% threshold detected.
|



Description of Changes
PushDrop.decode()now accepts an optionallockPositionparameter ('before' | 'after', defaults to 'before')OP_CHECKSIG) instead of assuming it's at the beginningLinked Issues / Tickets
Closes Issue #259
Testing Procedure
Added test case: "decodes the locking script correctly with lockPosition after"
I have added new unit tests
All tests pass locally
I have tested manually in my local environment
Checklist
CHANGELOG.mdwith my changesnpm run docandnpm run lintone final time before requesting a reviewts-standardnpm version patchso that my changes will trigger a new version to be released when they are merged