> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/telegram-and-promotion/31-boosts.md).

# 31. Boost a token in the Spawn Feed

Buy time-limited website visibility and understand how boosts differ from Trending.

**Open:** the SPAWN token page → **Boost $TICKER**. Anyone with a supported wallet can buy a boost when the tool is enabled; creator ownership is not required.

## What a boost does

Boosts increase paid visibility in SPAWN's discovery/feed ordering. **Hot Spawns** includes actively boosted tokens, and boost counts influence **Fresh Spawns** ordering. A boost is not a token purchase, an organic Trending rank or a Telegram sponsored campaign.

## Buy a boost

1. Confirm the token's full mint on its page.
2. Read the current price per boost and duration.
3. Choose **1x**, **5x**, **10x** or **25x**.
4. Review **Boost for \[total] SOL**.
5. Connect the payer wallet if needed, then choose the action.
6. Review and approve the payment transaction, which includes the token-specific reference.
7. Wait for **Boosted** and the updated active count.
8. Open the feed to check the relevant category.

The screen currently uses 24 hours as the default duration, but the active price/duration are configurable. Read the displayed live values. Network fees are additional. Boost purchases are described as nonrefundable website visibility, not a guarantee of placement duration beyond the purchased terms or a particular number of impressions.

## Troubleshooting

| Problem                          | Resolution                                                                                                                   |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Button disabled                  | Wait for pricing/configuration and wallet connectivity.                                                                      |
| Payment sent but count unchanged | Preserve the signature, wait and reload the same token page. Saved pending confirmation is checked on return.                |
| Still missing after confirmation | Contact support with the token and signature before paying again.                                                            |
| Boost count later fell           | Time-limited boosts expire. Check the purchase time and duration.                                                            |
| Token not first on the feed      | Other tokens may have more active boosts, and official pinning/category rules can affect order.                              |
| No Trending badge                | Boosts and [Trending promotion](/spawnmeme-docs/feature-guides/telegram-and-promotion/30-trending.md) are separate features. |

**Success:** the payment is verified and the active boost count changes for the intended token. Save the receipt until that happens.

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/telegram-and-promotion/31-boosts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.