Alright. I see. So it should mean that the transactions should never get dropped from the mempool in practice.
Yet the users like KittenBob trying to convince me that the transactions are dropping from the mempool all the time. I am still trying to figure out when and why though.
he meant if there's too much unconfirmed transactions in the mempool,
a low fee tx might get dropped after the default timeout as most nodes are using default relay settings.
Example: December 2017 bubble. hover over dec 2017
During that time, a lot of unconfirmed transactions got dropped after 2 weeks.
-edit-
The blockchain explorer on bash (as well as mempool explorer BTW) that I published above works just fine. So the problem is solved. Now we just talking about deployment-related issues which is somewhat within topic.
Start a new topic with what you're actually trying to achieve with this.
Something like a mempool_explorer/API for low-value instant Bitcoin payment?
AFAIK, there's a few discussions in the past about a no-confirmation "coffee payments" and I've said something like this:
"If it's a coffee shop and the customer is there, he wont dare to double spend as his face is in plain sight (people/CCTV)"
BTW, even if you prevented "them" in your mempool, you have no control over other nodes.