ebaf162a96
This commit improves the script builder API to better align with Bitcoin semantics when working with relative timelocks: - Add push_relative_lock_time() method that takes a relative::LockTime parameter, which correctly represents the semantic meaning when working with CHECKSEQUENCEVERIFY - Deprecate push_sequence() in favor of push_relative_lock_time() to avoid confusion between sequence numbers and relative timelocks This addresses a potential confusion point in the API where developers might incorrectly push raw sequence numbers in scripts when what they actually need is to push a relative locktime value that will be checked against the transaction's sequence numbers by CHECKSEQUENCEVERIFY. |
||
|---|---|---|
| .. | ||
| contrib | ||
| embedded | ||
| examples | ||
| src | ||
| tests | ||
| CHANGELOG.md | ||
| Cargo.toml | ||