-
Notifications
You must be signed in to change notification settings - Fork 268
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
Expired payment in ACINQ channel #691
Comments
Channel ID is |
Damn, nice catch again! This is similar to #649, but a little bit different: (a) Let's say remote is at commitment N NB: since #649 we would have failed the htlc if our commitment (which also didn't contain the htlc) had made it to the chain. This should be done here: eclair/eclair-core/src/main/scala/fr/acinq/eclair/channel/Helpers.scala Lines 736 to 752 in 12a80af
Currently the failing of htlcs is only triggered by downstream channels. I'm thinking that for extra safety, the upstream channel (the one that received the htlc) could decide to fail the htlc right before the expiration, it is probably always better than closing the channel. |
When we just signed an outgoing htlc, it is only present in the next remote commit (which will become the remote commit once the current one is revoked). If we unilaterally close the channel, and our commitment is confirmed, then the htlc will never reach the chain, it has been "overriden" and should be failed ASAP. This is correctly handled since 6d5ec8c. But if remote unilaterally close the channel with its *current* commitment (that doesn't contain the htlc), then the same thing happens: the htlc is also "overriden", and we should fail it. This fixes #691.
When we just signed an outgoing htlc, it is only present in the next remote commit (which will become the remote commit once the current one is revoked). If we unilaterally close the channel, and our commitment is confirmed, then the htlc will never reach the chain, it has been "overriden" and should be failed ASAP. This is correctly handled since 6d5ec8c. But if remote unilaterally close the channel with its *current* commitment (that doesn't contain the htlc), then the same thing happens: the htlc is also "overriden", and we should fail it. This fixes #691.
A
45 SAT
payment has been sent throughphone <-> ACINQ
channel a few days ago, as of now it is expired (but channel is still up since I've stopped closing them automatically), payment hash is3dd1ed8148d617f1705eeec896a569b0dc36de5726bafe13b3ca439b28c2bb81
.The text was updated successfully, but these errors were encountered: