Skip to content

Conversation

@t-bast
Copy link
Member

@t-bast t-bast commented Aug 19, 2025

We introduced a mechanism to limit the feerate used for non-urgent force-close transactions in #3097. We now provide a way to update this feerate on a per-channel basis, without restarting the eclair node, by using the forceclose API.

Fixes #3108.

We introduced a mechanism to limit the feerate used for non-urgent
force-close transactions in #3097. We now provide a way to update
this feerate on a per-channel basis, without restarting the eclair
node, by using the `forceclose` API.

Fixes #3108.
@t-bast t-bast force-pushed the max-force-close-feerate branch from 7a6b7e5 to 93db8ab Compare August 19, 2025 17:34
@t-bast t-bast marked this pull request as ready for review August 19, 2025 17:34
@t-bast t-bast requested review from pm47 and sstone and removed request for sstone August 19, 2025 17:35
We previously used the channel capacity to adapt the feerate used for
commitment transactions for mobile wallets, but now that we always
use anchor outputs and package relay for mobile wallets, that isn't
necessary anymore.
@t-bast t-bast requested a review from pm47 September 5, 2025 13:26
@t-bast t-bast merged commit d48dd21 into master Sep 5, 2025
1 of 2 checks passed
@t-bast t-bast deleted the max-force-close-feerate branch September 5, 2025 13:58
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.

Add maxClosingFeerate_opt to DATA_CLOSING

3 participants