If you don't have control over your mempool, who the fuck do you think does? If everyone thought like you, they'd surrender to a dictatorship of developers dumbass.

Reply to this note

Please Login to reply.

Discussion

Sorry, the level of willful ignorance is just baffling.

bafflement is a red flag for malicious disinformation (and the dupes who re-propagate it).

"bullshit baffles brains"

stop thinking about it. run your knots, and turn off that channel. they are trying to distract you from your job.

Oh don't worry, I do when I've done enough of calling out the B.S. for one day. 🧡

Everyone running a node has control over their mempool. Some node runner wants to see the whole picture and all available valid transactions so they can clearly see what's going on in the network, some wants to filter some transactions out and see the network only partly and some want to see only specific transactions in the mempool.

One noteworthy thing I noticed when playing with the filters was that, we have to download twice the transactions we try to filter. Once when we see them first time and reject it and second time when they enter in the block. It's not that bad but if one wants to optimize bandwidth usage they should not use any filters.

Have you looked into the cache settings?

I didn't know that there's a way to use mempool cache to also include filtered transactions, but I guess that makes sense if using filters. Thanks for the notice.