Eclipse Attack
Definition
An eclipse attack isolates a blockchain node from the legitimate network, surrounding it with attacker-controlled nodes. The victim receives only attacker-filtered information, enabling targeted double-spends or mining manipulation against that node.
Technical Explanation
Attack method: flood target's peer connections with attacker nodes, monopolizing network view. Victim believes attacker's chain is the valid chain. Enables double-spending against the victim or wasting their mining on invalid chains.
Defenses: diverse peer selection, preferring long-lived connections, monitoring peer diversity, using multiple network interfaces, and connecting to known good nodes. Post-quantum cryptography doesn't directly address eclipse attacks—network topology does.
SynX Relevance
SynX nodes implement eclipse resistance through: diverse peer selection algorithms, connection slot management, peer reputation tracking, and bootstrap node diversity. While SPHINCS+ doesn't prevent eclipse attacks, secure peer authentication ensures attackers can't impersonate legitimate nodes.
Frequently Asked Questions
- How do I know if I'm eclipsed?
- Monitor multiple information sources (block explorers, different nodes). Unusual behavior indicates potential isolation.
- Does quantum resistance prevent eclipse attacks?
- No—eclipse attacks are networking issues. However, quantum-resistant authentication helps verify peer identity.
- Who's at risk?
- Nodes accepting payments (exchanges, merchants). Validators should ensure diverse connections.
Network-aware node protection. Run a connected SynX node