Are we able to produce a couple of blocks at similar top on regtest for checking out very similar to https://forkmonitor.information/stale/btc/781277?
I attempted working 3 regtest nodes on other ports, maxmempool as 5,7 and 10, two of them had onion addresses and all had been hooked up. I created some huge transactions and plenty of small transactions to fill the mempool. In the end attempted to create block with generatetoaddress on a couple of nodes concurrently. On the other hand there is not any latency and the whole lot updates temporarily.
AJ had shared that mempool inconsistency impacts compact block relay and it might be probably the most causes for common stale blocks. There are a number of issues which may be concerned like complete rbf, patch to dam inscriptions, mempool limits and so on. On the other hand I need to see if mempools of a few nodes within the networks are complete as a result of the use of default dimension and others are not, would this build up the chance of stale blocks?
That is mempool chart for closing 2 years with stale blocks marked on best. There might be extra causes and whole mempools appears to be considered one of them:
