> For the complete documentation index, see [llms.txt](https://hfun.gitbook.io/hypurr-fun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hfun.gitbook.io/hypurr-fun-docs/guide/account/multi-wallets.md).

# Multi Wallets

Hypurr Fun creates a wallet for you by default, but you can also import or link existing wallets into the bot. The number of wallet slots you have depends on your **$HFUN balance**.

***

### **How to Link Wallets**

There are three ways to link a wallet into the bot:

1. **Private Key**:
   * Full functionality, including transfers, bridging out on Arbitrum, spot/perp trading, and pre-market trading.
   * Recommended for active trading.
2. **API Key**:
   * Allows spot/perp trading without exposing your private key.
   * Provides an additional layer of security.
3. **Read-Only**:
   * View-only mode to check your balance and track PnL.
   * Ideal if you don’t plan to trade with this wallet.

***

### **Why Import Additional Wallets?**

* **HFUN Privileges**: Access benefits tied to your $HFUN balance, such as priority in sniping or other exclusive features.
* **Whale Chats**: Gain entry to exclusive community spaces for high-value traders.

***

### **Security Recommendation**

If you do not plan to actively trade with a wallet, it’s best to import it in **Read-Only mode** for enhanced security.


---

# 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:

```
GET https://hfun.gitbook.io/hypurr-fun-docs/guide/account/multi-wallets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.