As we all know, the tx pool is very full - being flooded with thousands of transactions, peaking at over 100,000 tx in the mempool.
However, not only are transactions slow at this bottleneck, but it looks like wallets are unable to sync well.
I found this when trying out a micro transaction on MyMonero wallet, receiving error 504 - historically this error has occurred when too many users were querying the MyMonero scanning service.
As pic related shows, this is happening to GUI wallet, as well as Cake Wallet, so the biggest 3 wallets are affected - is this a side-effect of mempool congestion or - assuming this is an attack not just a significant uptick in XMR fans - is there a concerted attack to block all major wallets from syncing with the XMR blockchain?
Side Questions:
Does anyone running a full node have an insight, how is your node getting on and are you able to keep up?
How could a flooded mempool affect wallet sync, is there a direct causation?
@blake @monero I have monero-wallet-rpc connected to a public node, and it has become completely unusable. I always had issues with it (why a service that manages a couple of keys needs hundreds MBs of RAM?), but today it simply doesn't respond to most RPC calls.