Antoine Riard
Antoine Riard
> Technically blocked on interactive txs. But yeah, a few things I need to update before some conceptual/approach review here. If this is blocked on review interactive txs on the...
> Jurvis had two sketches up in his fork and will be putting a PR together as per the first action item here: https://gist.github.com/jurvis/98215abd6fd392a3f2f0ded03c5c6fff. @jurvis If you have a branch...
> Should be ready in the next couple of days! Many thanks, left a couple of review feedback on the new poc PR. If Duncan or you can maintain a...
By exposure do you mean at the counterparty-level or at the network-level? Unclear to me without spec modifications.
So announce `max_dust_htlc_exposure_msat` as a new `open_channel`/`accept_channel` param or as a new BOLT7 `channel_update` param ? Or something different ?
cc @devrandom @elichai @moneyball
Yes, I think a lot of complexity are likely to end in the signing backends and middleware beyond rust-lightning. We might still have to adapt some our internal APIs if...
@devrandom @valentinewallace @TheBlueMatt As you’re the current code of conduct team members, I’ll request your individual review on the proposed changes. If you’re NACK about them, I would like to...
@ConorOkus @jkczyz @dunxen As you have ACKed the original code of conduct PR, if the changes proposed here sounds unreasonable to you, thank to express an opinion.
Updated at fa82902 with new suggestion to address Matt’s feedback and bumped to 3y period.