....
Bitcoin's halving is around the corner and there is a concern that this will create mempool transaction problems on Bitcoin's network on a larger scale then previously witnessed
...
Why is the halving expected to increase Bitcoin traffic / mempool size?
...
Some predict that after halving and no price increase some miners could turn their machines off and hashrate could drop because of that more or less significantly. That would be ok but bitcoin difficulty adjusts every 2016 blocks so miners who are still mining would have more work to be done to solve a block than it should be for a hashrate like that for quite a long time (normally 2016 is 2 weeks and with lower hashrate this timeframe grows). This would mean larger time between blocks which in its turn would mean more transactions waiting in line to get into the block which could lead for confirmation problems which could decrease the price which will make it unprofitable for more miners which will turn their miners off and there you go - "death spiral".
I've been thinking about this problem too recently. Actual size usage of blocks is somewhere ~800kb, which means we could see throughput of ~400kb per block for up to a month after the halving. The reason for this is pretty simple, if the profitability of the network drops 50% in one moment, 50% of the miners should drop off. Also, the difficulty only readjusts every 2 weeks, which will take 4 weeks with 50% of the miners. If we're using ~800kb in transactions, doesn't that mean we'll start added 400kb to the blocklog... every 10 minutes? What happens after 30 days of that? A 1.72GB mempool
It's worth noting, miners didn't drop off last time. But the climate is completely different now. I have no idea what happens next, in either case it's sure to be entertaining.
