Antoine Riard

> Hello @ariard, this PR has had unaddressed review comments for over nine months. Are you still working on this? Yes re-implementing my own node in rust(https://bitcoinbackbone.org/). While not there...

> and is not expected to make any progress until an undetermined time in the future. This is a presumptuous and gratuitous statement, which actually does not level-up the technical...

Yes the rbf rule 2 bypass is an old known issue and yes the rbf rules are fairly broken. For bitcoin clients fee-bumping chain of transactions, they should ensure to...

I agree with other reviewers so far that we’re better to analyse a set of replacement rules in a logical whole. Be it a holistic upgrade as what could be...

> ...there a way to apply a formatter to just new code (ie format a commit) as a tool for those who don't want to format their code manually/want to...

Concept ACK, we can still stop to use formatter if it's too much a burden, or can't we exclude some lines of it, there is no per-line granularity?

I think you can have a look on the discussions in the old #21224 PR. At the time, there were few ideas discussed for the wider mitigations of CPU usage...

Related #1641, as reliable benchmark could be a source of information towards node operators in selecting the appropriate deployment for their needs.

> Moreover, things like “splitting the channel and HTLC state machines” I’m not sure is really practical, so it seems strange to put it in an issue unless you have...

> TLDR: trimmed value can go into the anchor itself, and is simply spent to fees by the spender. I believe this is broken - Let’s say you have Alice...