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

fix: zero sequence check on relative time #740

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

ChrisCho-H
Copy link
Contributor

I've just found out RelLockTime misses zero sequence check, which must be disallowed for miniscript.

@apoelstra
Copy link
Member

Great catch! I will also copy this commit into #735 so it gets backported to 12.x.

Copy link
Member

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK c128e79 successfully ran local tests

@apoelstra apoelstra merged commit 734d34e into rust-bitcoin:master Sep 3, 2024
30 checks passed
apoelstra added a commit that referenced this pull request Nov 27, 2024
9cedc49 bump version to 12.3.0 (Andrew Poelstra)
9420012 fix: zero sequence check on relative time (Chris Hyunhum Cho)
5147c6f descriptor: don't accept strings of the form tr(<key>,) (Andrew Poelstra)
6401c22 miniscript: fix string serialization of and_n (Andrew Poelstra)

Pull request description:

  We are incorrectly serializing and_n as "and_b", and incorrectly parsing `tr(<key>,)`.

  In master the `and_b` thing is fixed by #722 which rewrites the Display impl completely and the `tr(<key>,)` thing will be fixed as part of a coming series of PRs to clean up expression parsing.

  Also includes #740 since it showed up in time.

ACKs for top commit:
  sanket1729:
    ACK 9cedc49

Tree-SHA512: edd45781db5b712e6013a396f6840ce74a6b32861b58a4df25e457c46c845c225dcde95f6c33db7fa314a1c4d2857515f40608d9c66e9432994cadf3d2f10e78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants