A Monero DNSSEC failure affects checkpoint and blocklist lookups. Tor operators report directory-request floods, while eclipse defenses remain proposed.
1. Monero DNSSEC failure reported after trust-anchor change
October 13, 2026 · Investigate affected lookups
Affects DNS-based checks in monerod.
Issue #11537 reports that Monero v0.18.5.3 fails DNSSEC checks after a change to the root signing key. Nodes can keep syncing while DNS checkpoints, blocklists and update checks fail. A normal chain height therefore does not mean those checks are working. The v0.18.5.4 fix was not yet available.
- Review DNSSEC errors and compare node progress with independent references. Avoid treating a normal chain height as a complete health check.
- The October 23 edition covers the release that repaired this issue.
Sources: DNSSEC failure report
2. Tor relay operators report BEGIN_DIR floods
October 13, 2026 · Investigate abnormal relay load
Affects Public Tor relays.
Operators reported high rates of directory-request streams and resource pressure during a BEGIN_DIR flood. BEGIN_DIR opens a directory stream over a Tor circuit. These reports described observed load, not proof that the preceding Tor release introduced a regression.
- Check relay load and connectivity. Review memory use alongside CPU and circuit activity. Follow upstream mitigation guidance before changing limits that could disrupt legitimate traffic.
Sources: Tor relay operator discussion
3. Monero eclipse-resistance proposal remains open
October 9, 2026 · Research and review
Affects Monero outbound peer selection.
PR #11527 proposes changes intended to make hostile peer concentration harder. It remained open at the briefing date. Tests and simulations can help evaluate a defense, but do not establish that a particular production node is under attack.
- Track the review and any release that includes the patch. Keep experimental branches off production nodes.
Sources: Eclipse-resistance proposal
Monero Research Lab — October 14, 2026
FCMP++ integration proposals were ready for another review after comments had been addressed. Developers were finishing unlock-time handling before seeking audit quotes. The mx25519 library remained an integration blocker despite progress on its license. Multisig work and the second circuit audit continued.
The stressnet was functioning, but participants cautioned that sustained load testing had been limited. Logs from transaction-relay testing still needed review.
The peer-selection discussion compared larger lists with approaches that divide peers into groups. Participants considered stale entries, hostile addresses and the cost of repeatedly shuffling lists. PR #11527 was one proposed defense against Nyx, not an adopted answer to every network attack. More review and experiments were needed.