feat(utxo): refactor replay protection to use public keys #7696
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a getter for the specific public key used for replay protection. This refactors the existing code to use this new method. Issue: BTC-2806 Co-authored-by: llm-git <llm-git@ttll.de>
Refactor replay protection to use the public keys directly instead of output scripts. The output scripts are now derived from the public keys, making the code more maintainable and easier to understand. Add tests for replay protection to verify that the output scripts match those computed from descriptors. Issue: BTC-2806 Co-authored-by: llm-git <llm-git@ttll.de>
lcovar
approved these changes
Dec 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Key changes:
getReplayProtectionPublicKeyto AcidTest in utxo-libIssue: BTC-2806