# Virtual Mining

Crypto Lifeline uses a **virtual, fully on-chain hashpower mining mechanism**, replacing traditional mining’s reliance on physical hardware and high energy consumption.

Players don’t need to buy mining rigs. Instead, they build an on-chain “hashpower office” by acquiring **Workers** and **Desks**.

* Each **Worker** provides hashpower (**Hashrate**).
* All **Desks** together determine the player’s total capacity and overall hashpower setup.

In Lifeline:

* **Workers = Miners**
* **Desks = Virtual rig slots / rack positions**
* **Lunchboxes = Energy / hashpower upkeep**
* **Office = Hashpower farm**

All hashpower and reward calculations are **100% on-chain, transparent, and verifiable**.

***

### Mining Rewards

Mining rewards are distributed **every block** based on each player’s share of the total network hashpower.

The higher your hashpower, the larger your share, and the more **CLE** you earn.

Let:

* hih\_ihi​ = hashpower of player iii
* HHH = total network hashpower (sum of all players’ hashpower)

  H=∑hiH = \sum h\_iH=∑hi​
* RbR\_bRb​ = SLE produced per block at the current stage

Then player iii’s reward per block is:

Ri=hiH×RbR\_i = \frac{h\_i}{H} \times R\_bRi​=Hhi​​×Rb​

In other words, your output is directly tied to:

* Your own hashpower
* Changes in total network hashpower
* The current block reward (which changes with halving)

***

### Halving Schedule

Crypto Lifeline’s halving mechanism is inspired by **Bitcoin**.

CLE’s **block production** will halve at fixed intervals, causing total issuance to decrease over time and creating a consistent deflationary pressure.


---

# 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://cryptolifeline.gitbook.io/cryptolifeline/game-mechanics/virtual-mining.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.