Cap witness data to 400kb and try a reasonable small limit on OP_RETURN of like 4kb or something and monitor to see if it's an effective release valve. Combines fixing the problem with a cautious systems approach to a solution.

Replies (1)

Arguably, everybody now could bring the OP_RETURN down to zero with the current implementation of Core/Knots. Which would address that concern of yours and this whole thing might be a good catalyst to have people configure it in more limited ways than the default. Now the witness data itself...what is the minimum required datasize for it to work optimally and consistently? Why is that not being discussed as part of solution for the spam in the witness?