Web3 Coin
  • Welcome to Web3 Coin
  • Overview
    • 💡Our Vision
    • ✨Team
  • WhitePaper
    • Terminology
    • Abstract
    • Introduction
    • Vision
    • Overview
      • Current Problems of Existing Blockchain Networks
      • Web3Coin Solution
    • Web3Chain
      • An Overview for Web3Chain
      • Web3Anthill
      • EVM to MVM
      • Web3Chain Consensus Mechanism: PoW
      • Transaction Check Per Second (TCPS)
    • Proof of Web3 Consensus Mechanism
      • Web3Miner (WPoS & Web3Anthill)
        • Fees and Rewards
      • MacroMiner (MPoH & Web3Anthill)
        • Archive Node
        • Full Node
        • Light Node
      • MicroMiner (MPoSW & Web3Anthill)
    • Scalability
      • Blockchain Network Structure
      • Energy Consumption
    • Smart Contract
      • Smart Contract Compatibility
      • Smart Contract Fees
    • Transaction
      • Transaction Fees
    • Attack Vectors & Security
      • Transaction Denial
      • Eclipse Attack
      • Double Spending
    • Native Token
      • Web3 Coin (W3B)
      • Token Burning
        • Transaction Fee Burning
        • Constant Burning
      • Pool Distribution
    • Experimental Results
    • Information
    • Audit
    • Solution and Conclusion
      • Focused on 'Human'
    • References
    • Disclaimer
  • Fundamentals
    • 🌎Tokenomics
      • Chart
    • 🗺️ROADMAP
  • FAQ
    • ❓What is Web3Coin?
    • ⭐Good to Know
    • 💾Web3Anthill
  • Products
    • Web3Chain
    • Web3 Airdrop
    • Web3 Coin (W3B)
    • Web3Dex
    • Web3Exchange
    • Web3Explorer
    • Web3Launchpad
    • Web3NFT
Powered by GitBook
On this page
  1. WhitePaper
  2. Attack Vectors & Security

Eclipse Attack

PreviousTransaction DenialNextDouble Spending

Last updated 1 year ago

Eclipse attack is an attack method used in architectures where the network shares the workload with the nodes.

The purpose of this attack is to inactivate a particular node connection by providing more workload than its capacity and to seize the node connections.

For example, if a node has 8 connections and these connections accept up to 128 transactions, the attacker creates an overload of connections by sending more than 128 transactions to the focused node. As this overload will cause problems in the communication of all 8 connections with each other, the attacker exploits the vulnerability of the connections and takes control of the chain structure view.

Thanks to Web3Anthill, any artificial and natural traffic that can be experienced in the Web3Chain network is suspended.

If (n+k) transactions arrive in the network above the node capacity, it suspends (n+k) transactions in packages in the form of n*(Node Capacity), so as not to exceed the node capacity.

Thus, neither the large number of transactions executed by the attacker nor the large number of transactions occurring naturally can cause an overcapacity load on the nodes.