dual-funding: update fee_step to be a feerate

Using a 'feestep' is more restrictive than you'd want, instead we
enforce that the next feerate must be at least 1/64th more than the
last, but put no upper limit on it

Includes update to lnprototest changes

Contributed-By: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Changelog-EXPERIMENTAL: Protocol: Replaces init_rbf's `fee_step` for RBF of v2 opens with `funding_feerate_perkw`, breaking change
This commit is contained in:
niftynei
2021-07-09 14:13:20 -05:00
committed by neil saitug
parent 04b6ad06cb
commit 376e6f8bd1
20 changed files with 181 additions and 174 deletions

View File

@@ -1039,12 +1039,13 @@ class LightningRpc(UnixDomainSocketRpc):
}
return self.call("openchannel_update", payload)
def openchannel_bump(self, channel_id, amount, initialpsbt):
def openchannel_bump(self, channel_id, amount, initialpsbt, funding_feerate=None):
""" Initiate an RBF for an in-progress open """
payload = {
"channel_id": channel_id,
"amount": amount,
"initialpsbt": initialpsbt,
"funding_feerate": funding_feerate,
}
return self.call("openchannel_bump", payload)