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
  3. MacroMiner (MPoH & Web3Anthill)

Full Node

PreviousArchive NodeNextLight Node

Last updated 1 year ago

The minimum hardware requirements that users who want to undertake the task of Full Node must provide:

Starting from the moment it joins the Full Node system, the reward of the Full Node is calculated based on multiple parameters, just like in the case of an Archive Node. A Full Node receives its reward from a total of 50.000 W3B miner pool that is renewed every day at 00:00 (UTC).

The Full Node can track its share of the reward from the miner pool updated hourly, but the reward can only be transferred to its wallet at 00:00 (UTC). A Full Node can earn a maximum of 100 W3B within a 24-hour period.

The amount of W3B that will be reflected in a Full Node's balance for each hour of hardware contribution is calculated according to the following formula:

40.000/24xTN40.000 / 24 x TN40.000/24xTN

TN : Total Nodes

(10.000/(TMPx(TA/(TNx24))))xMPx(A/24)( 10.000 / ( TMP x ( TA / ( TN x 24 )))) x MP x ( A / 24 )(10.000/(TMPx(TA/(TNx24))))xMPx(A/24)
  • MP : Web3 Points

  • TMP : Total Web3 Point in the pool

  • TA : Total active hours of all Archive Nodes for the reward day

  • TN : Total Nodes

  • A : Active hours during the day

For Instance;

Starting from the moment Full Node joins the system, the reward of the Full Node is calculated based on multiple parameters just like in the case of the Archive Node, and it receives its reward from a total of 50.000 W3B miner pool that is renewed every day at 00:00 (UTC).

The Full Node can track its share of the reward from the miner pool, which is updated hourly, but the reward can only be transferred to its wallet at 00:00 (UTC). A Full Node can earn a maximum of 100 W3B within 24 hours.

The amount of W3B that will be reflected in a Full Node's balance for each hour of hardware contribution is calculated according to the following formula:

(10.000/(600.000x(500.000/(25.000x24))))x5x(24/24)=0,1W3B( 10.000 / ( 600.000 x ( 500.000 / ( 25.000 x 24 )))) x 5 x ( 24 / 24 ) = 0,1 W3B(10.000/(600.000x(500.000/(25.000x24))))x5x(24/24)=0,1W3B

and a total of 2.76 W3B can be withdrawn to the wallet at 00:00 (UTC).

The calculated reward in W3B is hypothetical. The number of nodes in the pool, active hours, and MP owned can increase or decrease the reward based on circumstances.