Jesse de Wit

@ddustin it doesn't help. Currently running v22.11.1 with those changes you suggested. Here's a case with a 'normal' channel open: ## Accepting side ``` 2023-01-05T14:39:05.064Z DEBUG lightningd: Adding block 103:...

@ddustin Would it be an idea to use the old debugging technique `log(1)`, `log(2)`, etc? If you can make a commit with a ridiculous amount of log statements I can...

> @JssDWt figured it out: the max possible receive amount for not opening a new channel doesn't take into account the extra commitment fee for a htlc. (a bug that...

@cdecker I moved the commits around a little bit. Only tracing payment_continue now, because under some circumstances it seemed that the traces got intertwined. Also incorporated your suggestion [here](https://github.com/ElementsProject/lightning/pull/7556#discussion_r1719490112) It...

Rebased. And also fixed a bug where the `error` field would be `false` when there was an error and vice versa.

@ddustin What are your thoughts on adding the mindepth parameter in order to allow for zero conf splices?

@ddustin What is the state of this discussion?

> I don't believe anyone's working on zero conf splices at the moment The splicing spec has changed in meantime to allow 0-conf splices. It now uses [acceptable depth](https://github.com/lightning/bolts/pull/1160/files#diff-ed04ca2c673fd6aabde69389511fa9ee60cb44d6b2ef6c88b549ffaa753d6afeR1884) rather...

> @kingonly are you planning to support it any time soon? do you need some help from us to adopt this feature (bug wise ofc) @vincenzopalazzo We can roll this...

Capitalized error strings and use `ok_or` rather than a verbose `match` statement.