> 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/economy/currencies.md).

# $COMPUTE & Store Points

Rig Rooms runs on two currencies: **$COMPUTE** (on-chain Solana token) and **SP / Store Points** (in-game store unit). Understanding both is essential in this **crypto mining simulator** and **Solana play-to-earn game**.

## $COMPUTE

| Fact      | Detail                                                             |
| --------- | ------------------------------------------------------------------ |
| Network   | Solana (SPL)                                                       |
| Role      | Mining rewards, marketplace, repairs, store conversion, hold gates |
| Mint (CA) | `Hvf6MeVBnUqQZBtMXkabRzfuQae1Tx3YQSvf3Lrkpump`                     |

Players often call $COMPUTE a **low market cap P2E coin** — that describes category and market size, not guaranteed returns.

### Earn $COMPUTE

* Operational mining hash-rate share ([How to Earn $COMPUTE](/rig-rooms-docs/play-and-earn/how-to-earn-compute.md))

### Spend / sink $COMPUTE

* Convert to SP in the Store (live rate)
* Marketplace purchases + **5%** sale fee → burn wallet
* Repairs (**50% burn / 50% platform**)
* Rig Wars entry (at live SP face rate)

Verify: [Solscan](https://solscan.io/token/Hvf6MeVBnUqQZBtMXkabRzfuQae1Tx3YQSvf3Lrkpump) · [DexScreener](https://dexscreener.com/solana/Hvf6MeVBnUqQZBtMXkabRzfuQae1Tx3YQSvf3Lrkpump) · [Jupiter](https://jup.ag/swap/SOL-Hvf6MeVBnUqQZBtMXkabRzfuQae1Tx3YQSvf3Lrkpump)

## Store Points (SP)

| Fact          | Detail                                              |
| ------------- | --------------------------------------------------- |
| Design anchor | About **1 SP ≈ $0.01**                              |
| Used for      | Packs, room unlocks, some store items / consumables |

### How to get SP

* Buy bundles with $COMPUTE in Store
* Convert mined $COMPUTE at the live rate
* Burn eligible **Mint** spare items / unassigned pack drops for SP
* Promo codes (when offered)
* Token-holder hourly SP ([Token-Holder Rewards](/rig-rooms-docs/economy/token-holder-rewards.md))

**Not burnable for SP:** Clean, Dusty, Hot, or Fried gear.

### Example SP bundles (bonus on first-buy style packs)

500 (0%) · 1,050 (3%) · 1,600 (5%) · 2,800 (8%) · 5,900 (12%) · 12,000 (18%) · 25,000 (22%) — check Store for live offers.

## Live conversion rate

$COMPUTE → SP uses a **live** Store rate (TWAP / market-cap ladder). Do not hardcode a permanent COMPUTE-per-SP number. Mining reward allocation is separate from the Store ladder.

## Related

* [Play](https://rigrooms.com/play/login)
* [Marketplace & $COMPUTE Token](/rig-rooms-docs/game-systems/marketplace-and-compute-token.md)
* [Packs, SP & Progression](/rig-rooms-docs/game-systems/packs-sp-and-progression.md)
* Site guide: [Currencies](https://rigrooms.com/guidebook/currencies)


---

# 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/economy/currencies.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.
