> For the complete documentation index, see [llms.txt](https://blackpump.gitbook.io/blackpump/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blackpump.gitbook.io/blackpump/how-we-work.md).

# How we work?

How does Black\_Pump work?

The process is simple but thoughtfully designed:

1. We create a new token with a short lifespan (5–10 minutes).
2. We buy back part of our own liquidity to control the token’s price movement and create an attractive market dynamic.
3. We pump the token’s price, pushing it onto scanners (platforms that highlight new coins).
4. New buyers spot the rising token and begin purchasing.
5. Once a real external purchase of at least $20 is made, we immediately pull back all liquidity to our wallet.
6. We lock in the profit and launch the next token.

This cycle repeats dozens of times each day.
\
Thanks to a blend of automation and manual oversight, we achieve stable and consistent results.
\
All activity and statistics are published live in your personal dashboard and in our Telegram channel.


---

# 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://blackpump.gitbook.io/blackpump/how-we-work.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.