Wave

mert | helius.dev - Oct 21, 2025 · 4:57 PM UTC https://x.com/0xMert_/status/1980679910558437508

I will try this once

xmr and certain btc folks,

there are devs writing privacy code in literal jail right now

trump is president, we have a window to finally make progress and make privacy normal again all over crypto

when zcash succeeds, things like monero also succeed, all privacy succeeds, and all of crypto's cypherpunk origins succeed

there will be plenty of time to in-fight

until the current administration is not favorable anymore, let's full send privacy systems as much as humanly possible before it's too late

we need to work together to make as much progress as possible

you can simply buy multiple coins

cross-posted from: https://monero.town/post/6680060

P2Pool v4.10 speed up the whole Monero network

If you're still mining on a normal pool like in the old days, your computer has to wait much longer to receive its work from the internet. With p2pool, it takes a fraction of the time of regular centralized pools!

How it will work with P2Pool broadcasts:

• 1. A pool or a solo miner finds a block, then submits it to their Monero node
• 2. Monero node notifies its connected P2Pool node of a new block (instantly)
• 3. P2Pool network spreads this block across all peers, spending only 2-3ms on each hop
• 4. All P2Pool peers submit this block to their respective Monero nodes
• 5. These Monero nodes verify this block in parallel - this is where the time saving comes from

As soon as enough P2Pool miners update to v4.10 or newer, block propagation times in the whole Monero network will reduce significantly.

➡️ Reddit

./monerod --zmq-pub tcp://127.0.0.1:18083 --out-peers 32 --in-peers 64 --add-priority-node=p2pmd.xmrvsbeast.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --enforce-dns-checkpointing --enable-dns-blocklist

P2Pool v4.10 speed up the whole Monero network

If you're still mining on a normal pool like in the old days, your computer has to wait much longer to receive its work from the internet. With p2pool, it takes a fraction of the time of regular centralized pools!

How it will work with P2Pool broadcasts:

• 1. A pool or a solo miner finds a block, then submits it to their Monero node
• 2. Monero node notifies its connected P2Pool node of a new block (instantly)
• 3. P2Pool network spreads this block across all peers, spending only 2-3ms on each hop
• 4. All P2Pool peers submit this block to their respective Monero nodes
• 5. These Monero nodes verify this block in parallel - this is where the time saving comes from

As soon as enough P2Pool miners update to v4.10 or newer, block propagation times in the whole Monero network will reduce significantly.

➡️ Reddit

./monerod --zmq-pub tcp://127.0.0.1:18083 --out-peers 32 --in-peers 64 --add-priority-node=p2pmd.xmrvsbeast.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --enforce-dns-checkpointing --enable-dns-blocklist

github presentation of the FCMP++ audits w.r.t. the modules in the codebase

@BitMEXResearch/status/1955254320305217726

Monero Re-org & Qubic

It seems like there may have been a delibrate 6 block re-org on Monero $XMR from Qubic mining. The target time is 2 minutes, therefore the re-org length is quite small. However, it is not clear if there was a double spend attack or if this was just selfish mining, i.e. trying to earn more of the block rewards. It seems for now that there is no evidence this was a double spend attack.

Qubic did seem to have around 20% of the Monero hashrate for a while and they may have sold some coins for USD, to rent hashrate to temporally push the hashrate up to over 30%. Qubic has significantly less than 51% of the hashrate, but perhaps it has just above the 33% theoretical threshold, where selfish mining is profitable (Assuming the coin price does not crash). It is not clear what the Qubic objective is here, but they do have a token $QUBIC and they may want to try and push up the price of it. Other than that, the endgame is unclear, but the "attack" from Qubic may not be sustainable

We have heard no reports of a double spend attack @krakenfx @bitfinex @MEXC_Official Any news on this? As for exchanges who take Monero deposits, it might be a good policy to increase the number of confs required for a deposit.

@/tuxpizza/status/1955191610410401816#m

Qubic never actually hit 51% btw. Don't fall for it.

However they do have a large enough hashrate to perform multi-block re-orgs with their selfish mining strategy.

