> For the complete documentation index, see [llms.txt](https://rig-rooms.gitbook.io/rig-rooms-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rig-rooms.gitbook.io/rig-rooms-docs/play-and-earn/optimizing-your-mining-room.md).

# Optimizing Your Mining Room

Your **mining room** (bay) is the grid where rigs live. Optimizing rooms is how serious players scale hash rate in this **crypto mining simulator** and **Solana play-to-earn game**.

## Room tiers & unlocks

| Bay            | Grid  | Unlock cost |
| -------------- | ----- | ----------- |
| Starter Bay    | 6×6   | Free        |
| Growth Bay     | 8×8   | 20,000 SP   |
| Workshop Bay   | 10×10 | 30,000 SP   |
| Industrial Bay | 12×12 | 60,000 SP   |
| Premium Lab    | 14×14 | 100,000 SP  |

Larger grids hold more frames. Higher room tiers also carry small **room hash bonuses** (roughly +0% on Starter up to about +8% on the top bay).

## Optimization checklist

### 1. Maximize operational racks

Empty frames and broken builds waste space. Every cell should either be empty on purpose or hosting an **operational** rig.

### 2. Balance power before GPU count

Stacking GPUs without PSU headroom zeros the rack. Always check watt draw vs PSU rating when optimizing a room.

### 3. Fill support slots

Fans and cables are not cosmetics — missing either makes the rig non-operational. Match rarity upward when you can afford it for the bonus bands.

### 4. Protect condition

A room full of Hot / Fried GPUs underperforms a smaller Mint farm. Schedule repairs as part of room ops, especially after long accrual sessions.

### 5. Expand when ROI is clear

Unlock the next bay when Starter is saturated with solid rigs — not before you understand [How to Earn $COMPUTE](/rig-rooms-docs/play-and-earn/how-to-earn-compute.md). SP spent on rooms also counts toward the **500 SP** full-earning gate.

### 6. Use consumables surgically

Consumables are 24h boosts (one per rig). Pop them when you want a temporary hashrate spike — for example around competitive pushes or after a big GPU upgrade — not as a substitute for base kit.

## Room skins & presentation

Cosmetic room skins change how your bay looks (Arena / profile vibes) without replacing the mechanical checklist above. See the site [skins docs](https://rigrooms.com/docs/skins) for catalog details.

## Competitive angle

Higher rooms → more racks → more MH/s → larger share of the reward pool and a higher [leaderboard](https://rigrooms.com/leaderboard) rank. In a **Solana play-to-earn game**, that share is the core progression flywheel — especially when $COMPUTE is treated by the market as a **low market cap P2E coin** with flexible upside and real downside.

## Related reading

* [Building Mining Rigs](/rig-rooms-docs/play-and-earn/building-mining-rigs.md)
* [GPU Tier Rarities](/rig-rooms-docs/game-systems/gpu-tier-rarities.md)
* [Packs, SP & Progression](/rig-rooms-docs/game-systems/packs-sp-and-progression.md)
* Site: [Rooms & Bays](https://rigrooms.com/guidebook/rooms)


---

# 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://rig-rooms.gitbook.io/rig-rooms-docs/play-and-earn/optimizing-your-mining-room.md?ask=<question>&goal=<endgoal>
```

`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.