Keags

> The major question that I have for this PR is whether you'd be open to breaking the change up into two parts: > 1. Rules + commitment update (not...

> The difficulty here is that option_simple_taproot also falls into the commitment transaction category (1). There is a path here where we consider this upgrade mechanism to only apply to...

> Meant that we could use dynamic commitments to only update our commitment transaction to use taproot without upgrading the funding output, introducing an inbetween channel type that has a...

> That's very dangerous as an attacker can trivially exploit this: they just need to offer very high fees to compensate for their bad reputation (it doesn't cost them anything...

Concept ACK Seems like you should also specify this requirement in the [CONTRIBUTING.md](https://github.com/lightning/bolts/blob/master/CONTRIBUTING.md) Also this is the type of thing you probably need a GitHub workflow to enforce, it's hard...

Perhaps this is a misunderstanding on my part for how the document is organized, but wouldn't you still have to support the original `closing_signed` message in the main BOLT docs...

Yeah I understand the desire to remove deprecated stuff. I just wonder what a "valid" implementation looks like here. If we implement this change, and essentially drop support for the...

I too just ran into this. I was reimplementing MiniScript in Haskell over [here](https://github.com/ProofOfKeags/plebfi-hackathon/blob/master/src/MiniScript.hs) and couldn't square some of the stuff I was seeing.

It's possible that it isn't related to it being short lived, that part is speculation. The observed behavior is that if I launch several (4) processes using `typed-process` with `conduit`...

I completely forgot about this. No updates as of right now. Not sure when I'll be able to get to it.