# Desks (Facilities)

In Crypto Lifeline, **Desks (Facilities / Desks)** are the core infrastructure for producing hashpower and deploying workers.

Desks determine how many workers you can host and how your office is structured—forming the foundation of your own “Crypto Lifeline.”

***

### 🧩 Desk Overview

* A desk represents a **virtual office space / hashpower factory layout**. Players can place **Workers** on desks, and those workers generate **Hashrate**.
* A desk itself does **not** generate hashpower, but it sets the **maximum total capacity (Capacity)**—i.e., how much worker “volume” you can place.
* Different desk levels have different **capacity**, **upgrade cooldowns**, and **upgrade costs**.

***

### 🔧 Desk Levels & Attributes

| Level | Name (CN / EN)     | Capacity | Upgrade Cooldown | Upgrade Cost        |
| ----- | ------------------ | -------- | ---------------- | ------------------- |
| Lv1   | **Fresh Desk**     | 50       | 24 hours         | — (default starter) |
| Lv2   | **Futures Desk**   | 300      | 48 hours         | 2,000 CLE           |
| Lv3   | **Quant Desk**     | 800      | 72 hours         | 5,000 CLE           |
| Lv4   | **Whale Desk**     | 2,000    | 5 days           | 12,000 CLE          |
| Lv5   | **Genesis Desk**   | 5,000    | 7 days           | 25,000 CLE          |
| Lv6   | **Enterprise Pod** | 12,000   | 10 days          | 45,000 CLE          |
| Lv7   | **Meta Station**   | 30,000   | 15 days          | 80,000 CLE          |

> **Note:** All values shown above are examples and may be adjusted based on future economic modeling and community consensus.


---

# 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-assets-and-tokens/desks-facilities.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.