Skip to content

Conversation

@darosior
Copy link
Contributor

Wonder if we should check that the timelock value is minimal too, what do you think?

This changes the ZeroTime error into an InvalidTime error and checks
that the disabling bit (most significant one) isn't set in the timelock
value.

We could also check the value is minimal, using the mask.

Signed-off-by: Antoine Poinsot <[email protected]>
Copy link
Member

@sanket1729 sanket1729 left a comment

Choose a reason for hiding this comment

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

utACK a3dd9fe . Thanks for doing this.

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 a3dd9fe

@apoelstra apoelstra merged commit 8887663 into rust-bitcoin:master Sep 8, 2021
@darosior darosior deleted the check_t_older branch February 7, 2022 09:00
heap-coder added a commit to heap-coder/rust-miniscript that referenced this pull request Sep 27, 2025
…timelock values aren't too large

a3dd9fe840c8cdae84e9d586cd9a9d6c195f0092 miniscript/types: check that timelock values aren't too large (Antoine Poinsot)

Pull request description:

  Wonder if we should check that the timelock value is minimal too, what do you think?

ACKs for top commit:
  sanket1729:
    utACK a3dd9fe840c8cdae84e9d586cd9a9d6c195f0092 . Thanks for doing this.
  apoelstra:
    ACK a3dd9fe840c8cdae84e9d586cd9a9d6c195f0092

Tree-SHA512: 900c4de066581a0aa3137349c75336c30bc2b70239f47d5dab4ce2b1b33fb40428ce27837916767e51c03a1340c3f86cec036825e5da277216b892cbdbfb54a2
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.

3 participants