We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We introduced soft error-handling because of other implementations sending us errors although the channel was still fully functional and could recover after restart. For more background see: C-lightning sending permanent channel failure on failed gossip sync ElementsProject/lightning#4212 We should Force-Close the channel as soon as we receive an error to be spec. compliant.
Moreover we need to also rethink our strategy of Force-Closing the channel if the next_commitment_number = 0because dual-funding has some use-cases where the commitment number is set to 0 and we should not force close the channel. For more info see: Do not unnecessarily retransmit commitment_signed in dual funding lightning/bolts#1214 (comment)
next_commitment_number = 0
commitment_signed
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We introduced soft error-handling because of other implementations sending us errors although the channel was still fully functional and could recover after restart. For more background see: C-lightning sending permanent channel failure on failed gossip sync ElementsProject/lightning#4212
We should Force-Close the channel as soon as we receive an error to be spec. compliant.
Moreover we need to also rethink our strategy of Force-Closing the channel if the
next_commitment_number = 0
because dual-funding has some use-cases where the commitment number is set to 0 and we should not force close the channel.For more info see: Do not unnecessarily retransmit
commitment_signed
in dual funding lightning/bolts#1214 (comment)The text was updated successfully, but these errors were encountered: