While consulting documentation on the prevalidator, it describes portions of the mempool as bounded sets:
For instance, in Alpha, contracts have counters, and operations with counters in the future are classified as temporarily refused. A malicious peer could easily flood the mempool with such operations, so they are put in a bounded set. Another bounded set is also kept for a third kind of non inclusion: operations that could be valid in another branch.
What are the bounds / limitations on portions of the mempool?
- Is there a limit on the number of operations with future counters an address can have?
- Is there a maximum size in bytes?
- Are there cases where valid operations could be submitted to the node which do not persist in the mempool?