[mempool.bitmixlist.org] Announcing the community Mempool.space node

[logfiles]

I am also facing the same thing right now, What I found about the NGINX 404 Error is that we can successfully send the request to the website but the specific file cannot be found on the server. Even this is due to a misconfiguration of the server.

Let's wait for the NotATether reply :")

Edited: Maybe this is the reason?

I am investigating a configuration error in the shared backend server.

Thank you for your patience.

The tool now works though the data seems to be a little off. Earlier on i thought the mempool was nearly empty but in reality it is not thanks to what Cricktor pointed out. Maybe it could be related to the error NotATether talked about yesterday.

[NotATether]

There was an error guys, unfortunately while I was writing policies for SELinux, I accidentally locked myself out of SSH and had to recover access with rescue mode. Restarting the box caused the 404s and it took quite a while to identify the root cause and revert it.

Everything is fine now.

The mempool looking empty is not an error though, it is simply showing what the default node actually sees, which means that transactions which have been dropped by default nodes will not show up here.

Mempool shows all transactions by default and doesn't evict any.

[nc50lc]

The mempool looking empty is not an error though, it is simply showing what the default node actually sees, which means that transactions which have been dropped by default nodes will not show up here.

Maybe higher maxmempool is a good idea since it's a Blockexplorer nonetheless.
About 2x or 3x the default, maxmempool=1200?

Not all nodes use the default so sooner or later when the average size goes lower,
those dropped transactions will eventually get propagated again as long as its not past their mempoolexpiry.
In this regard, it's more desirable for a blockexplorer to keep those transactions than follow the default behavior.

[NotATether]

Maybe higher maxmempool is a good idea since it's a Blockexplorer nonetheless.
About 2x or 3x the default, maxmempool=1200?

Not all nodes use the default so sooner or later when the average size goes lower,
those dropped transactions will eventually get propagated again as long as its not past their mempoolexpiry.
In this regard, it's more desirable for a blockexplorer to keep those transactions than follow the default behavior.

OK, I have changed the settings on the node to match mempool.space - mempoolexpiry to about 10 years (infinity basically), and now you can see the queue of 200MB worth of transactions in total.

While I don't really like this change, I understand that people prefer seeing the mempool displayed that way, so it doesn't make any sense for me to resist.

[nc50lc]

Maybe higher maxmempool is a good idea since it's a Blockexplorer nonetheless.
About 2x or 3x the default, maxmempool=1200? -snip-

OK, I have changed the settings on the node to match mempool.space - mempoolexpiry to about 10 years (infinity basically), and now you can see the queue of 200MB worth of transactions in total.

Nice.
So I take that its maxmempool (size) is already higher than a standard default node's mempool?
Current mempool.space's code keeps it at 4096MB but only shows up to 300MB in the live websites "memory usage" to match what the standard nodes keep.

[NotATether]

Nice.
So I take that its maxmempool (size) is already higher than a standard default node's mempool?
Current mempool.space's code keeps it at 4096MB but only shows up to 300MB in the live websites "memory usage" to match what the standard nodes keep.

Yes, on this instance, the max mempool is configured to show up to 1GB worth of transactions.

This is how it was from before the maintenance, and it's still the same now.

There are also Liquid and Monero mempools if you're into that sort of thing.