Blob spam protection mechanism

[arnetheduck]

The blob spam mechanism, as defined by #3244, opens up the possibility for a block producer to poison the seen cache of parts of the network and thus disrupting block propagation by introducing invalid blobs to some peers.

Although it is likely that such block proposers will lose their block, the network will nonetheless have to do additional work by trying to recover the blobs and blocks from participants using high-latency messaging (ByRoot requests since gossip gets disabled).

Potential control mechanisms include:

• deprioritising blocks from proposers that spammed the network (in the spirit of proposer boost)
• clearing seen cache when blob is determined to be invalid post-gossip-validation, thus allowing other blobs for the same block/index to propagate
• introducing new slashing conditions

Previous discussion:

• EIP-4844: Free the blobs #3244 (comment)
• EIP-4844: Free the blobs #3244 (comment)
• EIP-4844: Free the blobs #3244 (comment)