They disabled API hashrate reporting so that they could lie about it.

Keep mining and ignore the noise.

qubic.org, a miner with very high computing power, has made no secret of wanting to ignore legitimate blocks from other pools.

Would a generally legitimate reaction of sincere miners be to ignore the blocks of this belligerent miner?

It already looks to me as if the operators of some mining pools are taking countermeasures behind the scenes.

The administrator of supportxmr.com has a lot of experience and is trustworthy and certainly knows how to take countermeasures.

Perhaps an emergency feed for mining pool operators could be introduced, in which only recommended countermeasures for pool operators are communicated.

An option to adopt an emergency block list, which is switched off by default, could be introduced. The recommendation for pool operators and node operators could be to activate this option when starting the Monero software. This list would have to be distributed by experienced pool operators or members of the Monero core team.

We already have a block list, which MRL has recommended to activate. This could be extended by IP addresses from qubic.org.

• https://files.catbox.moe/1zyri6.jpg
• https://miningpoolstats.stream/monero

This change surprised me. Unstoppableswap is also recommended and linked in other places, e.g. on monerica.com

eigenwallet is an ambitious community effort to build the Monero wallet for the future.

Activate the blocklist in the Monero GUI wallet or Monero node.

It reduces the connections to suspicious, potentially useless or even counterproductive nodes in the Monero network. It is not absolutely necessary that you make this setting, but it would support the entire Monero network. Thank you.

Monero GUI wallet

If your run your own local node through the GUI wallet, go to Settings. In the “Daemon startup flags” box, input “–ban-list ”. Then click the orange “Stop daemon” button. It will take a few seconds for the daemon to shut down. Then click the orange “Start daemon” button. If you use a remote node, whoever operates the remote node will decide if the ban list is enabled.

✋ node operators enable a ban list

The Monero Research Lab (MRL) has decided to recommend that all Monero node operators enable a ban list

https://github.com/Boog900/monero-ban-list/blob/main/ban_list.txt

Download the ban list and:

./monerod --ban-list

🧐 https://gist.github.com/Rucknium/76edd249c363b9ecf2517db4fab42e88

Clover vs Dandelion++ | Network-Layer Privacy in Monero NOTE: SEE THIS IN MONEROKON IN JUNE 21 (06/21/2025)!

I've been reading about Clover and Dandelion++, two techniques aimed at improving privacy on the network layer specifically, hiding the origin IP of a transaction in systems like Monero.

Here’s a quick comparison and breakdown:

🌼 Dandelion++

How it works:

Uses a two-phase propagation system:

Stem phase: The transaction is passed through a few nodes in a linear, random path.

Fluff phase: It’s then broadcast normally (flooded).

Privacy benefits:

Helps hide the source IP by making it harder for attackers to pinpoint the origin based on initial propagation.

Works well against local or partial adversaries (those controlling a few nodes or monitoring part of the network).

Already implemented in Monero.

Limitations:

Vulnerable to global adversaries (e.g., an attacker that can monitor large parts of the internet).

Susceptible to timing analysis and some advanced correlation attacks.

🍀 Clover

How it works:

Proposes a more advanced, probabilistic routing system.

Introduces random delays, mixing, and adaptive path selection using buffers and stochastic rules.

Makes the traffic pattern statistically indistinguishable from honest noise.

Privacy benefits:

Much stronger protection against global passive adversaries.

Defends against timing attacks and traffic analysis far better than Dandelion++.

Higher entropy in transaction routing paths.

Limitations:

More complex to implement.

Likely introduces higher latency due to delays and buffering.

Not yet implemented in Monero—still a research prototype (see more in MoneroKon).

Conclusion: Dandelion++ is a practical and effective step forward for Monero’s network privacy, but Clover shows promise for the future, especially if we want to defend against more powerful, surveillance-level attackers. It’s a trade-off between deployment complexity and stronger anonymity guarantees.

Reddit

Zen-5, Shimada Peak, Ryzen Threadripper 9000, AMD 9995WX 96 core

Hashrate of supportxmr.com went from 1.25 GH/s to 2.6 GH/s in just one week.