Jon Atack

re-ACK b5eba9ad001f1035dd641bc5880cb6bb53a8b07f

re-ACK d87cb99bb37637e26a9e00b9f7de4bc6f44cb79d

> with full debug logging enabled (e.g. lock contention) If useful, the steps to take are described in https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#debug_lockcontention (and in the debugging section of that doc, in general).

Updating and rebasing.

Thanks for the detailed feedback, @ajtowns. Will update with it in mind; looks like it will be helpful in simplifying things.

Closing temporarily so that I can re-open it -- am still interested to finish this.

Have been waiting for bugfix #27231 to be merged to update here, but it seems useful to re-open it before so that people are aware of it. Given how long...

> Why not just make `LogPrint` default to DEBUG instead of NONE Much of the added value from moving to severity-level logging IMO comes from splitting LogPrint to trace or...

Closing to be able to re-open it.

See https://github.com/bitcoin/bitcoin/issues/26754 for why this may not be a good idea, namely: *Also in that doc, in the bandwidth section at the bottom, please encourage people to share as much...