Lightning Dev Kit
Unable to come to consensus about closing feerate #2826
-
|
I get the following error when trying to initiate a coop close (regtest).
This causes a force close and I never seem to get a |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Sadly there's only so much we can do about this for now. This is a pretty common issue for various reasons (often Bitcoin Core providing fee estimates without having enough history to provide robust fee estimates or just nodes using drastically different fee estimators). We're hoping the "v3 coops close negoation" protocol fixes it by removing this class of errors.
How long did you wait? Note that because its a force-close you have to wait the to-self-delay which is potentially a day or two. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, after playing around with fees the coop close case worked fine. Had to wait for the 144 blocks for the force close 👍🏿 |
Beta Was this translation helpful? Give feedback.
Sadly there's only so much we can do about this for now. This is a pretty common issue for various reasons (often Bitcoin Core providing fee estimates without having enough history to provide robust fee estimates or just nodes using drastically different fee estimators). We're hoping the "v3 coops close negoation" protocol fixes it by removing this class of errors.
How long did you wait? Note that because its a force-close you have to wait the to-self-delay which is potentially a day or two.