-
Notifications
You must be signed in to change notification settings - Fork 43
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
security: maker can lock taker funds #1048
Comments
Is there anything we can do to prevent this? Also per #1049 (comment) I don't think unlocking the funds requires a force-close. |
No AFAIK. @offerm? |
For this case the taker should force close the channel and not use this peer again. Note that this can be done by any node along tge route and not just by the maker. This should not be considered as a big problem since there is no risk of losing money and you can prevent that peer for the next payment |
Todo: documentation on how to resolve via force close |
I removed the critical bug label since there is nothing to be fixed (or to be done at all) in the xud codebase to prevent this - whoever sends payment first (in our case the taker) can have the recipient (maker) delay up to the HTLC expiration and that's just the way the network is designed. And this is not a risk of losing funds. What we need to be sure we are doing is penalizing peers for this, this ties into the greater scheme of how we detect and deal with misbehaving peers. As for force closing the channel, I believe that if that is necessary it is handled by lnd automatically - it does not require us to intervene to prevent loss of funds. |
Scenario:
Outcome: taker funds are locked due to the pending HTLC (unless the maker will cancel the invoice), until the taker will force-close the channel on-chain.
The text was updated successfully, but these errors were encountered: