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

Double Spending

PreviousEclipse AttackNextNative Token

Last updated 1 year ago

Double-spending is a type of attack where the attacker makes the same transaction operation to be performed more than once.

The attacker aims to make multiple expenses by sending the same signed transaction back to the network while the transaction is still in the process of being recorded in blocks.

The same transaction sent more than once by the attacker is subjected to the "Pre-verified Sign Is Valid" stage by Web3Anthill. Unsigned transactions are denied directly, and nodes are prevented from performing the same transaction a second time.