No the problem won't be solved, as unfortunately there is no way to prevent spam in ANY protocol since spam is by definition a protocol-valid-operation.
Protocols handle spam with spam filters that mitigate the problem instead.
Discussion
So how to exclude data defined as spam from a valid block provided via the protocol?
Since spam transactions are protocol-valid, nodes must accept any valid block—even if it contains spam.
Our spam filters are designed to:
- Discourage VC investment in meta-protocols
- Signal to miners that we prefer not to include these transactions
Please note that MARA (via Slipstream) is currently the only miner processing non-standard transactions, but they appear likely to discontinue the service soon.
So discourage means: restricting someone
And
Signalling to miners: asking them for permission
This does not compute, for me.
> So discourage means: restricting someone
If you don't understand that this does not make sense, there is not much to discuss anymore.