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. Web3Chain

Web3Anthill

PreviousAn Overview for Web3ChainNextEVM to MVM

Last updated 1 year ago

Web3Anthill technology has been developed for the hybrid mining system in Web3Chain to synchronize at high speed and use the resources of the platform-independent hardware most efficiently.

Inspired by nature, Web3Anthill literally means ‘anthill’. The working method of ants – who can instinctively recognize the most advanced and optimal scenarios – has been adopted in terms of workforce allocation and efficiency, and the structure of the anthill has been internalized in terms of the created work path. Web3Anthill is a software library written in Java. It acts as a platform-independent integrated accelerator and a smart processing router.

Web3Anthill scans the device at the hardware level and acts according to the configuration and available resources of the hardware. It also creates the path structure of the network for the synchronization between nodes.

Web3Anthill allows the blockchain network to be more scalable. It minimizes confirmation times of transactions and instantly meets millions of transactions on Web3Chain. It provides pre-verification and confirmation of the transactions because of seamless inter-node synchronization.

Web3Anthill also performs different tasks depending on the role and node type of the miners that make up the system.

Web3Miner monitors the entire network traffic and routes the traffic according to the incoming transactions.

MacroMiner ensures that the hardware required for Web3Chain is analyzed, the necessary software installations are completed and the most up-to-date software is used.

MicroMiner monitors node density and ping time, and provides communication and fast synchronization, and integration of all transactions into the blockchain network in the shortest way.

Web3Anthill divides incoming queries to the blockchain into transactions and more.

To ensure the verification and confirmation of hundreds of thousands of transactions in the same second, all incoming transactions are pre-verified by Web3Anthill. These are then sent to Web3Miner, MacroMiner, and MicroMiners – that are part of the hybrid mining system –, for block generation by using smart load optimization. Verified transactions, if confirmed, are processed into blocks, shared with the entire network, and synchronized by Web3 and Macro nodes.

Incoming Smart Contracts, on the other hand, are transmitted directly to TxPool, without any waiting process, they take their place in the generated block and are synchronized.