Pierre-Marie Padiou dceb6b9b06 Better handling of force-closing of channels (#483) ... As soon as we receive a valid closing signature, we will publish the resulting closing tx instead of our commitment tx if we need to immediately close the channel (before end of negotiation, e.g. in case of errors, or in case the counterparty goes OFFLINE). When the closing signature didn't correspond to one we sent ourselves, we weren't properly recognizing the publishing tx and went into `ERR_INFORMATION_LEAK` state. CMD_CLOSE is now split it to commands: * `CMD_CLOSE`: this command will succeed only if the current channel state is in NORMAL, or if the channel hasn't yet been created. * `CMD_FORCECLOSE`: the channel will publish its current local commitment (or its best signed closing tx if it has one). Using `CMD_FORCECLOSE` is more expensive and it incurs a delay before funds are spendable, but this can be useful in some situations, for example when the counterparty isn't responding anymore. Added a new `forceclose` method to the API and a force close button in the GUI.		2018-03-15 18:53:14 +01:00
..
src	Better handling of force-closing of channels (#483)	2018-03-15 18:53:14 +01:00
pom.xml	back to SNAPSHOT	2018-02-16 18:10:35 +01:00