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?
There is currently a fee bug on Monero, that the wallet doesn’t automatically bump the fee when there is a backlog. This fee bug is causing sync issues with many wallets. Only if you’re self-hosting a node or using unpopular public ones are you ok. The bug has already been solved with Anonero.io, and other wallets will be rolling out fixes shortly.
There are rumors that Nostr’s creator is behind a spam attack. Simplified Privacy addresses this and has a ready working solution: https://simplifiedprivacy.com/monero-attack-nostr/
Tor Browser Onion: http://privacypkybrxebcjicfhgwsb3coatqechwnc5xow4udxwa6jemylmyd.onion/monero-attack-nostr/