this post was submitted on 07 Mar 2024
8 points (75.0% liked)

Monero

1675 readers
25 users here now

This is the lemmy community of Monero (XMR), a secure, private, untraceable currency that is open-source and freely available to all.

GitHub

StackExchange

Twitter

Wallets

Desktop (CLI, GUI)

Desktop (Feather)

Mac & Linux (Cake Wallet)

Web (MyMonero)

Android (Monerujo)

Android (MyMonero)

Android (Cake Wallet) / (Monero.com)

Android (Stack Wallet)

iOS (MyMonero)

iOS (Cake Wallet) / (Monero.com)

iOS (Stack Wallet)

iOS (Edge Wallet)

Instance tags for discoverability:

Monero, XMR, crypto, cryptocurrency

founded 1 year ago
MODERATORS
[email protected]
8
Is Monero currently un-useable? (monero.town)
submitted 8 months ago by [email protected] to c/[email protected]
11 comments fedilink hide all child comments
 

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?

top 11 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 8 months ago* (last edited 8 months ago)

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.

[–] [email protected] 7 points 8 months ago

I'm running a full node and it works fine

[–] [email protected] 6 points 8 months ago

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.

[–] [email protected] 6 points 8 months ago* (last edited 8 months ago)

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.

[–] [email protected] 4 points 8 months ago* (last edited 8 months ago)

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/

[–] [email protected] 3 points 8 months ago* (last edited 8 months ago)

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.

[–] [email protected] 3 points 8 months ago

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

[–] [email protected] 3 points 8 months ago

We never had 100,000 tx in the mempool.

[–] [email protected] 2 points 8 months ago* (last edited 8 months ago)

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

[–] [email protected] 1 points 8 months ago

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

[–] [email protected] 1 points 8 months ago

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.