Anthony Towns

> I would like to propose to replace the per-item size limit with a total stack size limit that is equivalent and can be introduced as a softfork as well....

I think the worst case scenario would be if you setup a block proposer node behind a single (bastion) full node (so that it doesn't have random things on the...

"it should have multiple implementations from independent authors released in different software packages" How are the multiple implementers meant to implement the same thing if they don't have a spec...

ACK fa9f6d7bcdba5f18c46fff1dcc0ac6d3dd8db75d Added some debugging code to verify that the removed RPCTypeCheck calls seem to match what the new logic will enforce.

Is there a (2/2) somewhere?

> Rebased on master. @ajtowns putting aside the current comments, any thoughts on including changes like this in bitcoin-inquisition? No objection to it, but not sure why it would be...

Commit message says "Also, fix l_atomic.m4 bug." but that doesn't seem to be touched?

I guess I've got conceptual questions about this. 1. It seems very intrusive to change `LogPrint(NET, "hi");` to `LogPrintLevel(NET, DEBUG, "hi");` everywhere. Why not just make `LogPrint` default to DEBUG...

> But anyway, I agree with @jonasnick here. BIP2 mandates this section only for BIPs that introduce backwards incompatibilities. Sounds like that reading of bip2 doesn't match current policy, https://github.com/bitcoin/bips/pull/1421#issuecomment-1442718400

I think there's two components here -- one is if a stranger wants to start a direct message with you how do you notice that without being swamped by spam,...