> For the complete documentation index, see [llms.txt](https://docs.pumpfun.solhuger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pumpfun.solhuger.com/reference/glossary.md).

# Glossary

Plain-language definitions of the terms used across the Solhuger Pumpfun Launchpad.

| Term                          | Definition                                                                           |
| ----------------------------- | ------------------------------------------------------------------------------------ |
| **Bonding curve**             | The pricing mechanism on Pump.fun. The token price rises as more tokens are bought.  |
| **Bundle**                    | A group of transactions sent together so they are processed together.                |
| **Collect (Collect All SOL)** | Moves SOL from your project wallets to the Target Wallet.                            |
| **Disperse**                  | Sends SOL (or tokens) from one wallet to many wallets.                               |
| **Holder**                    | A wallet that holds your token.                                                      |
| **Jito tip**                  | A small amount of SOL paid with your transactions to help them be processed quickly. |
| **Market cap**                | The total value of all tokens at the current price.                                  |
| **Metadata**                  | The name, symbol, image, description and links attached to a token.                  |
| **Mother Wallet**             | The wallet that funds your market-maker wallets.                                     |
| **Project**                   | A workspace on your dashboard for one token.                                         |
| **Pump.fun**                  | The Solana platform on which tokens are launched and traded on a bonding curve.      |
| **SOL**                       | The native currency of Solana, used for purchases and fees.                          |
| **Slippage**                  | The largest price change you accept between sending a trade and its execution.       |
| **Sniper wallet**             | A wallet that buys your token at launch.                                             |
| **Symbol**                    | The short ticker of your token, for example `AAA`.                                   |
| **Target Wallet**             | A wallet you control that receives collected funds.                                  |
| **Token address**             | The unique on-chain address of your token.                                           |
| **Zombie Wallet**             | The project's main wallet, used to fund and deploy the token.                        |


---

# 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://docs.pumpfun.solhuger.com/reference/glossary.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.
