-
Notifications
You must be signed in to change notification settings - Fork 128
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
Wrong message for pending closed channel #1278
Comments
I am not sure if this was solved so I can test for it. |
@Nackoo2000 It's not solved and was not part of this release but I'll take a look. |
@Nackoo2000 The numbers aren't wrong per se, but your account's tip height appears to be 0 when this dialog was opened. (blockheight - account's tipHeight) * 10 (In theory there is one block per 10 minutes) / 60 which gives us Could you try recreating this with latest build and share logs? We'll investigate why account response returned tip height as 0. I'll be removing the $ signs. |
When I reported this it was an old node that was in this state it was not during testing. |
You can use the cooperative close channels feature, the pending close transaction should appear on tx list |
The message does not appear if the estimation is below an hour.
The $'s are removed and there isn't anything wrong with the estimation calculations. I will be closing the issue. We need to understand why your account's |
Now I remember that this was not my issue but it came from a support case but I will be on the lookout for it. |
The numbers are wrong in the dialog message and the $ sign has to be removed.
The text was updated successfully, but these errors were encountered: