Matt Corallo
Matt Corallo
One more thing we need to add to docs here before we ship is note that the signing `validate_*` methods may be called for two different commitments at the same...
Supersceded by #3115, #3150, #3152, etc.
The dust exposure we have on our current channel which is limited by the config knob.
Well, it wasn't needed, but now it is again....the dust exposure used to just be the sum of dust HTLCs, however in more recent releases it also considers the channel's...
Just needed a rebase.
Its just one commit already in a release, merging.
Tagging 0.0.122 not because we need to land this for 0.0.122, but because we have to at least be roughly confident in it working and the tests in it being...
Okay, sounds like @valentinewallace took a glance at this, and I did too. Nothing too wild here, tests pass, we can do this in the next release (or whenever), but...
Yea, I don't see why not? Just cause we're branching off for future releases doesn't mean we can't/shouldn't have future code behind cfg flags on the working tip.
I think we're probably okay without now. @valentinewallace checked today and said support was added in 0.0.123, which means if we ship this we'll support downgrading two versions of LDK...