Feature request: Allow higher than 144 block target for claim-main and mutual-close
See original GitHub issueIssue Description
I just had to pay 42 s/vB for a claim-main
tx. More than the 38 s/vB for the force closure itself. I assume this was partly due to a >24h full block period. Should still be much less since the former has a 6 block target while the latter has a 144 block target. So might be worth looking into that as well. Can provide logs if needed.
force closure: https://blockstream.info/tx/6a764119b4a52d01a794733c14b793e311183ac8acef1634513a8de207360e41 claim-main: https://blockstream.info/tx/9614abf33ae1db74316629a396362ab7ea80ea5b10faf8cfea145fee43c8e4e0
If targets of up to 2016 blocks were possible, one could always make use of cheap weekend fees to save money.
Worst case, those tx can be CPFPed in case they get stuck for too long.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
eclair/reference.conf at master · ACINQ/eclair - GitHub
// You may want to disable this when bitcoin is running on a remote machine with an unreliable network. batch-watcher-requests = true. }....
Read more >About the Brand | BLOCK Targets - FeraDyne Outdoors
BLOCK's award-winning series of game-changing archery targets allow arrows to find their way between layers of high-density foam, stopping them with friction ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As you can see a PR is ready that implements this. It should be merged soon.
any progress? Not having the option of a 1008 block target is costing me hundreds of thousands of satoshis on a regular basis.
what I also noticed is that LND nodes negotiate much harder in channel closure negotiations. The end result is always MUCH closer to what the LND node initially proposed. This is good for the rare cases where a peer is proposing less than my node but very costly in every other case.
would you consider negotiating harder as well? Preferably only for when peer is proposing a higher fee. (with a 1008 block target this should almost always be the case anyway though)