core-lightning/plugins/spender
niftynei ef1e36efe5 mfc: check that we can retry when things go haywire
There's a version of this that keeps the PSBT in memory and does some
fancy addition/subtraction of unuseable parts for the v2's, however
it's much easier and simpler to simply error on the peer and re-start
from the very beginning.

This only works if we haven't gotten commitments from the peer yet (in
fact either method would only work if we haven't got commitments from
the peer yet), so if we've got commitments from them we simply mark them
as failed an go again.

In a perfect world, we'd remember what inputs we used last time, and
reuse those again on the re-attempt, which would pefectly guarantee both
that the failed opens (ones w/ commitments exchanged) would be canceled
after this completes (and we could re-try the failed again).

As it is, this is not perfect. It is, however, servicable.
2021-03-15 14:08:44 +10:30
..
fundchannel.c fundchannel: take a 'close_to' address 2020-10-16 13:51:57 +10:30
fundchannel.h plugins/spender/fundchannel.c: Make fundchannel a thin layer around multifundchannel. 2020-09-10 15:28:50 +09:30
main.c libplugin: make init return a string. 2021-01-13 14:45:36 +01:00
multifundchannel.c mfc: check that we can retry when things go haywire 2021-03-15 14:08:44 +10:30
multifundchannel.h mfc: have error messages for redos be more robust (include why) 2021-03-15 14:08:44 +10:30
multiwithdraw.c plugins/spender/multiwithdraw.c: Implement multiwithdraw command. 2020-09-09 20:36:08 +09:30
multiwithdraw.h plugins/spender/multiwithdraw.c: Implement multiwithdraw command. 2020-09-09 20:36:08 +09:30
openchannel.c mfc: have error messages for redos be more robust (include why) 2021-03-15 14:08:44 +10:30
openchannel.h mfc-df: after sigs are collected, go sign the psbt 2020-11-23 12:41:05 -06:00