Skip to content
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.

Sign up for GitHub

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

Jump to bottom

distingish between closed and still dangling channels #106

Open
AleksandarFilipov opened this issue Jun 9, 2020 · 1 comment
Open

distingish between closed and still dangling channels #106

AleksandarFilipov opened this issue Jun 9, 2020 · 1 comment

Comments

@AleksandarFilipov
Copy link
Contributor

AleksandarFilipov commented Jun 9, 2020 •
edited
Loading

When a channel is closed it should be removed from dets, so it's not restarted. The same goes for channels which are considered as unrecoverable for some reason.
This could be a slightly tricky one, and we need a chat with SC poeple on all potental exit/close scenarios
@AleksandarFilipov AleksandarFilipov changed the title distingish between closed and still tangling channels distingish between closed and still dangling channels Jun 9, 2020
@AleksandarFilipov
Copy link
Contributor Author

AleksandarFilipov commented Jun 9, 2020 •
edited
Loading

"mutual_close" is aready handled but there are a number of other ways a channel can be closed (eg solo close - see testcase on this).

Thi also involves force progress which should probably be handled first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AleksandarFilipov