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. Proof of Web3 Consensus Mechanism

Web3Miner (WPoS & Web3Anthill)

Web3Miner undertakes the Signer task, which creates the unchangeable structure of the blocks, in addition to the task of confirming and archiving the transactions in the incoming block in the form of the chain structure of the network.

The user who wants to be the Web3Miner, the highest level stakeholder of Hybrid Mining, stakes a specified number of W3B's and makes the W3B payment in return for the annual rental amount. Then, a ready-to-use node is provided to the user by Web3time, and this user has full control over the node. The server can be managed through the administration panel and can be disabled at any time to terminate the service.

PreviousProof of Web3 Consensus MechanismNextFees and Rewards

Last updated 1 year ago