niftynei e66937e012 mfc: Add a commitment_feerate optional parameter to multifundchannel ...

Technically there *are* two feerates that we need to know:
  - the feerate to use for the funding transaction, and
  - the feerate to tell our peer to use for our commitment txs/htlc txs

As written, `multifundchannel` uses the same feerate for both. This
optional parameter will allow us to differentiate between the two, which
will be exceedingly handy for anchor output worlds. ;)

FIXME: test this

Changelog-Added: JSON API: `multifundchannel` has a new optional argument, 'commitment_feerate', which can be used to differentiate between the funding feerate and the channel's initial commitment feerate

2020-10-21 11:24:16 +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

plugins/spender/fundchannel.c: Make fundchannel a thin layer around multifundchannel.

2020-09-10 15:28:50 +09:30

multifundchannel.c

mfc: Add a commitment_feerate optional parameter to multifundchannel

2020-10-21 11:24:16 +10:30

multifundchannel.h

plugins/spender/multifundchannel.c: Move multifundchannel to the spenderp plugin.

2020-09-10 15:28:50 +09: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