# VIP Amplify

### **Overview**

The VIP Amplify system introduces an innovative, non-passive staking mechanism designed to enhance miner performance without compromising fairness or token integrity. Unlike traditional staking systems that generate yield through inflationary minting, HCLD’s VIP Amplify model focuses solely on improving active mining output through a performance multiplier applied to verified compute results.\
**Staked tokens must be locked for a minimum of 14 days** to qualify for VIP benefits; this lock period aligns incentives, reduces immediate sell pressure, and ensures that multiplier privileges reflect sustained network commitment.

This approach transforms staking from a passive wealth mechanism into an *active participation enhancer*, rewarding miners who commit to network stability and long-term alignment. Staked tokens do not earn rewards by themselves; rather, they unlock enhanced compute efficiency and GPU slot privileges that scale performance rewards in proportion to effort.

#### **Philosophy of Fair Staking**

HCLD’s staking model was built around the principle of **“Proof of Commitment, not Proof of Capital.”**\
By decoupling staking from passive income and requiring a **14-day minimum lock**, HashCloud ensures that all network rewards remain performance-driven. Staking simply amplifies the miner’s effectiveness within verifiable computation tasks, ensuring decentralization and fair participation at every tier. This 14-day commitment discourages speculative, short-term staking and instead promotes operational loyalty miners who genuinely contribute computational value over time receive the amplified benefits.

#### **VIP Tiers & Locking Rules**

HCLD introduces four staking tiers (VIP Levels). Each tier provides a proportional multiplier to verified compute results and requires that the staked HCLD be **locked for at least 14 days** to activate multipliers and GPU slot allowances.

| **Tier**       | **Stake (**HCLD**)** | **Multiplier** | **Lock Requirement**          |
| -------------- | ------------------------------ | -------------- | ----------------------------- |
| VIP1 (Bronze)  | 10,000                         | ×1.25          | 14 days locked                |
| VIP2 (Silver)  | 25,000                         | ×1.50          | 14 days locked                |
| VIP3 (Gold)    | 50,000                         | ×1.75          | 14 days locked                |
| VIP4 (Diamond) | 100,000                        | ×2.00          | 14 days locked + verification |

**Activation rule:** multipliers and GPU slot increases only apply after the stake has been locked for 14 continuous days. Stakes in an unlocking state do not confer multiplier benefits; any new stake must complete the 14-day period before being counted.

{% hint style="info" %}
Staking increases reward output but does not mint tokens. Multipliers apply to normalized performance results.
{% endhint %}

#### **Key Properties (including duration behavior)**

* **No Passive Yield:** Tokens staked in the VIP system do not accrue standalone rewards.
* **14-Day Lock:** All staking tiers require a **minimum 14-day lock** before multiplier and GPU slot privileges become active.
* **Unstake & Cooldown:** After initiating an unstake, a cooldown (e.g., 7 days) may apply before tokens become withdrawable; during cooldown, multiplier benefits are revoked.
* **Early Unstake Penalty (optional):** To discourage repeated short-term staking, a slashing or forfeiture of a small percentage of accrued multiplier benefit may apply for unstaking before 14 days (policy configurable by governance).
* **Compute-Linked Multipliers:** Amplification only applies to normalized compute results, preserving emission stability.
* **Non-Inflationary Design:** No new tokens are minted through staking; amplified rewards are drawn from the existing daily emission pool.
* **Hardware-Aware Limits:** Multipliers are bounded by GPU verification to prevent abuse via low-end hardware paired with high-tier staking.

These rules together ensure economic balance: the 14-day lock ties multiplier access to genuine commitment, preventing capital-only actors from exploiting short windows of advantage.

### Reward Formula

#### **Reward Formula (clarified)**

The VIP Amplify reward mechanism mathematically integrates the miner’s compute output, efficiency, and staking tier into a unified expression **applicable only after the 14-day lock period has completed**:

$$
\text{reward} = \left(\frac{\text{matrixSize}^2}{\text{elapsedTime}}\right) \times \text{vipMultiplier} \times \text{baseReward}
$$

#### **Concept Explanation**

* **matrixSize² / elapsedTime** — Represents normalized compute throughput.
* **vipMultiplier** — Enhances miner output proportional to their staking tier.
* **baseReward** — The epoch’s emission constant defining total available rewards.

Code-style:

```
if stake.lockedDays >= 14:
    reward = (matrixSize^2 / elapsedTime) * vipMultiplier * baseReward
else:
    reward = (matrixSize^2 / elapsedTime) * baseReward
```

**Note:** Stakes that have not met the 14-day requirement receive normal (non-amplified) rewards until the lock completes. If a miner begins unstake/cooldown, the multiplier is immediately suspended for subsequent epochs.

#### **Network Impact & Rationale**

Requiring a 14-day lock creates multiple positive effects:

* **Reduces short-term sell pressure**, improving token stability.
* **Aligns incentives** between long-term contributors and the protocol.
* **Discourages abuse** via repeated stake/unstake loops.
* **Provides predictable governance eligibility** since long-term stakers are demonstrably committed.

Example: a miner who stakes 25,000 HCLD (VIP2) will only see the ×1.5 multiplier applied to their normalized compute score after the stake has been locked for 14 days. If they unstake during the first 14 days, they forfeit multiplier access and may trigger the early-unstake penalty if such policy is enabled.


---

# Agent Instructions: 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:

```
GET https://docs.hashcloud.sh/vip-amplify.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.