-
Notifications
You must be signed in to change notification settings - Fork 120
Custom On-chain Fee Rate for Loop Out? #927
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
what fee are you seeing when you specify a fast confirmation target? if it's really stuck at the maximum fee rate and you want to bump it even more than that you can do bumpfee |
Thanks for the quick response! The issue is that the only option I’m given in the GUI is to specify a confirmation target block number, which—due to validation rules—can only start at 100 blocks. That’s way too slow for my needs. If I leave that field blank, the fee ends up being just a bit over 1 sat/vbyte, which results in the transaction getting stuck for a long time, especially with the current mempool congestion. What I’d really like is the ability to set an exact fee rate, e.g., 15 sat/vbyte, directly when initiating the loop out. Also, could you please clarify how exactly bumpfee works in this context? Is there a way to use it with a loop out that’s already been initiated through Umbrel? Some guidance or examples would be much appreciated. |
that sounds like a wrong validation then, it should allow for a fast conf target @levmi this would correspond with the
|
Are you using the litd binary UI or terminal.lightning.engineering? |
Hi team,
I’m using Lightning Terminal on Umbrel to perform loop outs from the Lightning Network to on-chain BTC. A major issue I’m facing is the inability to manually set the on-chain fee rate.
The GUI only allows setting a confirmation target (starting from 100 blocks), which is too slow for my use case. I want the loop out to confirm as quickly as possible.
If I leave the field blank, the fee defaults to something like 1 sat/vbyte, which is way too low given the current network congestion. As a result, transactions get stuck in the mempool for a long time.
Is there a way—through Umbrel’s terminal, CLI, or config—to specify the exact fee rate (e.g., 15 sat/vbyte) manually?
Thanks!
The text was updated successfully, but these errors were encountered: