18
submitted 6 months ago* (last edited 6 months ago) by tusker@monero.town to c/monero@monero.town

This may be a new attack tactic. By flooding the TX pool with large transactions they are trying to artificially jack up TX costs since the spam attack did not work.

As usual Monero will learn from this and improve. ๐Ÿ‘ It is best to go through all this while Monero is still not a top world currency.

you are viewing a single comment's thread
view the rest of the comments
[-] jet@hackertalks.com 4 points 6 months ago

Wow. Is there an analysis or write-up on these attacks?

[-] blake@monero.town 2 points 6 months ago

@Rucknium taking the lead on analysis here.

check the paper he wrote re: the first wave on his git here

https://github.com/Rucknium/misc-research/blob/main/Monero-Black-Marble-Flood/pdf/monero-black-marble-flood.pdf

then on this wave - fat input transactions filling blocks on XMR chain :

Thanks for mentioning my paper. It analyzed the privacy impact of an adversary owning many outputs. The transactions that are congesting the mempool/txpool now have many inputs. There may be a privacy impact of large many-input txs, but I don't have a clear idea of what it would be, and it's not the same as a standard black marble flood.

this post was submitted on 02 May 2024
18 points (87.5% liked)

Monero

1666 readers
27 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