Bump htlc resolution transactions feerate#3592
Merged
Merged
Conversation
1 task
616a432 to
16319f6
Compare
Contributor
Author
|
Rebased after #3570 was merged. |
16319f6 to
b7c0859
Compare
463aa90 to
b7c0859
Compare
A CONSERVATIVE/3 target for them. Some noisy changes to the tests as we had to update the estimatesmartfee mock. Changelog-Changed: We now use a higher feerate for resolving onchain HTLCs and for penalty transactions
Contributor
Author
Thanks this uncovered a fix which I thought having comitted but which was not part of the commit history anymore. |
Collaborator
|
ACK 4723860 |
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
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.
This builds upon #3570 to, now that we have a specific feerate for them, bump the feerate estimation target for HTLC resolution and penalty transactions.