As a person who runs my own full node, I can tell you that my wallet syncs fine, so it might be something to do with the public nodes that cake and others are using. And if you use a small node, you might get transactions through. I sent a transaction earlier this morning with the mempool full like it is now and while it took longer to get its first confirmation it still didn't take all that long.

I'm running a full node and it works fine

I am running a full node with the Official Monero GUI and also mining. I have not broken that connection in several days since I own a computer that doesn't need a reboot several times a day, so I haven't noticed any problems yet. Will update thread if I notice anything after power restart.

As a point of reference, when I first sync a full node after installing GUI or CLI program, it's not unusual at all for the first sync to take three or four days. I've done it several times.

Another full node selfhoster here. I did not notice any problems for me (except some transactions taking some time for confirmations), but I tried to onboard someone earlier and wondered why his freshly installed cake wallet acted weird. You might be onto something about official/public full nodes being overwhelmed or something.

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/

While still usable for me I can definitely feel the weight of these extra transactions. At this point I would say Monero if not ready for something like 1 million tx per day.

I would think the dynamic block size mechanism would have kicked in by now since there appears to be backlog forming.

@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.

We never had 100,000 tx in the mempool.

Working Monero Nodes.

We stand together to fight the attack: https://simplifiedprivacy.com/working-monero-nodes/

Post your's here, or contact us via any method on the site. We'll add it

I got few backlogs using it this week but bitcoin were slower lmao

I just restarted my node, got this message in startup over there:

2024-03-09 04:04:20.475 W Unable to send transaction(s), no available connections

Then it went on to give this message:

2024-03-09 04:04:22.880 I You are now synchronized with the network. You may now start monero-wallet-cli.