> For the complete documentation index, see [llms.txt](https://asteroid-shiba.gitbook.io/asteroid-shiba-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asteroid-shiba.gitbook.io/asteroid-shiba-docs/core-gameplay/portfolio.md).

# Your Portfolio

Every valuable asteroid you find **stays with you** and keeps earning — all season long. You're not chasing a single prize; you're building a **mining fleet**.

## How it works

```
Find an asteroid → it joins your portfolio (stays all season)
        ↓
Each asteroid mines ASTRO into its own buffer
        ↓
You Collect (one asteroid, or all at once)
        ↓
Keep the ASTRO, or invest it in Research to earn more
```

* **It compounds.** The longer you play, the more asteroids you hold, and the faster your total daily income grows.
* **The buffer.** Each asteroid fills a limited buffer, then pauses until you **Collect**. Coming back once a day keeps everything mining.

## How many asteroids can earn at once

| Scanner            | Active earning asteroids |
| ------------------ | ------------------------ |
| **Level 0 (free)** | **1**                    |
| **Level 1–10**     | **50**                   |

A **free** account keeps **one** asteroid earning at a time. Find a better one and you choose: replace the one you have, or keep it. Buying any Scanner upgrade opens the full fleet of 50.

You can *find* as many asteroids as you like at any level — instant Discovery rewards always come in. The limit is only on how many generate daily passive income at the same time.

{% hint style="info" %}
Most paying players never hit the 50 cap in a season — it's there so the biggest hunters face a real "which asteroids do I keep?" decision, not to limit everyday play.
{% endhint %}

**Next:** [Rarity tiers →](/asteroid-shiba-docs/asteroids-and-rarity/rarities.md)


---

# 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://asteroid-shiba.gitbook.io/asteroid-shiba-docs/core-gameplay/portfolio.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.