> For the complete documentation index, see [llms.txt](https://docs.hashcloud.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashcloud.sh/daily-reward-distribution.md). # Daily Reward Distribution ### **Overview** The **Daily Reward Distribution** mechanism defines how HashCloud allocates HCLD tokens to participants based on *verified computational performance*.\ Unlike traditional mining systems that rely on block discovery luck or arbitrary hashing power, HCLD’s reward system is fully deterministic, transparent, and performance-driven. Each miner’s reward is calculated relative to the total verified compute output of the network within a 24-hour emission cycle. This ensures that all contributors regardless of scale receive a fair portion of the daily token emission proportional to their actual computational work. ## Reward Formula The reward distribution mechanism is built on a two-tier formula: 1. **Performance Share Calculation** 2. **Final Reward Computation** Step 1: Compute Reward Share $$ \text{rewardShare} = \frac{\text{minerPerformance}}{\text{totalNetworkPerformance}} $$ This equation determines the relative weight of each miner’s contribution within the total compute output for the day. Step 2: Calculate Final Reward $$ \text{finalReward} = \text{rewardShare} \times \text{vipMultiplier} \times \text{dailyEmission} $$ Where: * **minerPerformance** = The miner’s verified compute score (derived from normalized matrix operations). * **totalNetworkPerformance** = Aggregate of all verified miner scores. * **vipMultiplier** = Staking-based performance amplifier (refer to VIP Amplify Policy). * **dailyEmission** = Total HCLD tokens released per 24-hour cycle. This dual-layer calculation ensures both *fair performance weighting* and *staking incentive alignment* without inflating token supply. ## Distribution Flow The entire reward cycle operates through a transparent, automated process composed of four core stages. {% stepper %} {% step %} ### Collect performance scores All miners’ verified computation results are aggregated by the **Performance Database**.\ Each record includes matrix size, elapsed time, and hardware data, forming a complete performance profile. {% endstep %} {% step %} ### Normalize performance The system normalizes raw compute scores into proportional shares relative to the total network output.\ This ensures that rewards are based purely on contribution ratio, eliminating hardware and time biases. {% endstep %} {% step %} ### Apply VIP multipliers Once normalized, each miner’s performance share is adjusted according to their **VIP multiplier**.\ Higher-tier stakers receive a larger proportional weight, rewarding long-term network commitment and resource dedication. {% endstep %} {% step %} ### Distribute tokens The **Reward Engine** finalizes calculations and transfers HCLD tokens on-chain, ensuring auditable, tamper-proof distributions.\ Every transaction is recorded, providing a verifiable trail of reward allocation for transparency and accountability.. {% endstep %} {% endstepper %} This ensures a transparent and performance-based mining reward mechanism. ### **Example Scenario** Assume a total network performance of **10,000 units** and a miner contributing **1,000 units** with a **VIP2 multiplier (×1.5)**.\ If the daily emission is **100,000** HCLD, the miner’s reward would be: $$\text{Reward Share} = \frac{10,000}{100,000} = 0.10\text{Final Reward} = 0.10 \times 1.5 \times 100,000 = 15,000 \text{ HCLD}$$ | **Variable** | **Value** | **Description** | **Implied from Calculation** | | ------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------- | | Miner's Performance Score | 10,000 (Implied) | The miner's individual performance score (normalized hashrate). | Numerator in Reward Share | | Total Network Performance Score | 100,000 (Implied) | The sum of all active miners' performance scores. | Denominator in Reward Share | | Proportional Reward Share | 0.10 (10%) | The miner's share of the total network compute power. | $$ $\frac{10,000}{100,000}$ $$ | | VIP Multiplier | 1.5 | The staking-based multiplier for the miner (e.g., VIP Tier 2/Silver). | The $$ $\times 1.5$ $$ factor | | Daily Base Reward (Total Pool) | 100,000 HCLD (Implied) | The total number of HCLD tokens available to be distributed to the entire network that day. | The last $$ $\times 100,000$ $$ factor | | Final Reward | 15,000 HCLD | The total tokens the miner earns for that period. | The final result | #### Conclusion This calculation confirms the successful application of the complete reward formula from the HCLD documentation: $$\text{Final Reward} = \left( \frac{\text{Performance Score of Miner}}{\text{Total Network Performance Score}} \right) \times \text{VIP Multiplier} \times \text{Daily Base Reward}$$ ### **System Advantages** * **Transparent Reward Distribution:** Every payout is traceable and mathematically verifiable. * **Performance-Based Fairness:** Rewards are tied to measurable compute work, not random chance. * **Non-Inflationary Model:** Emissions are capped per cycle staking affects distribution, not total supply. * **Daily Sync Cadence:** The 24-hour reward window ensures consistent engagement and predictable returns. This approach transforms mining into a *compute economy* where performance, not luck or centralization, dictates rewards. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hashcloud.sh/daily-reward-distribution.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.